nengo / nengo-gui

Nengo interactive visualizer
Other
97 stars 38 forks source link

Unable to run Nengo GUI on Mac #807

Open Seanny123 opened 8 years ago

Seanny123 commented 8 years ago

On OS X, Nengo GUI refuses to open a browser window to start the GUI. In Chrome, I get the following error:

screen shot 2016-07-14 at 12 26 10 pm

In Safari, the error is: screen shot 2016-07-14 at 12 26 10 pm 2

When I try to change localhost to 127.0.0.1, I get the following error, which may or may not be relevant:

Starting nengo server at http://localhost:8080
WARNING:nengo_gui.server:Error response (403): Forbidden
Traceback (most recent call last):
  File "/Users/rgao/Documents/fluffypony/nengo_gui-master/nengo_gui/server.py", line 233, in do_GET
    self.handle_upgrade()
  File "/Users/rgao/Documents/fluffypony/nengo_gui-master/nengo_gui/server.py", line 260, in handle_upgrade
    self.upgrade_to_ws()
  File "/Users/rgao/Documents/fluffypony/nengo_gui-master/nengo_gui/server.py", line 282, in upgrade_to_ws
    raise Forbidden()
Forbidden: Forbidden
parenthetical-e commented 8 years ago

On my computer, I get a different error that might be related.

ERROR:nengo_gui.guibackend:Error during websocket communication.                                                                                               │
Traceback (most recent call last):                                                                                                                             │
  File "/Users/type/anaconda/lib/python2.7/site-packages/nengo_gui/guibackend.py", line 223, in ws_default                                                     │
    msg = self.ws.read_frame()                                                                                                                                 │
  File "/Users/type/anaconda/lib/python2.7/site-packages/nengo_gui/server.py", line 363, in read_frame                                                         │
    self._read()                                                                                                                                               │
  File "/Users/type/anaconda/lib/python2.7/site-packages/nengo_gui/server.py", line 344, in _read                                                              │
    self._buf = self._buf + bytearray(self.socket.recv(512))                                                                                                   │
error: [Errno 54] Connection reset by peer                                                                                                                     │
INFO:root:No connections remaining to the nengo_gui server.                                                                                                    │
No connections remaining to the nengo_gui server.                                                                                                              │
Shutting down server...
celiasmith commented 8 years ago

i only use it on OSX and it's always worked ok for me. so the question is: what is the difference in our setups. i wonder if you have something in your 'security' settings that doesn't allow a server? Found this here

In Lion, do the following:

go to System Preferences > Sharing and enable Web Sharing.

NOTE: There appears to be a bug in Lion for which I haven't found a workaround. If web sharing doesn't start, just keep try

Seanny123 commented 8 years ago

As an aside from Chris' comment, going back to f5958e5 causes the same error with localhost, but switching to 127.0.0.1 seems to resolve the problem.

This is using the OS X Yosemite.

parenthetical-e commented 8 years ago

Using El Cap (10.11.5). I use both a Jupyter and Rstudio server daily. Rolling back to f5958e5 does work fine, so far as I can tell (only ran a brief test).

celiasmith commented 8 years ago

i just updated to the latest versions of the gui and core nengo and it works fine :( (or :) ?) .. i'm on el cap (10.11.5) as well. very strange.

jgosmann commented 8 years ago

Please check #808. It should fix most of the problems. Not sure what causes @Seanny123's initial problem of localhost not working. It might be fixed by adding in IPv6 support, but it might very well persist.