Teo
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
im gonna mark this as resolved since i dont think theres anything that can be done to fix it but perhaps some feedback to make this more robust for service deployments like mine 🙂
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
thanks for your help though!
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
so this solves my issue but imo it would be nice to be able to opt out of this proxying and just get a public IP that i can control myself
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
yeah even if i use the runpod ports i get i have the same issue, it doesnt seem to be possible to use nginx to route traffic to different pods using runpod and the main culprit seems to be this proxy on runpod's side, both for http and tcp
as a workaround i just implemented separate IP whitelists for the other ports
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
just tested using TCP instead, still it creates an ip:port and works similar to HTTPS; if i just have one port then go to the /path for the other one it times out, if i expose that port then i can access it on its newly created ip and port
perhaps the nginx routing should use the runpod ports though? i think thats whats going wrong
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
Like the url/path doesnt actually go there
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
So it seems that the runpod proxy somehow causes issues when reverse proxying like this
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
And no access on that url in the access log, like i see it when i test locally
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
Not sure how to test if its accessible but i had nothing in the error log
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
Inside the container i could curl localhost:1337 and got what i expected when its up
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
Hi! Thanks for the swift reaponse, yep thats exactly the case
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
so i want to connect over all of these paths/ports by exposing only one port
28 replies
RRunPod
•Created by Teo on 4/18/2025 in #⛅｜pods-clusters
runpod nginx networking
server {
listen 6969;
# Frontend — proxy all requests to port 3000
location / {
proxy_pass http://127.0.0.1:3000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
# Stable Diffusion WebUI
location /sd/ {
proxy_pass http://127.0.0.1:7860/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
# LLM server
location /llm/ {
proxy_pass http://127.0.0.1:1337/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
# API
location /api/ {
proxy_pass http://127.0.0.1:8000/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
heres my nginx conf, the frontend works fine interestingly
28 replies