Websocket ping/pong timeout not working

[OneB1t]

Welcome!

• [X] Yes, I've searched similar issues on GitHub and didn't find any.
• [X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?

We have application which is running websocket with ping/pong messages implemented based on rfc6455 with traefik running TLS termination. When i pull network cable on client side (so no ping/pong messages can go trough to traefik) the connection between traefik and backend service is never dropped.

We also included all kinds of timeouts based on documentation but nothing is working as expected. Is there any setup we are missing or this behavior is not supported?

Thank you

What did you see instead?

Connection never times out on its own.

What version of Traefik are you using?

2.11

What is your environment & configuration?

azure kubernetes

--log.level=DEBUG 
--api 
--api.insecure 
--entrypoints.web.address=:80 
--entryPoints.web.transport.respondingTimeouts.idleTimeout=30 
--entryPoints.web.transport.respondingTimeouts.writeTimeout=30 
--entryPoints.web.transport.respondingTimeouts.readTimeout=30 
--entryPoints.web.transport.keepAliveMaxTime=30s 
--entryPoints.websecure.Address=:443 
--entryPoints.websecure.transport.respondingTimeouts.idleTimeout=30 
--entryPoints.websecure.transport.respondingTimeouts.writeTimeout=30 
--entryPoints.websecure.transport.respondingTimeouts.readTimeout=30 
--entryPoints.websecure.transport.keepAliveMaxTime=30s 
--entrypoints.sftp.address=:2222 
--entrypoints.web.http.redirections.entrypoint.to=websecure 
--entrypoints.web.http.redirections.entrypoint.scheme=https 
--certificatesResolvers.le.acme.dnsChallenge=true 
--certificatesResolvers.le.acme.dnsChallenge.provider=azure 
--certificatesresolvers.le.acme.email=*****@gmail.com 
--certificatesresolvers.le.acme.storage=/opt/acme.json 
--providers.kubernetescrd

If applicable, please paste the log output in DEBUG level

No response

[framebassman]

@OneB1t Could you reproduce this issue with the v2.11.2 version? They had an issue with the websockets for 2.11.1 - #10598

[OneB1t]

@framebassman We are already on 2.11.2 and we still encounter the issue. Is there anything else i can provide to help with troubleshooting?

[mloiseleur]

@OneB1t Would the recent keepAlive options, like keepAliveMaxtime help on your use case ?

[OneB1t]

@mloiseleur We started with keepAliveMaxtime at 0 (which was default) and now we set it to 30 sec and it still behaves the same so no impact

[rtribotte]

Hello @OneB1t,

Thanks for your interest in Traefik!

Could you please share a minimal reproducible case? (client cmd/configuration and Traefik static and dynamic configuration)

[traefiker]

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.I have to close this one because of its lack of activity :disappointed:Feel free to re-open it or join our Community Forum.