January 29, 20188 yr After I upgraded to 6.4, I noticed the new web terminal feature. Super slick and it worked no problem for me... until today. I'm not getting a window that tells me "login incorrect' then bails. I'm logging in as root. This worked fine yesterday so not sure what happened... my credentials didn't change. Any ideas? Looking at the logs, i see this: Jan 28 21:18:57 Tower login[15600]: ILLEGAL ROOT LOGIN on '/dev/pts/8' Again, this used to work before so not sure why root login is denied now. Edited January 29, 20188 yr by tmchow
January 29, 20188 yr What browser? Also if you can access a terminal locally run ls -la /boot/config/ssh and check your SSH keys aren't corrupted and 0 bytes. Also, not to be THAT guy, but you tried turning it off and on again? A browser cache might be helpful too.
February 17, 20188 yr I'm totally new to unraid (but not Linux), just installed 6.4.1. Was having the same problem, fixed it by adding pts/8 to the end of /etc/securetty. No idea why it's broken in the first place though.
February 17, 20188 yr Definitely something wrong, adding entries to securetty is only a quick fudge as the numbers increment. No issue with 0 byte/corrupted ssh keys either from what I can see.
February 17, 20188 yr I just had a thought, could it be that the 8 preclears I'm running (via plugin) took up pty 0-7, and maybe they didn't anticipate that? Wonder what would happen if I tried to run another preclear...
February 17, 20188 yr Very possibly. If you really want to run that many at once, I'd advise not using the plugin, rather use the patched script at the command line and use screen sessions to manage them. Much cleaner. However... I've seen multiple people have issues running that many preclears at once, I wouldn't be surprised if your server falls over or freezes at some point with that many running.
February 17, 20188 yr Thanks. Seems to be working fine so far at least, will see if it finishes. I just checked with who and they're not using up pty's, so it's not related to the web terminal problem at least.
February 17, 20188 yr Never mind, I was right the first time. lsof shows that the preclears are in fact using up ptys.
February 28, 20188 yr I had the same issue with preclear, had to kill tmux to get the weblogin to work again...
March 30, 20188 yr I have the same problem, I can access with SSH but if I open the web terminal I get this error in the log Mar 30 22:27:58 MediaCenter login[30658]: ILLEGAL ROOT LOGIN on '/dev/pts/9'Mar 30 22:28:13 MediaCenter login[30785]: ILLEGAL ROOT LOGIN on '/dev/pts/8' Same issue in chrome and firefox, all I did between working and not working was to create a win 10 VM
March 31, 20188 yr 7 hours ago, L0rdRaiden said: I have the same problem, I can access with SSH but if I open the web terminal I get this error in the log Mar 30 22:27:58 MediaCenter login[30658]: ILLEGAL ROOT LOGIN on '/dev/pts/9'Mar 30 22:28:13 MediaCenter login[30785]: ILLEGAL ROOT LOGIN on '/dev/pts/8' Same issue in chrome and firefox, all I did between working and not working was to create a win 10 VM You have too many ptys open. Apparently each qemu (VM) uses one up to provide a serial console to the VM. You likely have some combo of 8 total VMs+web terminals+preclears running. Other than closing some of them, the other option would be to allow more ptys to be used for a root login by appending lines like pts/8 pts/9 pts/10 pts/11 etc. into /etc/securetty. Removing /etc/securetty entirely also accomplishes this, but I don't claim to understand the security implications (if any) of doing this.
March 31, 20188 yr 5 hours ago, psm321 said: You have too many ptys open. Apparently each qemu (VM) uses one up to provide a serial console to the VM. You likely have some combo of 8 total VMs+web terminals+preclears running. Other than closing some of them, the other option would be to allow more ptys to be used for a root login by appending lines like pts/8 pts/9 pts/10 pts/11 etc. into /etc/securetty. Removing /etc/securetty entirely also accomplishes this, but I don't claim to understand the security implications (if any) of doing this. How do I close some of them without restarting unraid?
Archived
This topic is now archived and is closed to further replies.