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

WebSocket error messages #13

Closed
mterwill opened this issue Sep 6, 2016 · 1 comment
Closed

WebSocket error messages #13

mterwill opened this issue Sep 6, 2016 · 1 comment
Labels

Comments

@mterwill
Copy link
Owner

mterwill commented Sep 6, 2016

Probably has something to do with the nginx reverse proxy. I think it's set to /cable right now and this looks like it's requesting /cable/.

I, [2016-09-06T06:20:10.861752 #8714]  INFO -- : [348838b5-29a6-4cf5-a2cc-5d639ed8b364] Finished "/cable/" [WebSocket] for 68.40.195.218 at 2016-09-06 06:20:10 +0000
I, [2016-09-06T06:20:11.480329 #8714]  INFO -- : [e18ef3c3-f311-4e30-b434-8e030e78fa31] Started GET "/cable" for 68.40.195.218 at 2016-09-06 06:20:11 +0000
I, [2016-09-06T06:20:11.481667 #8714]  INFO -- : [e18ef3c3-f311-4e30-b434-8e030e78fa31] Started GET "/cable/" [WebSocket] for 68.40.195.218 at 2016-09-06 06:20:11 +0000
E, [2016-09-06T06:20:11.481819 #8714] ERROR -- : [e18ef3c3-f311-4e30-b434-8e030e78fa31] Request origin not allowed: null
E, [2016-09-06T06:20:11.481960 #8714] ERROR -- : [e18ef3c3-f311-4e30-b434-8e030e78fa31] Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
@mterwill mterwill added the bug label Sep 6, 2016
@mterwill
Copy link
Owner Author

This appears to no longer be an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant