[SOLVED] can't access my web server from outside my network.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
can't access my web server from outside my network.
Hello group,
I have been getting reports that my web server can't be accessed.
This is a new problem. I beleive it is a problem with one of my LinkSys
routers? I can reach it on the interanet just fine.
In order to debug the problem I need an outside system that I can access
to do thing like ping, traceroute and nmap. Are there any system open
to the publc for free? All I need is a general user ID, no root access is
needed. I would like Ethernet SSL access but dialup would work.
From the LQ Rules (which you agreed to when you signed up here):
Quote:
Originally Posted by LQ Rules
Please do not post requests for help via email, IM or other personal communication channels.
This is so that future people with the same problem who find this thread can find the answers that they're looking for. Also, it allows a better discussion of how to fix your problem.
It sounds like your issue is with port forwarding. Go into your router's settings and forward port 80 to your Linux box. It helps if you set a static IP for your webserver.
You might also want to consider a free dynamic DNS service so you can give people a URL instead of just an IP address (which can and probably will change).
Is port 80 being filtered on the router?
Is port 80 forwarded to a system with a firewall restricting port 80?
When I do this from the inside, I get:
nmap -PNO -sV 64.124.13.3 -p 80
Starting Nmap 6.45 ( http://nmap.org ) at 2015-03-03 12:19 PST
Nmap scan report for 64.124.13.3.gatespeed.com (64.124.13.3)
Host is up (0.0076s latency).
PORT STATE SERVICE VERSION
80/tcp open http Apache httpd 2.2.22 ((Debian))
Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 15.20 seconds
Which shows me I am getting port forwarding to my Raspberry Pi web server.
But shows not filtered??
On my web server:
From the LQ Rules (which you agreed to when you signed up here):
This is so that future people with the same problem who find this thread can find the answers that they're looking for. Also, it allows a better discussion of how to fix your problem.
OK, my bad.
Quote:
It sounds like your issue is with port forwarding. Go into your router's settings and forward port 80 to your Linux box. It helps if you set a static IP for your webserver.
This is how the router is set up. It used to work.
Quote:
You might also want to consider a free dynamic DNS service so you can give people a URL instead of just an IP address (which can and probably will change).
I have had this address for ten years. I do have a DNS naame of
The router is using E-wrt, which is not supported any more. I used to be able to access the router with SSL and web bit not any more. Sounds lie to it time to replace that router and/or the firmware (DD-wrt)? This could also explain my poor down link performance. maybe?
Update:
I found a public web site that allows me to do a traceroute from the outside of my private network. http://http://www.nmonitoring.com/
It shows/suggest the problem is with my ISP.
OK my problem has been solved. The problem was with one of
the WRT54G LinkSys routers. It was running Ewrt and the port
forwarding feature started to have intermittent problems. I replaced
it with a WRT54G router running DD-wrt. The problem
was compounded by my ISP changing my IP address. The old address was 64.124.13.3, it is now 216.173.131.138.
The key to solving the problem was finding a remote site to
test the outside link access. There are many sites that will
help with this. I used ping.eu and pingdom.com both. The reason
I needed a remote site to test the port forwarding link
which was flaky and worked from the network inside but not from the outside. Everything is working correctly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.