Hello all,
I have the following problem with a terminal-in-a-browser application ("ttyd") on a Raspberry Pi 2 (32bit Raspbian 13 "trixie").
I know, this screams "it's an application problem, so don't ask here and don't blame it on the OS!" - but hear me out, please![:)]( "Smile")
I have already created a support issue [https://github.com/tsl0922/ttyd/issues/1489] on the project's GitHub page, currently waiting for a response.
But then I'm not completely convinced that the problem is not with the OS (or rather my attempt at configuring the OS correctly). So here it goes...
Running ...
... on my Raspberry Pi should give me a login prompt in a web browser connected to http://myinternalip:7681
However, there is no "login" prompt, just a plain cursor prompt, no other output. Yet it appears that the login procedure is actually present, because when I (blindly) enter username <return> password <return>, a new session is apparently established (as verified with the "w" command from another session); and a new /dev/pts device is created, and it is removed again when I (blindly) type "exit". But this session is obviously of not much use, as there is no visible input/output on the screen.
(Note: I had to add the user account running ttyd to the "tty" group in /etc/group to avoid access errors in /dev/pts)
What does work, however, is skipping the login procedure (with an entry point directly into bash) like so:
i.e. I get a proper shell prompt and can see all input/output on the screen. However, this approach is clearly not feasible for a server publicly accessible on my network. But yet it proves that the armhf build of ttyd is generally working as expected.
In contrast, I also have another ttyd installation running on a Raspberry Pi 5 which works just fine in login mode. So, I wonder what the key difference is between these 2 configurations (see below for version details).
Long story short: my gut feeling is that the bash shell I/O is somehow not properly "attached" to the /dev/pts device - for lack of a better term.
I only have limited knowledge of how pseudo terminals work (or even how the login process actually works), but perhaps someone here has any ideas? Does this sound to you like a software problem in ttyd or more like a Debian configuration issue?
Version details of the failed configuration:
Thank you for reading this far.
Any hints would be greatly appreciated.
I have the following problem with a terminal-in-a-browser application ("ttyd") on a Raspberry Pi 2 (32bit Raspbian 13 "trixie").
I know, this screams "it's an application problem, so don't ask here and don't blame it on the OS!" - but hear me out, please
I have already created a support issue [https://github.com/tsl0922/ttyd/issues/1489] on the project's GitHub page, currently waiting for a response.
But then I'm not completely convinced that the problem is not with the OS (or rather my attempt at configuring the OS correctly). So here it goes...
Running ...
Code:
sudo ttyd.armhf -W loginHowever, there is no "login" prompt, just a plain cursor prompt, no other output. Yet it appears that the login procedure is actually present, because when I (blindly) enter username <return> password <return>, a new session is apparently established (as verified with the "w" command from another session); and a new /dev/pts device is created, and it is removed again when I (blindly) type "exit". But this session is obviously of not much use, as there is no visible input/output on the screen.
(Note: I had to add the user account running ttyd to the "tty" group in /etc/group to avoid access errors in /dev/pts)
What does work, however, is skipping the login procedure (with an entry point directly into bash) like so:
Code:
ttyd.armhf -W bashIn contrast, I also have another ttyd installation running on a Raspberry Pi 5 which works just fine in login mode. So, I wonder what the key difference is between these 2 configurations (see below for version details).
Long story short: my gut feeling is that the bash shell I/O is somehow not properly "attached" to the /dev/pts device - for lack of a better term.
I only have limited knowledge of how pseudo terminals work (or even how the login process actually works), but perhaps someone here has any ideas? Does this sound to you like a software problem in ttyd or more like a Debian configuration issue?
Version details of the failed configuration:
- Raspberry Pi 2 (32bit)
- Raspbian 13 "trixie"
- ("Lite" install, no GUI)
- kernel 6.12.47+rpt-rpi-v7
- ttyd version 1.7.7-40e79c7
- Raspberry Pi 5 (64bit)
- Debian 12 "bookworm"
- (full Desktop install)
- kernel 6.6.31+rpt-rpi-2712
- ttyd version 1.7.7-40e79c7
Thank you for reading this far.
Any hints would be greatly appreciated.
Statistics: Posted by each — Fri Jan 16, 2026 12:41 pm — Replies 1 — Views 53