RUNPOD_ALLOW_IP does not work
I just tried a series of testing with
1. RUNPOD_ALLOW_IP to be my address
2. RUNPOD_ALLOW_IP to be 0.0.0.0/0
3. Without RUNPOD_ALLOW_IP environment variable
Regardless of what I use for the value for the environment variable, I am not able to hit the exposed to port. When I remove the environment variable, then I can start hitting the address. Why is this happening?
---
Edit 1: 0.0.0.0 seems to work with a bit of lag; after a minute or two it starts working
4 Replies
Could it be you guys are behind Cloudflare but not checking for the real IP?
Is this through the proxy? (
id-port.proxy.runpod.net?) We're specifically checking for the CF-Connecting-IP for traffic over this mediumCloudflare Docs
Cloudflare HTTP headers
Cloudflare passes all HTTP request headers to your origin web server and adds additional headers as specified below.
Just to confirm, when you say you can't hit the exposed port - are you getting a 400 response?
Yes - I was getting 400 and couldn't see any access through nginx access log. It was also through the id-port as well...
I'm right now setting the CF-Connecting-IP through nginx and using that straight (which is IPv6) to deny all other access, which seems to work for now.
I tried to use my IPv6 in the env variable as well with no success
Tried again today and it's working. Must've been a blip? Used the same IP, same set of env variable and everything!