Connection failure: "The operation couldn't be completed. (Error 502.)"

im seeing this on some computers all of a sudden too

I second this as well.

@Mateo137 Do you have a ticket open with JAMF on this or have you got any more info on your situation?

@CorpIT_eB @hdsreid @Mateo137

Have you gotten a resolution to this? We started seeing this just after moving the a jamf cloud instance last week. I've opened a ticket with Support but they can't finding anything yet.

Im getting the same error when uploading pkg files. Seems to be very random. Opened several tickets, when I do they do some tweaking and then it works for a bit but will fail again.

I'm seeing this error during recon on several of our machines as well. Did anyone ever get a resolution?

I'm seeing this on a few too

did this get resolved - now seeing also

ill add to this that ive been seeing it sporadically for a bit.

1 of a few things can happen, and ill list in them from least to most common:
1. either it fails the recon, and actually fails, then it says it will upload the data on next check in. probably internet related, but 1/100
2.recon fails with the 502, but if you refresh JSS itll show the updated info (i can only verify on the 2 EAs that im keeping an eye on) - 1/20 or so

maybe just a glitch, maybe a fluke, but 99%+ of the time, at least it seems to me, the recon is actually going through.

granted, im us-east-1, so im getting maintenance for at least another 3-4 hours.
maybe thatll fix something.

on that note, does plist changes in config profiles work for you guys?
i see the option to choose the jamf stuff along with what version mau, but when it comes to the actual plist settings, its blank :(

I am getting it too, sent in trouble ticket to JAMF.

any update on this any one?

I'm getting this often as well!

I am having the issue as well and is affecting my whole provisioning workflow.

Same issue also for me with a script "sudo jamf recon" on the Self service... I don't know why

Same issue while uploading a small pkg. Any resolve?

Has anyone resolved this? Seems to be part of an issue we are having with devices not checking in.

Same problems here since this morning...

Hey all! Has anyone successfully worked through this with Jamf support? Seeing it on a sizable chunk of devices over the past week. Have a ticket of my own open, but thought I'd check with the hive mind as well 🙂 

There hasn't been a solution since I posted this. To be honest I stopped seeing the issue but I don't doubt that it still happens for others.

@landonletzkus Let us know what JAMF support comes up with on the ticket that you have open.

Any news for this issue ?

have the same issue trying to jamf recon -assetTag 

We've developed this issue as well. It's causing issues with JAMF Admin logins, device enrollments, and recons. Case opened to support. 

Ditto we have the same issue cant enroll new laptops or re-enroll freshly wiped machines.. recon throws back a 502 error.. jamf support hasn't gotten back to us .. Our instance is completely unusable. 

 I have created a Case for the support they are having the cloud support team run queries. I post their solution.

 We are also experiencing self-service issues.