Linux – Apache Web Server Works Locally Not Globally

I don't know about your particular ISP, but I am pretty sure most ISPs block port 80. Here are some things you can try.

First, you can verify that your router is accessible from the internet. Most router firmwares allow some form of "remote access" . Pick a random port, beyond 8000, say 8680. Then, verify that you are able to access the router at http://your.actual.ip.address:8680. If this opens up your router page, you are on the right track.

Next, try changing the port. You don't have to mess with the server, just forward port 8700 externally to 192.168.2.64:80 internally. Try accessing http://your.actual.ip.address:8700 and that should reach your server.

According to the screenshots you are showing, you have port forwarding oddly set on your WAN connection as follows:

• External Port Start/End: 80/80
• Protocol: TCP
• Internal Port Start/End: 80/80
• Server IP Address: 192.168.1.11
• Schedule Rule: Always
• Remote IP: 192.168.1.11

The way you have that setup basically tells the router to just route all traffic from 192.168.1.11 on port 80 to 192.168.1.11 on port 80 which makes no sense. The “Remote IP:” should be set to your external IP address of 117.218.XXX.XXX like this:

• Remote IP: 117.218.XXX.XXX

With that in place that tells the router to route all traffic from 117.218.XXX.XXX on port 80 to 192.168.1.11 on port 80.

That said, if the router itself uses port 80 for the D-Link management page, then you need to see if you can change the port that management page uses. Otherwise all you are doing with that ruleset is exposing your D-Link management page to anyone/anything that can reach that 117.218.XXX.XXX. As to how to do that? Each router has different ways to handle that and some routers just don’t provide end users with that option since ISP’s generally don’t want end-users to easily run web servers off of their ISP-provided Internet connection.

If you cannot change the D-Link management page port to be something other than port 80 the next best thing is to just change your web server’s port to be something else, like 8000 or 8080. Of course you now need to adjust your port forwarding rules to match the new port, but it might be the best/simplest solution to this issue.