Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
How do you configure apache to allow access from inside and outside a network? When I access it internally (via IP address) is tries to load the public IP which isn't a local address. The only way that I can get to my own site from home is to connect to a public proxy and come back in to my network, which is a pain because every proxy I try is completely unreliable.
I already have that set to listen on port 8080 because my ISP blocks > 1024 (unless I pay them $10 per month).
I think that the problem has to do with the ServerName being set to my public IP address.
When I connect to the machine via the local IP (http://10.50.0.xxx:8080/~user) then the address is automatically switched to the public IP address which isn't accessible from inside my network.
Have you setup name resolution in /etc/hosts? It should not be necessary to specify the port for http connections as it should respond to requests on port 80 which are then sent to the specified DocumentRoot. For example on my server if I use either the IP address or server name I am sent to /var/www/index.htm. If I try a link on the internet to this address I cannot because I am using the same interface. This sounds like either a DocumentRoot problem or a firewall problem.
Yes I have the server added to the /etc/hosts file.
I specify the port because it's not on the default 80. The server is running on an alternate http port 8080 and my browser doesn't check that. I think I may have at least narrowed down the problem.
Seems like that would work but I get the same results. This only happens when I append the ~user but it is still trying to use the public IP (ServerName).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.