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.
I was wondering if anyone knew where to find a tutorial on how to set up a reverse proxy in Ubuntu-Server with Apache2 already installed.
I've been messing with it for about two days and haven't had much luck getting it to work.
What I want to do is make it so that when someone connects to my Ubuntu Server, the server well pass the request to an external web server. Right now I am at a test site setting up the front end server to deploy at a later date, but I want to proxy from the test site to a server that is setup at the official site that has a Public IP address. I am currently behind a Private Network at the test site... is this possible?
Is the someone connecting inside the LAN or connecting from the outside? If they are inside the lan, then you should be able to proxy with nginx.
If the someone is connecting from the outside and you want to proxy the request, I'd use a router outside the firewall. If you are in a hosted situation, then the host should do it for you. If you control everything, I'd stick a router in front of the firewall device. If your firewall device is running Linux, it can route for you. Not a 'best practices' moment, but it will do the job.
Right now I have a LAMP Ubuntu-Server, a very simple setup. Routing requests is exactly what I need to do. It's a small network where security and load are not a big concern. Still having trouble setting it up correctly though. One Server in the DMZ passing requests to a few other servers. There is only one up and running at the remote site atm.
Is the someone connecting inside the LAN or connecting from the outside? If they are inside the lan, then you should be able to proxy with nginx.
If the someone is connecting from the outside and you want to proxy the request, I'd use a router outside the firewall. If you are in a hosted situation, then the host should do it for you. If you control everything, I'd stick a router in front of the firewall device. If your firewall device is running Linux, it can route for you. Not a 'best practices' moment, but it will do the job.
I'm not apart of the LAN that I need to proxy to at the moment. I'm not allowed to do any configurations on the Cisco router (student), yet they're letting me do pretty much everything else.. which I find odd. I could ask them about the router config, but these people are far away from the site (over 3 hour drive) and are not likely to give me the passwords.
Is the someone connecting inside the LAN or connecting from the outside? If they are inside the lan, then you should be able to proxy with nginx.
If the someone is connecting from the outside and you want to proxy the request, I'd use a router outside the firewall. If you are in a hosted situation, then the host should do it for you. If you control everything, I'd stick a router in front of the firewall device. If your firewall device is running Linux, it can route for you. Not a 'best practices' moment, but it will do the job.
Currently inside, the Server has a private IP but it well be changed to a public address when we move from the test site.
I'm on a different network (test site), so I'm going to set up another server that will take the place of the server at the remote site for now. Hopefully I can get it to work!! Bit of a noob, sorry!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.