-
-
Notifications
You must be signed in to change notification settings - Fork 249
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 is closed before the connection is established. #213
Comments
Hi @shinebayar-g, do you see anything in server log? |
I'm using nginx reverse proxy as explained here. After a while I'm getting this error. Here is the logs from
Here is nginx error log
|
After googling about nginx error log I've tried
or
Both didn't work. |
In the server log I don't see the websocket connections reaching the server (they should be starting with 101 GET) For the nginx I meant smth like access.log (which connections and redirections are performed). Is there anything like this there? |
I have disabled access_log, let me turn on them.
I think this line looks suspicious |
Hi @shinebayar-g, thanks for the info. So, there is 401 error, however, there are no logs in script server for it. Unfortunately, I won't be able to try to reproduce it locally today (no access to the machine with similar setup) PS please write updates in a separate message. I don't get notifications for message edits :) |
Yea I'm wondering about that too. That double slash doesn't look good, I don't know why it's happening after months of running. I didn't change anything at nginx setup. |
May be I changed the way, how I build the websocket URL, I have to check |
Hi @shinebayar-g, I managed to reproduce the issue with basic auth enabled in nginx. And for me, only Chrome was failing (firefox was fine). The problem, as I see it, is that an authentication header is not passed with websocket connection. There is no way to control this header from the code. The browser should send it automatically. But probably I understand it wrong, will investigate further. |
Anyway, after fixing double-slash issue, it started working for. @shinebayar-g, could you check please, if dev version works for you? If yes, I'll move this fix to stable release |
Okay, @bugy This is screenshot from Safari browser. I'm getting this error instantly. (On google chrome this error appeared after a while) Let me update to dev release and see if it's working. |
It's working, confirmed fixed. |
Updated latest release (still version 1.14.0) |
I've edited
conf.json
file to add new member. I know I have to restart script-server after editingconf.json
. After script-server restart I cannot see Execute button and I'm getting this websocket error. I've updated to latest release 0.14.0 and still seeing the same error..The text was updated successfully, but these errors were encountered: