Teo
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
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
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