-
-
Notifications
You must be signed in to change notification settings - Fork 1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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 connection failed on community edition #3824
Comments
Can you please share the latest logs from docker compose logs plausible and your networking configurations (reverse proxies, cdns, etc.)? |
plausible-1 | Loading plausible.. |
What about Google Chrome console logs? Does it include any kind of reason for the connection failure? |
What about the "Console" tab? |
Is there anything showed if you click on one of these log lines? |
No when clicking on it it attempts to open the wss link.. but doesnt work. |
I don't mean clicking on the link, but outside of it :) E.g. on the ➤ symbol. |
Do you use any proxies? |
I use nginx and use the tracker /script.js proxied. Maybe i need to add some websocket stuff to the nginx from the stats server? |
Most likely, yes :) I'm going to move it to discussions since it doesn't seem to be an issue with Plausible itself. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Past Issues Searched
Issue is a Bug Report
Using official Plausible Cloud hosting or self-hosting?
Self-hosting
Describe the bug
app-7a5f917ab82642c1…42aaea32.js?vsn=d:6 WebSocket connection to 'wss:///live/websocket?_csrf_token=X39ZCnwaKDAuBBQUETAuCSF…UBMB0e67tK-jA_ojlgIrKVd7BtfJKv&_mounts=0&_live_referer=undefined&vsn=2.0.0' failed:
Expected behavior
Succesful made websocket connections for small charts
Screenshots
Environment
The text was updated successfully, but these errors were encountered: