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

Can't access PonyGateway lobby: tornado.access:404 #190

Open
davidgruebl opened this issue Mar 29, 2016 · 17 comments
Open

Can't access PonyGateway lobby: tornado.access:404 #190

davidgruebl opened this issue Mar 29, 2016 · 17 comments
Labels
websockets Issues affecting the websockets communication layer

Comments

@davidgruebl
Copy link

After encountering and working around #189 I ran into the following:

$ ponyd serve
PonyGateway starting. Listening on http://127.0.0.1:9000
WARNING:tornado.access:404 GET / (127.0.0.1) 2.11ms

The webserver seems to be up, while the PonyGateway lobby is not being served.
http://localhost:9000/ only gets me 404: Not Found

@luccascorrea
Copy link

+1

@leonardowistuba
Copy link

+1

screen shot 2016-04-06 at 4 34 08 pm

@spark86
Copy link

spark86 commented Apr 7, 2016

+1

@ricardopaiva
Copy link

+1 :(
Using El Capitan.

@undsoft
Copy link

undsoft commented Apr 17, 2016

+1

@batiatto
Copy link

batiatto commented Apr 23, 2016

+1

also using el Capitan

@lakhman
Copy link

lakhman commented Apr 23, 2016

+1 also el capitan

@moko-ist
Copy link

+1 also using El Capitan

and try to access other endpoint directly like http://127.0.0.1:9000/device,
then i got the same error with the following error page

Can "Upgrade" only to "WebSocket".

@kenichi
Copy link

kenichi commented May 5, 2016

i was able to make the service find the correct directory for the web files. i started with changing:

~/Library/PonyDebugger/lib/python2.7/site-packages/ponyd-1.0-py2.7.egg/ponyd/gateway.py

this line:

https://github.com/square/PonyDebugger/blob/master/ponyd/gateway.py#L218

should be static_path = .... then i was able to fire up ponyd with:

$ ponyd serve -v -i 0.0.0.0 -s ~/Library/PonyDebugger/src/ponydebugger/ponyd/web

at this point, both my app with the debugger lib in and chrome were able to connect to the ponyd service. the coredata model browsing feature, which is what i was after with all of this, does not appear to work though 😢 . i can double click the indexeddb, see the model names, but i can't do anything past that.

@AmjadAlSawafta
Copy link

+1 also capitan OS

@mlostekk
Copy link

same here on osx 10.11.4

@reejosamuel
Copy link

same from 10.11.5

@ghost
Copy link

ghost commented Jun 15, 2016

@kenichi can you try to add the method below in the file gateway.py in this class

class DeviceHandler(tornado.websocket.WebSocketHandler):

def check_origin(self, origin):
    return True

@luccascorrea
Copy link

For anyone still having this problem, I was able to solve it by copying the contents of the "web" folder (https://github.com/square/PonyDebugger/tree/master/ponyd/web) to /usr/local/lib/python2.7/site-packages/ponyd-1.0-py2.7.egg/ponyd/web.

This problem happens because ponyd can't find the static files. Hope it helps anyone.

@dkavraal
Copy link

Thanks for your comments. I have created a workaround. It worked for me on El Capitan and python2.7

@mediba-Kitada
Copy link

👍

@paramu
Copy link

paramu commented Oct 16, 2016

@luccascorrea ...your solution worked for me ....thanks

@asmallteapot asmallteapot added the websockets Issues affecting the websockets communication layer label Jul 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
websockets Issues affecting the websockets communication layer
Projects
None yet
Development

No branches or pull requests