I’m using an on-premises version of W&B behind a corporate proxy. We’re trying to create a team within our instance to collaborate on data. To do so, I go to the team settings (as the owner), and type in the username of the person I’m trying to add. W&B tries to send an email to the person. Because we’re behind a SSL proxy, we get this error:
Something went wrong while trying to add the user <USERNAME>: Post "https://api.sendgrid.com/v3/mail/send": x509: certificate signed by unknown authority
Is there an option (like with signing up new users) to just copy an invite link to the clipboard to send ourselves? There doesn’t seem to be a ‘backdoor’ way to add a user to a team, like through python code or an API. Am I missing something?
Are you using a self-signed certificate for the HTTPS load balancer in front of your container? The simplest fix would be to use a trusted cert from https://letsencrypt.org or a trusted vendor like https://www.verisign.com. You may be able to add the authority to the instance itself, but it’s not officially supported today. If you did go this route you would need to run
sv restart gorilla after updating the ca certificates.
@lesliewandb – I have, unfortunately, no control over the corporate proxy, and there is no additional HTTPS load balancer in front of the container either. Even if I added a nginx/traefik https reverse proxy, I would still be faced with getting out through the corporate firewall and errors on that end.
On the user creation page, W&B provides a “copy link” rather than “email link” button. Is the same capability available for the team invites? We can make the team/project completely public, which makes is ‘public within the intranet’ – that might be a viable solution but I would prefer not to rely on it.
Is there somebody that you can contact to do this? The CA certificate needs to be updated to get around this error
Hi @tkott , you can use our public API to invite users to your team. The code snippet below should be able to guide you well.
api = wandb.Api()
team = api.team('your_team_name')
Please let us know in case of any further queries.
@anmolmann unfortunately that (I believe) still tries to send an email using the same service that is unavailable through the UI. So the problem is still the need to “invite” someone, rather than (as an admin, at least) being able to direclty “add” someone without an invite.
This is the error I get, which is unhelpful:
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http://<SERVER_URL>/graphql
wandb: Network error (HTTPError), entering retry loop.
@lesliewandb : Short answer: no.
Long answer: yes, but the answer to a request to avoid this problem will be no, or will come with so many caveats and gotchas and ruin the simplicity of the workflow that it would be irrelevant. This is a non-negotiable part of the job, unfortunately.
I sincerely hope that W&B will consider an option for site admins to be able to just add users to a team without invites, OR to allow team admins to copy / paste an invite link.
I see, thanks for the update @tkott. You should be able to solve this by setting the following environment variable:
If you started the docker container using
wandb local, you can restart the container with this env variable by running:
docker stop wandb-local
wandb local -e GORILLA_EMAIL_SINK=dummy://
you can also add
- "GORILLA_EMAIL_SINK=dummy://" line in your
wandb container in my docker-compose file.
Please let me know if this helps resolving your issue.
Thanks for that ENV variable. What will that do in terms of the invite though? When faced with not being able to send an email, will it just print out the invite to the console? Or add them as originally envisioned?
Hi @tkott , this would make sure that you can add users to any teams without them needing to click on any invites as it’ll turn off email sending and directly add them to teams. So, the the env var I just posted disables email sending.
Hi @tkott , I wanted to follow up on this request. Please let us know if we can be of further assistance or if your issue has been resolved.
Hi, yes! This worked and we can now automatically add folks to a team. Thank you!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.