CasaOS Terminal stops responding

Operating System CasaOS
,
1

I’m building some webpages on my ZimaBlade running with CasaOS. When I’m working locally on the same network where Zimablade is operating, I use ssh connection to enter through terminal. But sometimes I work out from home and I don’t want to enable port 22 on my router to access ssh from outside. So I use the integrated terminal window on CasaOs to access command prompt and continue working on my developments.

The thing is that I have to constantly close and login-open the terminal on CasaOs because it stops responding after a while. Normally if I stay some time (seconds) without writing anything on the prompt, it stops responding. But some others, I’m editing a file and suddenly it stops responding.

Is there something I can do to avoid terminal to freeze and constantly closing-login-opening when working with it?

Thank you!

2

The built-in CasaOS terminal is convenient, but I would not rely on it for long editing sessions. It runs through the web UI/browser session, so if the browser tab, websocket connection, proxy, login session, or network drops even slightly, the terminal can stop responding.

For quick commands it is fine, but for editing files or doing development work, I would suggest using a real SSH session instead.

If you do not want to open port 22 on your router, safer options are:

Tailscale

or

Cloudflare Tunnel

Both allow remote access without exposing SSH directly to the internet.

Another option is to install a web terminal such as ttyd or wetty behind authentication, but again I would avoid exposing it directly without protection.

Also, when editing files over a remote terminal, it is worth using tmux or screen. That way, even if the browser or SSH session disconnects, your work session can stay alive and you can reconnect to it.

For example:

tmux new -s work

Then if you disconnect, reconnect and run:

tmux attach -t work

So the short answer is: the CasaOS built-in terminal freezing is probably related to the web terminal session, not necessarily your ZimaBlade itself. For remote development, I would use SSH through Tailscale or Cloudflare Tunnel, and use tmux for anything important.

3

Hey! Thanks for your support!

I decided to go with Cloudflare Tunnel as I already had Cloudflare services attached to my Zimablade. I didn’t know how to configure it but chatGPT helped me with that :slight_smile:

So now I can access through ssh from Windows’ Powershell with no issues.

Thank you!

1 Like