-
Notifications
You must be signed in to change notification settings - Fork 667
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
reverse proxy #25
Comments
Maybe because websocket connection is not getting establised? I am not sure. It will be related to proxy. Check out nginx proxy config in Readme. |
It seems that Pound is not ready yet for websockets. ... :/ Thanks for all your help! Appreciated! |
butlerx
pushed a commit
that referenced
this issue
Oct 13, 2018
* Added Apache configuration for proxifying wetty. * Typo fix for Apache configuration. * Updated procedure for starting wetty (use of bin/index.js instead of app.js)
butlerx
pushed a commit
that referenced
this issue
Jan 12, 2019
* Added Apache configuration for proxifying wetty. * Typo fix for Apache configuration. * Updated procedure for starting wetty (use of bin/index.js instead of app.js)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using a reverse proxy called Pound on my system.
On connecting:
And have only a red frozen cursor on the client - no error messages in the client console.
How could I troubleshoot this, and what settings are recommended in general for a proxy?
The text was updated successfully, but these errors were encountered: