Hello supertokens, we've deployed our nextjs app with supertokens to a container on cloud run with an nginx reverse proxy, and we're experiencing some issues with our api. Can you help? Calls to

/api/auth/session/refresh

return 502 (sometimes). Is there anything else we need to be aware of? Essentially, everything starting with

/v1

will be rewritten externally, and everything else should pass through to the app. Here is our nginx config

limit_req_zone $binary_remote_addr zone=mylimit:10m rate=500r/s;

server {
    listen 80;
    listen 8080;
    client_max_body_size 5000M;

    location /v1 {
        limit_req zone=mylimit burst=20 nodelay;
        proxy_pass http://<IP_and_PORT>/v1;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $server_name;
    }
    
    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $server_name;
    }
}