did you try a different client? maybe try removing the cert or make sure that the Credential Manager control panel doesn't have any entries for that system
this post was submitted on 20 Oct 2023
4 points (100.0% liked)
Self-Hosted Main
515 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
systemctl stop ssh&&/usr/sbin/sshd -ddd on the server, then try again
What software are you using to SSH from Windows?
I'm using default terminal, but I've tried connecting from putty as well and it didn't work.
You got Fail2Ban installed on your Linux host? Has it possibly banned your Windows IP?
I've installed Fail2Ban before on this machine, but I've since uninstalled it. I've also checked sudo-iptables, and it doesn't show any rejected IPs.
Is is possible that Windows passkey is being used? Did you remove all traces of the sshd install. Also if your using Windows Terminal try putty.
Note the order of "(publickey,password)". I'm gonna guess publickey is being used before password.
Certainly seems like a Windows (client) problem and not a server problem.
How would I go about removing the sshd install traces? I just used the powershell command for uninstalling the server that was provided in this page (but this wouldn't be the first time Microsoft has screwed me over.): https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse
I've tried putty, it hasn't worked.
Check your logs /var/log/auth.log. You can pipe grep it to search by IP or just try to connect then quickly check. That might give you more insight that isn't being provided to the remote client (windows).
Doesn't seem like there are any logs.
Check storage if it’s full, if it cannot audit your login it won’t let you.
When you say your Windows machine is getting an external ip, is it an actual external ip or that it's the 169 address that your machine gets when it can't speak to your dhcp server?
Can you access the Internet or any other services on your Windows machine?
Fwiw he wouldn't get a public key password denied type error if he wasn't able to at least reach the target, to my knowledge.
It was my actual external IP.
I could access the internet and everything just fine, but when I tried to connect to Jellyfin or anything that my other machine is running it wouldn't work. The issue is resolved now.
Connect with more v(erbose) output to your server. Example:
ssh -vvvv @
... and read line by line.