portainer: container console freezes when using other apps or windows in the browser
Steps to reproduce the issue:
- open container console in portainer in chrome
- change to another tab or any application 3.return to console gets frozen, not able to type anything have to open new console
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:
- Portainer version:1.13.2
- Target Docker version (the host/cluster you manage):17.05
- Platform (windows/linux):windows
- Command used to start Portainer (
docker run -p 9000:9000 portainer/portainer
): - Target Swarm version (if applicable):1.13
- Browser:chrome
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 20 (5 by maintainers)
Commits related to this issue
- feat(app): added Input components [EE-2007] (#995) — committed to portainer/portainer by cheloRydel 3 years ago
Pretty sure the issue here (at least when NGINX is involved) is the
proxy_read_timeout
setting. For a long running socket connection like a websocket, if nothing is read from the proxied connection after 60 seconds (default) the connection will be closed. Once closed, there doesn’t seem to be any reconnect code on the client side, so the console is basically “dead”. I just bump up the setting to 7 days for the websocket path. Nothing lives on my desktop longer than that 😉Thank you @Codelica ,
proxy_read_timeout
is the answer