runpod nginx networking
hi all!
Just started working with runpod and im quite impressed with the affordability but im having some trouble now that im building an application that uses nginx to send users down different ports
so this works perfectly locally, i have an app that has services running on multiple ports and the user connects to just one port then goes to various /paths and gets connected to the different services using nginx's proxy. The idea is to just have one port open and filter access through it in nginx (because runpod also doesnt have a firewall feature it seems)
The problem is that when i go to the runpodurl/path i get redirected to an ip then that path, which times out since its incorrect. If i expose the port then i can visit the service normally through the different port's url, but that's not what i want, the idea is to just have a single port. I really want to get this running in runpod, in aws this works very seemlessly since the networking is simple and what you expect of public cloud, but its a lot more expensive. It would suck if I cant deploy my application in runpod just because of this. I feel that firewalls between the compute im paying for and the internet is a bare minimum for a cloud provider to have. Whatever solution I would have to implement now would seem very hacky and i dont see why that's neccesary, so some feedback on the service there. Other than that im really happy with the simplicity so appreciate you guys making it!
Has anyone else experienced this issue this issue and can suggest a solution? Thanks in advance!
Just started working with runpod and im quite impressed with the affordability but im having some trouble now that im building an application that uses nginx to send users down different ports
so this works perfectly locally, i have an app that has services running on multiple ports and the user connects to just one port then goes to various /paths and gets connected to the different services using nginx's proxy. The idea is to just have one port open and filter access through it in nginx (because runpod also doesnt have a firewall feature it seems)
The problem is that when i go to the runpodurl/path i get redirected to an ip then that path, which times out since its incorrect. If i expose the port then i can visit the service normally through the different port's url, but that's not what i want, the idea is to just have a single port. I really want to get this running in runpod, in aws this works very seemlessly since the networking is simple and what you expect of public cloud, but its a lot more expensive. It would suck if I cant deploy my application in runpod just because of this. I feel that firewalls between the compute im paying for and the internet is a bare minimum for a cloud provider to have. Whatever solution I would have to implement now would seem very hacky and i dont see why that's neccesary, so some feedback on the service there. Other than that im really happy with the simplicity so appreciate you guys making it!
Has anyone else experienced this issue this issue and can suggest a solution? Thanks in advance!
