-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
visdom shows nothing #111
Comments
Same on python3.6, it used to be OK. |
Same on python2.7 ubuntu 14,04 |
Hmm. Can you surface the Developer Console in your browser and post any error messages that show up on the browser end? With Chrome you can get this in 'View'->'Developer'->'Javascript Console'. |
This time-out error could be solved by proxy, and then Thanks to the GREAT Firewall in China. 👎 |
Would you please give some instructions on how to use proxy to solve this? @zengyu714 |
That is, use your VPN.
2017-08-10 11:29 GMT+08:00 yukang2017 <notifications@github.com>:
… Would you please give some instructions on how to use proxy to solve this?
@zengyu714 <https://github.com/zengyu714>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#111 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATbNA2-qllNHUdED3Wh_h3PZdAOGMBf6ks5sWnkmgaJpZM4OLnir>
.
|
I don't think it can be solved by VPN. Sometimes I use VPN, and visdom works; sometimes I don't use VPN, and Visdom works. But sometimes I use VPN, and Visdom do not work. @zengyu714 btw, it seems that you and me have a same name 'zeng yu' 😃 |
@zengxianyu It works for me without VPN |
It does not work for me 😢 @yukang2017 |
When using it, go to the address : 127.0.0.1:8097 instead of http://localhost:8097. |
The reason is the web browser can not find plotly and react-gird-layout through internet So I downloaded And put them in And I added the search path of them in: So the web browser can find them locally.
Finally, it works and do not need to use a VPN. |
@zengyu714 I met many issues concerning |
I have same problem, but I have a proxy on own machine. I tried to copy locally js libs, but see this logs on js console. |
Please manually download and install the dependencies per the instructions in https://github.com/facebookresearch/visdom/blob/master/CONTRIBUTING.md |
Sometimes, when there is a proxy setup in environment, it will make visdom only display a blue screen. I found that setting os.environ['http_proxy'] = '' solves this case. Hope this could help. |
Without a proxy setting, sometimes visdom server gets stuck expecting something (javascripts?) to be downloaded. With proxy settings it completes start up but it then later runs into the problems mentioned above -- only showing the results upon a reload, and then going into a full blue screen. |
@masoodmortazavi does anything appear in the javascript console or the python server logs when you're running into this issue? |
Comparing the already-downloaded javascript files in the pip installation in Python virtual environment with those specified in visdom's "download.sh" on this git repository, and then using wget over proxy to download missing javascripts into the corresponding folder, fixed the problem. (There should be no OS level http proxy or https proxy settings. This does cause problems. The javascripts should be downloaded with wget -- just like specified on download.sh -- but with proxy settings set up for the wget process that does each download individually.) |
|
I tried all the above-mentioned solutions but still, the error is not getting solved. What else should I do? |
Are you sure there is no proxy between your visdom server and the code generating the visualization, or between the server and the machine on which you are looking at the visdom dashboard? Behavior like this is most commonly caused by some proxy configuration blocking traffic. Do you see any errors in the JavaScript Console? (In Chrome: View -> Developer -> JavaScript Console.) |
Can you please copy-paste the errors you see here? |
Uncaught :2019/extensions/MathMenu.js?V=2.7.1:2 |
This works for my Mac, python 3.6, torch 1.0, visdom 0.1.8.9 |
Visdom : blue screen (or with white tool bar but I cannot see anything plot in screen) if checked develop tools , it also shows click into the above http will show tornado web.py 404 problem. I understand this might be due to some proxy but how should I fix them? What are js.map or css.map file do i really need to find and download them? thanks --Editted on 05/18-- I can see the white menu bar though ( view, enviroment bar) |
@leopardyao The contents of your image suggest that visdom is now running correctly. If you run the demo you should either see plots or potentially errors in the server logs if not. |
Thanks JackUrb. I am curious why this happens? After downloading all necessary static files, why Proxy setting still matters for visdom? As a few people are having the issues, can we add this as an option in future versions when staring visdom server from the command? |
Hi! I get into the same trouble. Could you please tell me how to find some offline downloaded static folder to replace the online one? |
maybe you need to update a newer version of visdom package. |
I am very confused that I tried the demo.py but showed nothing at http://localhost:8097
The server has received the message but shows nothing, the web explorer only shows blue background, It has no other windows.
y406539259@BILL-172:~$ python -m visdom.server
It's Alive!
INFO:tornado.access:304 GET / (127.0.0.1) 5.03ms
INFO:tornado.access:304 GET / (::1) 3.56ms
INFO:tornado.access:304 GET / (222.201.139.49) 3.57ms
INFO:tornado.access:304 GET /favicon.png (222.201.139.49) 2.84ms
INFO:tornado.access:200 POST /events (::1) 1.37ms
INFO:tornado.access:200 POST /events (::1) 2.56ms
INFO:tornado.access:200 POST /events (::1) 1.79ms
INFO:tornado.access:200 POST /events (::1) 1.20ms
INFO:tornado.access:200 POST /events (::1) 0.79ms
INFO:tornado.access:200 POST /events (::1) 1.08ms
INFO:tornado.access:200 POST /events (::1) 1.69ms
INFO:tornado.access:200 POST /events (::1) 1.47ms
INFO:tornado.access:200 POST /update (::1) 1.51ms
INFO:tornado.access:200 POST /events (::1) 1.01ms
INFO:tornado.access:200 POST /events (::1) 0.99ms
INFO:tornado.access:200 POST /events (::1) 0.91ms
INFO:tornado.access:200 POST /events (::1) 0.69ms
INFO:tornado.access:200 POST /events (::1) 0.60ms
INFO:tornado.access:200 POST /events (::1) 9.94ms
INFO:tornado.access:200 POST /events (::1) 6.87ms
INFO:tornado.access:200 POST /events (::1) 1.26ms
INFO:tornado.access:200 POST /events (::1) 0.92ms
INFO:tornado.access:200 POST /events (::1) 0.71ms
INFO:tornado.access:200 POST /update (::1) 0.89ms
INFO:tornado.access:200 POST /update (::1) 0.62ms
INFO:tornado.access:200 POST /update (::1) 1.09ms
INFO:tornado.access:200 POST /events (::1) 1.12ms
INFO:tornado.access:200 POST /events (::1) 0.92ms
INFO:tornado.access:200 POST /events (::1) 1.33ms
INFO:tornado.access:200 POST /events (::1) 0.60ms
INFO:tornado.access:200 POST /events (::1) 0.61ms
INFO:tornado.access:200 POST /events (::1) 0.65ms
INFO:tornado.access:200 POST /close (::1) 0.78ms
INFO:tornado.access:200 POST /events (::1) 0.67ms
INFO:tornado.access:304 GET / (::1) 3.81ms
INFO:tornado.access:304 GET / (127.0.0.1) 2.62ms
INFO:tornado.access:304 GET / (222.201.139.49) 3.58ms
INFO:tornado.access:304 GET /favicon.png (222.201.139.49) 3.68ms
INFO:tornado.access:304 GET / (222.201.139.49) 3.55ms
INFO:tornado.access:200 GET /favicon.png (222.201.139.49) 3.33ms
INFO:tornado.access:304 GET / (127.0.0.1) 3.01ms
INFO:tornado.access:304 GET / (127.0.0.1) 3.74ms
INFO:tornado.access:304 GET / (::1) 3.33ms
INFO:tornado.access:304 GET / (127.0.0.1) 3.35ms
The text was updated successfully, but these errors were encountered: