404 Not Found error for /api/script.js with Docker + Nginx Proxy Manager setup

[tilwegener]

Hello,

I am having a problem with my self-hosted installation where script.js is returning a 404 Not Found error.

https://analytics.test.com/api/script.js

There are no errors visible in the log.

I have a reverse proxy with NPM and am running a Docker Compose stack.

Best regards and thank you very much!

[Snuffsis]

I have the same, or at least a similar issue.

I am using Coolify for managing and deploying my containers. I do not use the coolify proxy, I use nginx proxy manager because the Coolify proxy doesn't work for my set up (multiple servers with one ip). So the nginx proxy manager serves as entrypoint that then sends requests to the correct machine.

I Deployed using the new Coolify template, I then added my port mappings (I have different ports exposed than 3001 and 3002) to the docker compose.
I set up the A record in cloudflare with proxy enabled for the domain I want to use.
Started the stack and made sure it all starts. Now when visiting the site, I see 404 errors for any /api/ calls made, which also prevents signup and signin. I add the /api location in the proxy_host that was setup in nginx proxy manager with the same server ip but pointing to the api port mapping along with the proxy_set information specified in the nginx-proxy-manager guide.
Now I am getting 502 (bad gateway from cloudflare) for all the /api/ calls.

I disabled the cloudflare proxy, which then got me one step closer, but I am now getting a 500 error saying "Failed to parse url"
{"statusCode":500,"error":"Internal Server Error","message":"Failed to parse URL from https, https://rybbit.domain.com/api/auth/sign-up/email"}

Here is the full log entry from the backend output:
{ "level": 50, "time": 1761727706513, "pid": 1, "hostname": "37d6be09c092", "reqId": "req-e", "req": { "method": "POST", "url": "/api/auth/sign-up/email", "path": "/api/auth/sign-up/email", "parameters": { "*": "sign-up/email" }, "headers": { "host": "rybbit.domain.com", "x-forwarded-scheme": "https", "x-forwarded-proto": "https, https", "x-forwarded-for": "ip1, ip2, ip1", "x-real-ip": "ip1, ip1", "connection": "Keep-Alive", "content-length": "93", "priority": "u=0", "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0", "accept": "*/*", "accept-language": "en-GB,en;q=0.5", "accept-encoding": "gzip, br", "referer": "https://rybbit.domain.com/signup", "content-type": "application/json", "origin": "https://rybbit.domain.com", "sec-gpc": "1", "alt-used": "rybbit.domain.com", "sec-fetch-dest": "empty", "sec-fetch-mode": "cors", "sec-fetch-site": "same-origin", "cf-ray": "996169f56a511656-ARN", "cdn-loop": "cloudflare; loops=1", "cf-connecting-ip": "ip2", "cf-ipcountry": "SE", "cf-visitor": "{\"scheme\":\"https\"}" } }, "res": { "statusCode": 500 }, "err": { "type": "TypeError", "message": "Failed to parse URL from https, https://rybbit.domain.com/api/auth/sign-up/email: Invalid URL", "stack": "TypeError: Failed to parse URL from https, https://rybbit.domain.com/api/auth/sign-up/email\n at new Request (node:internal/deps/undici/undici:9588:19)\n at getRequest (file:///app/node_modules/better-call/dist/node.js:69:10)\n at file:///app/node_modules/better-call/dist/node.js:138:36\n at Object.<anonymous> (file:///app/dist/index.js:171:19)\n at preHandlerCallbackInner (/app/node_modules/fastify/lib/handleRequest.js:161:24)\n at preHandlerCallback (/app/node_modules/fastify/lib/handleRequest.js:129:5)\n at validationCompleted (/app/node_modules/fastify/lib/handleRequest.js:119:5)\n at preValidationCallback (/app/node_modules/fastify/lib/handleRequest.js:96:5)\n at handler (/app/node_modules/fastify/lib/handleRequest.js:73:7)\n at /app/node_modules/fastify/lib/contentTypeParser.js:214:9\ncaused by: TypeError: Invalid URL\n at new URL (node:internal/url:806:29)\n at new Request (node:internal/deps/undici/undici:9586:25)\n at getRequest (file:///app/node_modules/better-call/dist/node.js:69:10)\n at file:///app/node_modules/better-call/dist/node.js:138:36\n at Object.<anonymous> (file:///app/dist/index.js:171:19)\n at preHandlerCallbackInner (/app/node_modules/fastify/lib/handleRequest.js:161:24)\n at preHandlerCallback (/app/node_modules/fastify/lib/handleRequest.js:129:5)\n at validationCompleted (/app/node_modules/fastify/lib/handleRequest.js:119:5)\n at preValidationCallback (/app/node_modules/fastify/lib/handleRequest.js:96:5)\n at handler (/app/node_modules/fastify/lib/handleRequest.js:73:7)" }, "msg": "Failed to parse URL from https, https://rybbit.domain.com/api/auth/sign-up/email" }

[Snuffsis]

Actually solved the problem for what I got and it's now working.
I had to remove the proxy_set_header X-Forwarded-Proto $scheme; from the location configuration in npm.

Also now realized, after setting things up, that the api error you described isn't solved by what I did, because I now got to the same issue where the script.js can't be found from the api path. I can see that there is a script.js and a script-full.js in the public folder of the backend container at least.

[Einstein-schrodinger]

This might be useful to you. #487

[Snuffsis]

Tried that to see if it solved it, but no dice.
This is why it looks like in NPM with your suggestion:

[Einstein-schrodinger]

Tried that to see if it solved it, but no dice. This is why it looks like in NPM with your suggestion:

[Rex-82]

I had the same issue and got it working by setting:

location ^~ /api/ {
    proxy_pass http://rybbit_backend:3001;
    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-Proto $scheme;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
  }

in the Advanced settings of the Proxy Host (without any location in Custom Locations)

[Snuffsis]

I had the same issue and got it working by setting:

location ^~ /api/ {
    proxy_pass http://rybbit_backend:3001;
    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-Proto $scheme;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
  }

in the Advanced settings of the Proxy Host (without any location in Custom Locations)

Yes, this was the solution for me (i just updated the proxy_pass information to reflect my setup) and it works fine now.

[tilwegener]

Reinstall fixed it.