-
Notifications
You must be signed in to change notification settings - Fork 5.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
Websocket: Unable to hijack the connection #452
Comments
It's probably not a problem specific to consul backend. What version of Traefik are you using ? $ traefik version We had a regression last month. It has been fixed in recent released. |
It seems to be on rc2. Could you give us some DEBUG logs? |
traefik version returns:
How can I get some DEBUG logs? I tried starting traefik with -d and -l DEBUG.
|
Ok thanks. Last thing, what is your toml file (or command line)? |
The command line is: traefik_consul.tmpl is the same as the original template except it skips consul:
|
I'm getting the same error (without the crash) while using the file config driver. My back-end is Mattermost, fwiw. |
To clarify, the last log |
Oh, lol. Thanks for letting me know. :) On Mon, Jun 13, 2016 at 2:57 AM ydemartino [email protected] wrote:
|
It seems |
Here's my Traefik config. Running in a Docker container, with no specified https://gist.github.com/adamgoose/45bccd014d9ca82c81ad36cb536c711d |
After more investigations with @adamgoose, here are options that don't work with websockets:
These issues are in https://github.com/vulcand/oxy. |
Thank you! :D |
I confirm, removing ddr load balancer from my config fixes the issue. Thank you! |
Hi,
I have a hard time understanding this issue.
I use traefik 1.0.0-rc2 with consul discovery. Everything works fine except the websocket. When I try to connect to my websocket I see this log:
WARN Unable to hijack the connection:
I tried to monitor the connection with wireshark. What I can see is that traefik is opening the connection to the server but there is nothing more... Just SYN/ACK.
When I try to access another non-websocket URL from this backend, it works.
I tried to setup the same configuration using the file backend approach. With this configuration the websocket works normally.
Can you help me to figure out why this does not work with consul discovery?
Thank you!
The text was updated successfully, but these errors were encountered: