Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local Quick Start Guide doesn't work #111

Open
Inquisitive-ME opened this issue Mar 8, 2023 · 14 comments
Open

Local Quick Start Guide doesn't work #111

Inquisitive-ME opened this issue Mar 8, 2023 · 14 comments

Comments

@Inquisitive-ME
Copy link

Inquisitive-ME commented Mar 8, 2023

I am running wandb server on 1 computer and trying the quickstart example code on another computer all on my local network.

On the computer I am trying to run the quickstart guide on I cannot get wandb.init() to work in Python. The output I get is:

wandb: W&B API key is configured. Use `wandb login --relogin` to force relogin
wandb: Network error (ConnectionError), entering retry loop.
wandb: Network error (ConnectionError), entering retry loop.

I am running wandb login on the command line before running the Python scrip that calls wandb.init()

I am starting wandb server with
wandb server start -e HOST=http://192.168.99.156:8080

and have tried the login with both
wandb login --host http://192.168.99.165/
wandb login --host http://192.168.99.165:8080

and can access the webpage from the computer I am trying to run wandb.init() in Python on.

@nate-wandb
Copy link
Contributor

Hi @Inquisitive-ME, still looking into this on our side. Can you try running wandb verify on the machine that is not running the Docker container?

Thank you,
Nate

@Inquisitive-ME
Copy link
Author

It just appears to hang and I don't see any logs:

Default host selected: http://192.168.99.165
Find detailed logs for this test at: /tmp/tmphra6d1qd/wandb

Wandb verify works on the host machine:

Default host selected: http://localhost:8080
Find detailed logs for this test at: /tmp/tmp5pihk34z/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...............................❌
Your object store does not have a valid CORs configuration, you must allow GET and PUT to Origin: http://localhost:8080
Checking wandb package version is up to date............................❌
wandb version is not supported by your local installation. This could cause some issues. If you're having problems try: please run `pip install --upgrade wandb==0.13.9`
Checking logged metrics, saving and downloading a file..................✅
Checking artifact save and download workflows...........................✅

@nate-wandb
Copy link
Contributor

@Inquisitive-ME I notice that on the non-host machine, it is trying to access http://192.168.99.165 but the port is not specified.

I believe you tried logging in with wandb login --host=http://192.168.99.165:8080 --relogin correct? If so, can you delete ~/.netrc and `~/.config/wandb/settings and then log in again?

Then when you run wandb login --host=http://192.168.99.165:8080 --relogin it should point to correct port.

Running wandb verify should print Default host selected: http://192.168.99.165:8080 at that point and I believe this will resolve the issues with the API not connecting as well

Thank you,
Nate

@nate-wandb
Copy link
Contributor

Hi @Inquisitive-ME, I just wanted to follow up and see if that helped or if the API is still not pointing to the correct port?

Thank you,
Nate

@Inquisitive-ME
Copy link
Author

Hi I tried the above steps and get

Default host selected: http://192.168.99.165:8080

In the wandb verify output but it is still hung. When I cancel wandb verify it outputs

Aborted!
Checking if logged in...................................................

@Inquisitive-ME
Copy link
Author

I found that even if I login on the host machine with the host set to 192.168.99.165:8080 it does not work. wandb verify also hangs. The host has to be set to http://localhost:8080 for it to work

@nate-wandb
Copy link
Contributor

@Inquisitive-ME on the non-host machine you are able to access the UI at 192.168.99.165:8080 in the browser, correct?

@Inquisitive-ME
Copy link
Author

@nate-wandb that is correct. I am able to access the UI at 192.168.99.165:8080 in the browser. But wandb verify is hanging and any attempt to connect with Python examples ends up in a retry loop

@vanpelt
Copy link
Contributor

vanpelt commented Mar 24, 2023

@Inquisitive-ME that indicates the machine you're running wandb verify on can't connect to 192.168.99.165. This is likely due to firewall rules or other networking issues.

@Inquisitive-ME
Copy link
Author

Okay, it seems like it's an issue with the computer I was trying to run as host. Are there specific ports that wandb uses. I would guess that a port that wandb uses is in use already?

@exalate-issue-sync
Copy link

WandB Internal User commented:
Inquisitive-ME commented:
I found that even if I login on the host machine with the host set to 192.168.99.165:8080 it does not work. wandb verify also hangs. The host has to be set to http://localhost:8080 for it to work

@exalate-issue-sync
Copy link

WandB Internal User commented:
Inquisitive-ME commented:
Okay, it seems like it's an issue with the computer I was trying to run as host. Are there specific ports that wandb uses. I would guess that a port that wandb uses is in use already?

@nate-wandb
Copy link
Contributor

Hi @Inquisitive-ME, wandb server will use 8080 by default but you can specify which port you would like the server to use by starting the container with the following command:

docker run --rm -d -v wandb:/vol -p <available port you would like to access the app on>:8080 --name wandb-local wandb/local

@nate-wandb
Copy link
Contributor

Hi @Inquisitive-ME, I wanted to follow up and see if you were able to make this work or if you had any other questions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants