User setting error - Application Error Unable to reach the backend api. If this perists, check the system logs.

[kyoungrok0517]

User setting error - Application Error Unable to reach the backend api. If this perists, check the system logs.

Hello. I'm seeing this error when I try to do something in the system settings. I'm connecting to remote server that I can't access GUI. I tried to download debug bundle but the downloaded file contains nothing but a 500 Internal Error HTML file.

One strange thing is that I see Network error message when starting the server.

wandb: W&B server started at http://localhost:8080 🚀
wandb: You can stop the server by running `wandb server stop`
wandb: Network error (ConnectionError), entering retry loop.
wandb: W&B API key is configured. Use `wandb login --relogin` to force relogin

This is what I see in docker logs <container_id>

*** Running /etc/my_init.d/01_enable-services.sh...
*** Enabling production mode
*** Running /etc/my_init.d/02_load-settings.sh...
*** Loading settings...
*** Booting runit daemon...
*** Runit started as PID 45
*** Starting wandb servers...
*** Migrating database...
Initialized random go rng seed: to fix set env var TEST_GO_RNG_SEED=1555636347484274323
Invoking megabinary "migrate": GOMAXPROCS=48
No change.
Loading custom chart definitions...
*** All services started
*** Access W&B at http://localhost:8080

[umakrishnaswamy]

hey @kyoungrok0517 - few questions & troubleshooting suggestions to dig into this:

• what command are you running specifically to get this error? you mentioned you were trying to do something in system settings, and I'd love to know what you were trying to do so I can dig into this further
• could you try resetting your login credentials? You can do this by doing the following:

In the terminal:

1. Run rm ~/.netrc
2. Run wandb login --relogin --host=http://localhost:8080
3. Enter your API key and run the command you were trying to run again

Please let me know how this goes!

[umakrishnaswamy]

@kyoungrok0517 - We wanted to follow up with you regarding your request as we have not heard back from you. Please let us know if we can be of further assistance or if your issue has been resolved

[exalate-issue-sync[bot]]

WandB Internal User commented: umakrishnaswamy commented: hey @kyoungrok0517 - few questions & troubleshooting suggestions to dig into this:

• what command are you running specifically to get this error? you mentioned you were trying to do something in system settings, and I'd love to know what you were trying to do so I can dig into this further
• could you try resetting your login credentials? You can do this by doing the following:

In the terminal:

1. Run rm ~/.netrc
2. Run wandb login --relogin --host=http://localhost:8080
3. Enter your API key and run the command you were trying to run again

Please let me know how this goes!

[umakrishnaswamy]

hey @kyoungrok0517 - since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!

[kyoungrok0517]

Hello. Thanks for the response. Here are the details.

• I see the the error when I try to update server settings from remote. Can't add a license because I see the same error.

• Now I don't see Network error when I start the server

• I tried re-login but the error persists.

• wandb verify outputs are below

Default host selected: http://localhost:8080
Find detailed logs for this test at: /tmp/tmp9om8mn0y/wandb
Checking if logged in...................................................✅
Checking signed URL upload..............................................✅
Checking ability to send large payloads through proxy...................✅
Checking requests to base url...........................................❌
Connections are not made over https. SSL required for secure communications.
Checking requests made over signed URLs.................................❌
Signed URL requests not made over https. SSL is required for secure communications.
Checking CORs configuration of the bucket...............................✅
Checking wandb package version is up to date............................✅
Checking logged metrics, saving and downloading a file..................✅
Checking artifact save and download workflows...........................✅

[umakrishnaswamy]

@kyoungrok0517 - how did you start the container? sometimes this error can arise when the port set by the container doesn't match the frontend host.

running a command like the following could help address this: docker run --rm -d -v wandb:/vol -p 127.0.0.1:<port>:<port> --name wandb-local wandb/local where you can specify the appropriate ports