Web Server Crashes on port 80.

In reference to a webserver, a redirect is a function of the server that listens for requests that matches, such as a port, like port 80, a standard web request, and sends the request to port 443 (secure SSL).

Do you mean that you need to access an server on your LAN from the outside world ?

The manual is on the second result of a google search for smcd3gn and the table of contents has clickable links.

The machine you run any inside server on needs a static IP address (192.168.0.11 for example) and you configure the gateway so that your outside request to address and port (http://10.10.10.1:8080) gets mapped to your inside machine's IP address and the port you are running the server on (192.168.0.11:8000) for example.

If you are only using one internal web server just map port 80 to port 80 along with the inside IP and you can omit the port number in the external URL. (If you are running more than one server you should be able to figure it out.) Remember to disable external access to the router's configuration if you do this because that also runs on port 80.

My example mapped outside port 8080 to inside port 8000 just so they would be different. Remember that one outside port can be mapped to a single inside address and port. You can run two inside machines with a service on their own port 80 but they need different ports on the WAN interface.

Your setup looks correct to me. It might very well be that your ISP is blocking port 80. Go here and check from your server if port 80 is accessible.

If you are the only one that wants to connect to you server, you can simply choose another port to use, i.e. www.myserver.com:801. Set port forwarding form port 80 to 801 in your router.
TCP&UDP - from 801 - to 80 - [serverIP] - [Webserver]

The better way is to use a service like DynDNS.com or No-IP.com. You can register a DNS name (like myserver.dyn.com), which redirects to your public IP. The trick is to update your IP address, so even if you have a dynamic IP assigned from your ISP, the redirect will point always to your server. Most routers have the ability to set up with DynDNS, so the process runs in the background and you don't have to update manually - check your router manual.

The second part of this beauty is the redirect to a different port. So even if your port 80 (and 25 for that matter) are blocked, you don't have to have an arbitrary number in your URL (http;//myserver.com:801). You can find more detailed information here.

For a quick check, change your webserver to run on port 801, enter the redirect in your router and see if you can get to your server from the outside (internet). If you still can't access the webserver, the problem is not a blocked port.

Hope this helps, but if you have any more questions, just come back here and leave a comment - I'm happy to help you figuring this out.

I did this with a cctv and another dns server and does not really work. So i just change my ip to static and open ports 80 and 443 and 8000 (server) and worked fine without using ddns or free dns. Oh and i use this to check my ports if they are working

http://canyouseeme.org/

I am uncertain if you already have a server on your machine, however you will want to download one (a server). The best around is obviously Apache. Once downloaded, install it to C:\Apache (Not the default C:\Program Files\Apache Foundation folder). Afterward set up your Internet Modem to forward port 80 on TCP and UDP to your computer's IP address (Not necessary if you're not behind NAT or a firewall)

Once you've done that you have a running web-server. Any document's you place in Apache's, "htdocs" folder will be accessible from the web.

Now to get you a DNS. Try out DynDNS. They have free services (which I myself use) and some services which cost money. Most likely you're after a domain name, so you're going to end up paying for your DNS services. However once you have an account you will want to forward any traffic dialing the DNS to your computer's IP Address.

After the DNS is setup any traffic visiting your DNS will be forwarded to your computer's IP address where Apache will direct them to the files located in its, "htdocs" folder.

Let me know if you need me to clarify any one of the previous points, I will gladly do so.

Good luck.

go to http://www.whatismyip.com/ and then have them type in that ip address. if you have had them typing in your internal ip address that will not work. Try the ip that that website tells you is yours. Also do you have it forward port 80 to your computer? also you should set up DHCP reservations for the server. Hope that that helped.

You have to create an object for your Web server and then set up new rule to forward traffic via port 80 to the newly created object.

Router cannot forward tcp requests to linux box if it has a http server already running on the same port. Make the router's web server listen on a different port.

1. Make sure that your ISP is not blocking port 80. You can check that here. (Otherwise switch to another port like 8080 or 805)
   
2. Have you setup your DDNS service on your router or ensured by other means that no-ip has your up-to-date external IP? (Make sure that your external IP matches the entry at no-ip.com!)
3. Set your LAN server to a static IP address
4. Make sure that port forwarding is enabled and pointing to your server.
   - That means: if you run a webserver on port 80, you have to set the external port to 80 and leave the internal blank, unless your internal server listens on a different port.

If this does not help, what exactly do your mean by "Fail to connect"? Is it a 404 error? Please provide details.

I think this might be interesting for some other people too. So please come back and leave a comment!

Good luck!

Hi Robmoll,
Let's get a little bit more in detail. I'm doing the same exact thing you are trying to do with a D-Link DI-624 and I'm using NO-IP instead of DynDNS. I'd like to ask you a question, if I may, what are you actually seeing now using port 80 and how did you disable it? Can you connect another PC to the same router (making a small Home Network) and test locally your Apache and eventually your web-page by typing something like this "http://192.168.0.101/"? Are you already able to see your router from the "outside" trough port 8080? Are you specifying your "private" IP in the port forwarding setting of your router? Do you mind showing a snapshot of your port forwarding settings? Here is mine; you see two different IP's because there are two PC connected.

Regards,
GiBi