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
Rails WSS connection broken #738
Comments
Hi @mbajur - you might be able do get some more insight into this by enabling Traefik access logs: traefik:
args:
accesslog: true
accesslog.format: json
# Include HTTP headers in logs like so:
accesslog.fields.headers.names.User-Agent: keep There's more documentation here - https://doc.traefik.io/traefik/observability/access-logs/. |
@djmb sadly, enabling that doesn't show anything more in the traefik logs. It's like this request never reaches the server |
@mbajur - did you reboot Traefik ( |
@djmb Ah, right, good catch :) I rebooted and now i indeed can see an output in the logs related to
|
Hello,
I recently moved my production app from Dokku to Kamal and loving it so far but one feature of rails i've been using went broken - the ActionCable support.
Basically, after the migration, my frontend is not able to connect to /cable endpoint anymore. The message in browser log says:
WebSocket connection to 'wss://domain.com/cable' failed:
without giving me any more information about why it failed after the colon. Also, the rails log is empty for/cable
route. The only suspicious thing i can see in traefik logs are these lines:But i'm not sure if that's related as this app is on production already with decent traffic so i'm not able to tell if that relates to the failing wss connection or not. However, the amount of these logs doesn't match the amount of failed wss connection retries so i would say that's not it.
My kamal config looks as follows:
Thank you in advance for any clues!
The text was updated successfully, but these errors were encountered: