-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
traefik reverse proxy, ssl and real time html - cannot connect to websocket #2369
Comments
Unfortunately I'm not familiar with traefik, but there have been some questions related to this, let me know if any of these help: |
Thanks, also for this great tool. I've seen the links but couldn't manage to get it working. For now I opted for static reports via cronjobs, which does the job for me. Thanks! |
Just out of curiosity and something you could try, I know that in some proxies the following configuration has worked:
Also, I'd try without TLS first and see if you get it to work that way. |
Any updates on this? Thanks |
Hey, sorry! I haven't pursued this further, sticked with the static version and moved on to other projects. Sorry and thanks for your time! |
Closing this. Feel free to reopen it if needed. |
Hi,
I've spent some time trying to set up goaccess for a project. While real time html reports worked on localhost, I cannot get it to run on the server with SSL:
Firefox can’t establish a connection to the server at wss://stats.example.com:7890/.
The setup is a docker-compose environment containing traefik as reverse proxy (providing tls certificates), a goaccess docker container and a nginx webserver serving the report. I am unsure how the websocket connection should be routed with the reverse proxy... if at all. maybe this is more a traefik question than a goaccess websocket question. (I'm quite new to the field so please indulge my lack of knowledge.)
excerpt of
docker-compose.yml
:In addition, traefik is configured for entrypoints websecure (443), web (80, redirected to websecure) and "wss" (
entrypoints.wss.address=7890
). The config is a mix of bits and pieces I found online, probably messy and confusing.The generated report is served at
stats.example.com
(obviously I replaced my domain by example.com everywhere), but only static. and real-time updates are not working.The firefox console reports:
Firefox can’t establish a connection to the server at wss://stats.example.com:7890/.
Request Headers:
Stack trace:
Also, the connection attempt is marked as insecure.
I would much appreciate any help you can offer!
The text was updated successfully, but these errors were encountered: