Keeping the browser terminal session connected

[robi]

@Kubernetes TY, I made it clearer in the OP.

@necrevistonnezr Thanks for the hint. I am trying out the Staying Alive extension to see if it does the trick for the domain or just the terminal sessions.

[robi]

No go so far with the extension.

Console log shows:

Uncaught Error: Could not dispose an addon that has not been loaded
    at Proxy._wrappedAddonDispose (terminal-BYZevxTX.js:8:31585)
    at l.dispose (terminal-BYZevxTX.js:8:31403)
    at WebSocket.<anonymous> (terminal-BYZevxTX.js:9:1319)
terminal-BYZevxTX.js:9 Socket closed. Reconnecting...
cs.js:65 

[nebulon]

Do you happen to have anything like Cloudflare proxy in front of your system? Maybe that gets into the way?

[robi]

@nebulon No, CF is DNS only.

[nebulon]

Then I am out of ideas without further error details, something seems to pause/disconnect the websocket connection.

[robi]

Not sure what else to provide other than flip the script and revisit the OP asking what can we do to make the browser keep thinking it's alive? Send NOOPs?

[fbartels]

Do other solutions, like for example guacamole suffer from the same issue?

I think i am personally leaning towards using the cloudron cli, as this way I can use tmux for persistence and can even share the session. I had tabs crashing because too much memory was used and a reload will always start a new session.

[corsacca]

Using worpdress managed app, after ~90 seconds of inactivity the terminal resets and shows "Reconnecting..." and then the first line.
I can be trying to write a mysql query and loose all progress.
I'd love a solution to keep the session live.

[nebulon]

@corsacca since we have no timeouts on our side, do you have any proxying services or something in front of your Cloudron, which may terminate the connection on inactivity?

[corsacca]

Sorry, i should have checked that first.
Downgrading CF proxy to DNS only does seem to fix the issue for me.
Thanks @nebulon.