Environment variable not being set correctly

[dickravison]

Hi @evroon, thanks for creating this, it's great! I'm having an issue when updating from v1.5.3 to v2.0.0+. I get this error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8400/token. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 400

This is only when using a public endpoint instead of localhost. I have set NEXT_PUBLIC_API_BASE_URL to my public endpoint and this works fine on v1.5.3 but not on v2.0.0+. It looks as though this env var isn't being set for some reason. Could the bug detailed in this issue have come back?

#843

I've tested this on v2.0.0, v2.0.1 and v2.0.2 and all of them have the same issue. Let me know if you need any more info.

[evroon]

Ah that would be annoying, how do you set the environment variable? Do you pass it in docker-compose or do you build the image yourself using this variable?

[evroon]

And thanks for looking at the existing issue, troubleshooting and testing it on multiple releases btw!

[dickravison]

Thanks for the quick response! I'm setting it in docker-compose, like this:

services:
 ...
  bracket-frontend:
    container_name: bracket-frontend
    environment:
      NEXT_PUBLIC_API_BASE_URL: "https://api.tournament.abc.xyz"
      NEXT_PUBLIC_HCAPTCHA_SITE_KEY: "10000000-ffff-ffff-ffff-000000000001"
      NODE_ENV: production
    image: ghcr.io/evroon/bracket-frontend:v2.0.1
    ports:
      - 3000:3000
    restart: unless-stopped
...

No worries, I know how much easier troubleshooting is when you as much info as possible! Let me know if there are any other settings that'd help troubleshoot or anything you'd like me to try to test :)