Why does my Remote Access seem to stop working?

Problem: My password is no longer accepted.

Remote Access is technically based on a serial connection. In some environments, a successful connection may change the properties of the local terminal. As a result, a new login fails due to an allegedly wrong password. And this although – or just because – the password was passed via copy/paste as before. To fix the problem, your Notebook terminal must be reinitialized. In Linux and Mac OS this can be done very easily by typing reset. Alternatively, the terminal window can be closed and reopened.

Example: Reinitialize your terminal via “reset” command

Problem: Copy+Paste (or other) actions freeze sometimes my session.

Remote Access is technically based on a serial transmission which unfortunately is always a bit bitchy. The connection quality depends on the terminal settings and many other parameters. Tools like interactive editors that intervene deeply in the environment configuration are sometimes a challenge in this context. This is also why Remote Access is generally only intended for situations in which a regular login is no longer possible due to a faulty configuration. Otherwise, access should always be made via SSH or similar services of your colocation computer.

The standard version of nano in particular is known to cause serial disconnections when copy+paste actions are used, see e.g. this very old congeneric screen bug. But there is a workaround: The –enable-tiny compile flag disables many functions that can potentially interrupt a serial connection. Most distributions contain such a stripped down nano version as package which can be installed additionally. Please see this wiki page for configuration instructions.

If you can’t reach your colocation computer via SSH or other remote protocols and your Remote Access is also frozen, there are two options left: If you have booked the USB Power Connection Incl. Remote On/Off option, you can restart your system at any time. Otherwise you must unfortunately create a ticket to request remote hands.

Problem: Multiple parallel connections are not possible.

This is not a bug, it’s a feature. As described, Remote Access is technically based on a serial transmission. Parallel connections via a serial interface often lead to unexpected and therefore confusing behavior. Therefore, multiple logins are not allowed and are rejected by our SSH service.

Example: Multiple parallel connections are not allowed

Please note again: Remote Access is generally only intended for situations in which a regular login is no longer possible due to a faulty configuration. Otherwise, access should always be made via SSH or similar services of your colocation computer.

Leave a Reply