Jamf Remote stuck at Opening SSH Connection

Good morning, sir,

Same problem, we try to change the mdp of a user with Jamf Remote, it blocks on the SSH part, while the port is open, I ping the address of the target Mac without problem ...

Thank you.

I have a ticket open around this, the only real response I've been given is that jamf remote doesn't work across subnet...nevermind this had never been any issue before

i found a "workaround" for the moment...if i ssh into the machine on terminal and then initiate in jamf remote, it will connect. strange, but at least it works.

I'm having the same issue.

I thought it was just me. Started happening about two weeks ago. 10.19.0

This is PI-008041.
Unable to SSH from Jamf Remote on 10.15.4 without Manually Accepting SSH Fingerprint.

Having the same issue, I have an open case and PI-008041 was mentioned by support but even after accepting the SSH fingerprint, Jamf Remote is not functional. I've heard the issue is resolved in Jamf Pro v10.21.0, but I can't confirm that.

I might be experiencing this as well as of today. I'm trying to use JAMF Remote to do nothing more than update inventory and it just hangs. In backtracking my steps I'm pretty sure that this was working fine up until the point that the 10.15.4 system rebooted. I can't say that with total confidence though.

Received from Jamf Support:

PI-008041
Description : Unable to SSH from Jamf Remote on 10.15.4 Beta without Manually Accepting
SSH Fingerprint
Steps to reproduce:
- Enroll a client in the JSS
- Download Jamf Remote on a 10.15.4 Beta host computer
- Open and authenticate into Jamf Remote
- Select the client from step 1 as a target computer
- Select any option (I attempted to install a PKG and DMG as well as run a script)
- Click 'Go'
Found during compatibility testing for the Spring Release. This will affect the first time any new
client is connected to via Jamf Remote from 10.15.4.
You must manually accept the fingerprint via Terminal to get Jamf Remote to Connect to any
client from a 10.15.4 host computer.
Expected Results:
- Jamf Remote connects to the client computer from the host via ssh
- PKG, DMG, and script are run against the client
Actual Results:
- Jamf Remote hangs at the "Attempting to SSH to client..." step
- PKG, DMG, Script never install
WORKAROUND: Manually accept the SSH Fingerprint for each client before using Jamf Remote
by doing
'ssh {user}@{client_ip}'

This is so ridiculous as it basically erased most of the Jamf Remote benefits (send tasks to managed machines in BULK using Jamf resources). Wasted the whole day pulling my hair out looking for the cause and fix. It's becoming more and more sensible to stay behind one major version for macOS in the enterprise environment.

@cbd4s thanks for clarifying some of this...
if its only impacting 10.15.4, it explains why only two of us have seen the issue in my environment lol

Thought it was just me as well but hadn't got around to logging another job for something all of a sudden not working any more. Around 10.15.3 and/or 10.19 is when I first noticed it.

I've been seeing this too and until this week we were on Jamf Pro 10.16.1. Clients I've tested on are Mac OS 10.13.6 and all the way up to 10.15.4. I'm still seeing this behaviour using Jamf Pro 10.20.1.

I'm not saying this is a solution to your problem, but, when manually trust (or not trust) a SSH connection, the text file you can nuke is user/user_name/ssh/known_hosts . Just delete everything in the file and save. Again, this probably won't help this specific problem, but it is a workaround I used to SSH into my Odroid when having a SSH problem.

I am having this same issue, started last week after updating to 10.15.4 on my computer (clients are all older OS). Makes Jamf Remote useless.

Has anyone updated to 10.21.0 and test to see if this issue was resolved?

Ok, I thought this was just me, so kind of relieved it’s happening to others. Jamf Remote is a must have in our environment, so until this is resolved we won’t be going to 10.15.4

@a.holley Push on Jamf to fix the issue or use the work-around. Don't hold back security updates.

10.21.0 has quietly fixed this issue!

This sounds like something I've experienced for a long time. When you've tested connecting, are you using the same credentials for your JAMF administrator account? For me the only resolution has been to delete the service account JAMF creates and recreate it.

@mvora confirmed fixed? i do not get upgraded until next weekend, and did not see it in the change notes either

@hdsreid Yes confirmed fixed in 10.21.0. But you don't need to actually upgrade your JAMF server, we're still on 10.17.1. Just the 10.21.0 version of Remote.

@ITFRANCE I have also confirmed that simply updating the Jamf Remote app to 10.21.0 resolves this issue, we are still running JamfPro v10.20.1

@mvora @mrheathjones awesome, didnt even think about that!

@ITFRANCE When using Jamf Remote 10.21.0 with Macs that have an older Jamf binary agent, such as 10.20.1, doesn't it generate an error that there was a mis-match between Jamf versions after installing packages or running scripts on the Mac?

@jhalvorson It sounds like Jamf Remote no longer does this.

From the 10.21.0 release notes:
"Jamf Remote no longer attempts to install or update the jamf binary on remotely connected client computers. "

Jamf Remote 10.21.0 doesn't fix the issue. We just began factory resetting our Macbook Airs to 10.15.5 and I'm unable to connect to any of them via Remote. Our JSS is also on 10.21.0.

Does anyone have any solid workarounds until Jamf fixes yet another issue that Apple created in the name of security?