#Mac os ssh client update#
#Mac os ssh client pro#
#Mac os ssh client software#

I don't want to end up on Hacker News again bitching about Catalina. But I don't know what difference connecting via the hostname versus the IP address would make when specifically using a non-standard port above a certain threshold. I would love to be proven wrong and told I'm an idiot. Am I and this one other forum poster just doing something totally bizarre yet the same? This ssh setup has been working for years for me until just the last week. The internals of this is all so incredibly above my head I have no idea what the underlying problem might be. They both connect fine, while the host machine continues to fail. Just to verify, I boot up a Mojave and Catalina (10.15.3) VM on the same iMac. At least in my case, my one server that happened to be running on a non-standard ssh port above 8192 will not connect from Catalina 10.15.4 when using the hostname instead of the IP address. I changed the server to listen on standard port 22 and tried connecting via the hostname once again. So, I tried ssh ip-address -p9944 and it worked! (That server runs on an alternate ssh port.) Up until this point, I was connecting via a saved hostname defined in my ~/.ssh/config, which let me login simply by tying ssh some-server. Yes, I do change the port on the server side prior to every test.

#Mac os ssh client update#

This issue started just after upgrading to macOS Catalina 10.15.4.ДЄfter that update I am no longer able to open a SSH connection to a port greater than 8192 using server name (instead of IP). Totally grasping for straws I google for '10.15.4 ssh' and find this top result on the Apple discussion forums:Д¬atalina 10.15.4 SSH port > 8192 does not work when using server name instead of IP My laptop is still on 10.15.3 - and, of course, the virtual machine isn't macOS at all. This all started around the time I updated my iMac to 10.15.4. I start trying to think what could possibly be different about this one machine. I can connect from my iMac if I jump through any other server, first.I can connect to other servers from the problematic machine - both at the same hosting provider (Linode) and others (AWS and DigitalOcean).I've verified my ssh keys are correct and have the appropriate permissions.I've connected successfully from behind the same public IP using a laptop, a virtual machine, and my iPhone and iPad.My iMac is the only machine that cannot login.Just a cable modem and a router.) So, I login to the VM, try and connect, and it works fine. (To be clear, my home network is perfectly ordinary. That will rule out if there's just something odd about my iMac's LAN IP. I'll ssh into it and then try and connect. I think about it for a few minutes and then - aha! - I have an Ubuntu virtual machine running on this iMac inside Parallels. So, I blow away ~/.ssh and recreate all of my keys from a backup. At this point I'm thinking maybe the permissions on my local private key got screwed up. Next, I ssh into a different server and then hop to the problematic one. So, it can't be that my home IP address got mistakenly banned somehow. They're both on the same wifi and thus the same IP.

#Mac os ssh client pro#

My MacBook Pro is at home right next to my iMac, which is refusing to login. I try connecting from my laptop, and it works. Also, SequelPro is able to connect to MySQL via ssh as well.ДЄnd then things get even stranger. I'm able to connect using ForkLift - my FTP client, which connects via SFTP. I reboot the server itself and the problem persists. I waited 10+ minutes and it never timed out or produced any other output. That's the ssh output with the verbose flag. Ok, did sshd somehow become unresponsive? I login through the Linode control panel and restart the service. And, yes, it was still up and running and serving web traffic. When it goes down, I get worried.ДЄt first I thought maybe the server was down? I hadn't received any alerts, so I did a quick check.

#Mac os ssh client software#

It's sort of the linchpin for my tiny software company. I don't have an exact date, but within the last week I realized that I was unable to ssh into my primary web server - the one that runs my business website, activation server, etc. I was completely at my wit's end and feeling like I had lost my mind until about a half hour ago.