question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR:visdom:failed CONNECT via proxy status: 403

See original GitHub issue

When I run the code:

import visdom import numpy as np vis = visdom.Visdom(server=‘http://10.8.0.1/’, port=8080) #visdom.Visdom(use_incoming_socket=False) #vis = visdom.Visdom() vis.text(‘Hello, world!’) vis.image(np.ones((3, 10, 10))) #################################################################

Ouput on terminal:

WARNING:root:Setting up a new session… ERROR:visdom:failed CONNECT via proxy status: 403 ERROR:visdom:failed CONNECT via proxy status: 403 ERROR:visdom:failed CONNECT via proxy status: 403 WARNING:visdom:Visdom python client failed to establish socket to get messages from the server. This feature is optional and can be disabled by initializing Visdom with use_incoming_socket=False, which will prevent waiting for this request to timeout. ######################################################### How to fix this proxy problem and what are the commands for using visdom since I am using firefox of the same server as a screen for visualization?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

20reactions
OlofHarryssoncommented, Feb 4, 2019

I sit behind a proxy due to company reasons. Since I’m running everything on my own computer I don’t know how this would work with ssh but I managed to get around the connection problem by running my script that was connecting to the Visdom server via the no proxy command eg. -> no_proxy=localhost python train.py

The visdom server was started like normal

2reactions
tlatlbtlecommented, Mar 20, 2020

I sit behind a proxy due to company reasons. Since I’m running everything on my own computer I don’t know how this would work with ssh but I managed to get around the connection problem by running my script that was connecting to the Visdom server via the no proxy command eg. -> no_proxy=localhost python train.py

The visdom server was started like normal

Thanks so much for your suggestions! I solve my problem. I meet the same problem when I run scripts on remote server.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Proxy Error Meaning - http Status Codes - Bright Data
A 403 error code, however, means your access to the site is forbidden. The request was understood, but the site did not want...
Read more >
failed CONNECT via proxy status: 407 · Issue #486 - GitHub
Bug Description I use the company intranet, can not connect proxy. Don't know where to set the username and password.
Read more >
5 Ways to Fix 403 Forbidden Error (2020 Edition) - Medium
In this guide, we're going to get over with 403 Forbidden Error. ... can not have excess access to the website if you're...
Read more >
403 Forbidden error: What it is and how to fix it - Allconnect.com
Prohibited IP address – There can be several reasons for this, but sometimes it boils down to spam or unwanted posts from a...
Read more >
failed CONNECT via proxy status: 403 when running in python ...
When trying to run my .py script it's showing the error websocket._exceptions.WebSocketProxyException: failed CONNECT via proxy status: 403.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found