Websocket pings #9590
Replies: 5 comments 1 reply
-
Can you add configuration for this? |
Beta Was this translation helpful? Give feedback.
-
Yes please, console is dropping so quickly. |
Beta Was this translation helpful? Give feedback.
-
If I'm using nginx proxy for portainer with
console works, but nginx closes connection after 60 seconds. According to Nginx documentation it is default value for websocket. But it also says:
Please, add websocket ping to solve this problem |
Beta Was this translation helpful? Give feedback.
-
Did this ever get resolved or did anyone manage to find a workaround? |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
When behind a reverse proxy, the websocket that powers the built in console can easily time out when it's sitting idle because there are no keepalive pings or any active traffic. Mature reverse proxies allow you to manually increase timeouts so that the console doesn't disconnect after a common default of 60s, but places such as cloudflare has a max limit of 100s which makes the console UI unusable if you leave it for a small moment.
Describe the solution you'd like
Built in ping/pong traffic between the browser and portainer server for websockets.
Describe alternatives you've considered
N/A
Additional context
N/A
Beta Was this translation helpful? Give feedback.
All reactions