Thanks for the great tutorial! I have done this successfully with multiple sites (subdomains) set up as multiple server config files for nginx, proxying to their respective locations. I haven't been able to successfully get this to work. Perhaps there's an issue with how it's passing the address to the host...

@MissingRemote

5 ай бұрын

What response do you get from the server? If you can get to the RP, then it's almost always a problem with the way the routes are defined.

@woltjerl

5 ай бұрын

@@MissingRemote It gets to the RP but it's not passing correctly to the host. I think I'll just stick with subdomain routing. Thanks again for your video! It was very helpful for me.

Hello, I haven't tried this yet. But I must say this will helo me a lot thank you. I did have one question. Is it possible to do an updated video showing how to do the multiple servers? The problem I'm facing is that I have 3 all the same ports 80 for http and port 21 for ftp. Not sure how to tackle that.

@MissingRemote

5 ай бұрын

This is a HTTP(S) reverse proxy. I don't think it will work for FTP (you really shouldn't be using FTP either, it's not secure). For HTTP(S) traffic, it is managed by the location sections. Each "location /route" block points back to the internal server.

@DiyintheGhetto

5 ай бұрын

@@MissingRemote I have 3 servers that have http, https and ftp. The problem for me is I need to give all this to the people I know. All server have the same ports and I can not change any of the ports.

@MissingRemote

5 ай бұрын

This method will work for HTTP/HTTPS. I don't think it will work for FTP. The location blocks are how you configure the reverse proxy from the system that is port forwarded from your gateway to the other systems. You don't have to change ports.

@DiyintheGhetto

5 ай бұрын

@@MissingRemote Got you Thank you. I think there is a way to change ftp ports. I should be okay with that. Just need to figure out how to add the other servers now.