-
Notifications
You must be signed in to change notification settings - Fork 276
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
Error connecting to websocket #3041
Comments
With a correct configured nginx reversed proxy this should be fixed in current develop. |
I got the issue through IP direct |
The websocket is likely trying to use wss which requires ssl. It will work fine with nginx if you add the websocket details on the page I linked. |
Already added ... |
server { location ^~ /medusa { In the proxy.conf Advanced Proxy Configproxy_connect_timeout 86400; Basic Proxy Configproxy_set_header Host $host; |
Are u using a webroot? |
sorry I don't understand what it is ? :) |
are you running default using a root like this: http://localhost:8082/home/... or did you have a base configured like: http://localhost:8082/medusa/home/... |
I suspect you have the webroot configured, and then you'll need to wait for our next release to have this fixed. Or checkout develop branch. |
OK I understand (thanks) |
Hello
I get this notification error
Error connecting to webscoket
Behind Nginx and with direct IP access
Someone got this issue too ?
Thanks
The text was updated successfully, but these errors were encountered: