SSH not working as it did before 22.01 upgrade
-
I've been reading posts and the blog... but that doesn't mean I'm reading the right things.
So I come here after trying. Everything is working fine on my 22.01 upgrade except SSH. Keys no longer accepted. No problem, I was running an older version of Putty so I updated it and regen'd the public and private keys, and reconfigured Putty to the new pvt key. Now I connect just fine but all I get is a command line, not the serial output menu (sg4860) with the 16 config options. It's as if the number "8) Shell" is already selected. But unlike before when I could "exit" the shell and go back to the menu, if I type exit, it drops the connection altogether. I've got a fall back option for now but I'd really like to get this working again. Have I missed a new config item? Any help would be appreciated.Thanks,
Rick -
@ramosel I can tell you that I have been ssh in since upgrading to pfSense+ no problem, and just now seeing your post...maybe delete that putty, reboot, and install fresh one then SSH in again.
-
@ramosel what account are you logging in with? admin?
Works fine here..
-
@johnpoz said in SSH not working as it did before 22.01 upgrade:
Works fine here..
Using my admin account. The "factory" admin account is disabled. Has been for years.
Are you using the latest Putty... 0.76?
John, Thanks to you, my fallback is working until I get this fixed. I still run the Raspberry Pi with the screen command you helped with to access the SG-4860 locally. For now I just SSH the RPi and run screen.
-
@ramosel said in SSH not working as it did before 22.01 upgrade:
Using my admin account. The "factory" admin account is disabled. Has been for years.
Well other accounts are not going to run the script that brings up that menu.. Lots of threads about that around here, and how to get it to run when you login.
-
Custom accounts never get the menu because they don't have privileges to use most of the options.
If you saw the menu when you logged in with a custom account you probably changed something in the account's shell files (e.g.
.profile
or similar) and those may have been overwritten in the upgrade.You'll need to make whatever customizations you made again.
-
@jimp said in SSH not working as it did before 22.01 upgrade:
Custom accounts never get the menu because they don't have privileges to use most of the options.
If you saw the menu when you logged in with a custom account you probably changed something in the account's shell files (e.g.
.profile
or similar) and those may have been overwritten in the upgrade.You'll need to make whatever customizations you made again.
Now it's coming back to me... yep, actually, Chris helped me with that... I called about something in your book that didn't make sense. After he explained whatever that was he asked if I had any other questions and he was kind enough to walk me through adding those customiations. v2.1.2? Damn, I'll have to dig up my notes.
Speaking of Chris, I hope you all are still on good terms. How's he doing?
Rick
-
@jimp said in SSH not working as it did before 22.01 upgrade:
You'll need to make whatever customizations you made again.
John, Jim,
Thanks as always for your help, even if was just a nudge in the right direction. All back and working again.Funny those changes survived all the recent upgrades and the conversion to "+"... but this last one hosed it up.
Now to get my backup SG-4860 built with the fixed ZFS install.