Issues Accessing FastAPI /docs and /health via Proxy
I am running a FastAPI application inside my RunPod GPU pod. The application works correctly inside the container — for example:
curl http://127.0.0.1:8000/upscale
and
curl http://127.0.0.1:8000/health
both return valid responses.
When I test externally via the RunPod proxy URL, POST requests to /upscale work fine. However, GET requests to other endpoints such as /docs, /health, or even / always return HTTP 404.
Example:
curl -v https://<POD-ID>-8000.proxy.runpod.net/docs
Response:
HTTP/2 404
So, to summarize:
Inside the pod, all endpoints (/, /health, /upscale, /docs) work perfectly.
Externally, only /upscale (POST) works.
Any GET endpoints return 404 through the proxy.
Could you clarify if the RunPod proxy only supports certain paths/methods, or if this is a configuration issue on my side? If the proxy is limited, what’s the recommended way to expose all FastAPI endpoints (such as /docs and /health) for external access?
Thank you very much for your help!
curl http://127.0.0.1:8000/upscale
and
curl http://127.0.0.1:8000/health
both return valid responses.
When I test externally via the RunPod proxy URL, POST requests to /upscale work fine. However, GET requests to other endpoints such as /docs, /health, or even / always return HTTP 404.
Example:
curl -v https://<POD-ID>-8000.proxy.runpod.net/docs
Response:
HTTP/2 404
So, to summarize:
Inside the pod, all endpoints (/, /health, /upscale, /docs) work perfectly.
Externally, only /upscale (POST) works.
Any GET endpoints return 404 through the proxy.
Could you clarify if the RunPod proxy only supports certain paths/methods, or if this is a configuration issue on my side? If the proxy is limited, what’s the recommended way to expose all FastAPI endpoints (such as /docs and /health) for external access?
Thank you very much for your help!
