There was a problem communicating with a push server

same here

Connection Settings Establish a connection to the Apple Push Notification service.
Protocol Apple will no longer support the binary APNs protocol. For more information, see the Supporting Apple Push Notification Service Over HTTP/2 Knowledge Base article.
Binary

edit: it works at least in one environment now. seems to be very slow everything in the moment

Same Problem here. I talked with Jamf Support moment ago. there is a problem with communicating between APNS and Jamf Cloud instances in EU Region.

Edit: the answer I got via mail: It looks like we do have an ongoing issues with APN's only on cloud instances not for on-prem.

Same here. (In South Africa)

We were experiencing issues enrolling devices through DEP, manual enrolments and config profiles not deploying too so issues with APN's makes sense. We're in the EU region. I've successfully enrolled one Mac now so hopefully it's getting fixed now.

UK also, very slow, but some commands are getting through

We're having the same issue - none of our devices are updating in the inventory... reset iPads aren't getting their Pre Enrollment either

Still having the same issue (UK) here too.
Edit: Saturday 22/8 9:00 GMT - We're getting traffic now, config profiles are getting pushed OK.

Is anyone else seeing this with manual enrolments at the moment? We can install the CA certificate, then install the MDM profile and then nothing happens after that. No configuration profiles, no Jamf binary and no self service app.

@RobertPetrie we see exactly the same behaviour.
edit: working now for us

Hi,
still experiencing issues with profiles not being pushed...
At least in Austria it seems to be stuck since Friday last week.
New DEP installed devices do not get most of the profiles we push.
Edit: we are on On-Prem v10.23 and use already the HTTP/2 (443) setting for connection. When testing I get an error.

eu-central-1 APNS
New incident: Investigating
We are observing higher APNS traffic volumes and intermittent failures for customers located in eu-central-1. We are investigating the issue.
https://status.jamf.com/incidents/2mdstr7s0px0

Same here aswell, been happening for the past couple of days. What is going on and better, what can we do to let it function normal again. We cannot work around this

Same problem here (USA - Florida)

Same problem for me, East US

Same problem here in Texas. We noticed a syncing issue last week and it is ongoing. We are on-prem.

Same here...in California

I don't know if it's related, but I am trying to renew the ABM server token for our on-prem JSS and if I try to upload it says "the file received was not valid". The Automated Device Enrollment page in JSS says "Information out of date. Awaiting next sync"
Test with TwoCanoes "Push Disgnostic" seems fine (APNs tests completed with 63 passed and 0 failed)

@carlo.anselmi (and everyone else posting on this issue) What version of the JSS are you running?

@sdagley sorry forgot to mention it's JSS 10.17.1-t1574185757 on prem

Hello, having this same issue in US East

Running 10.23.0-t1595614145, and we just renewed our Push Notification Certificate earlier this summer

Since this issue is being reported across multiple versions, and impacts both on-prem and AWS/Jamf Cloud hosted instances, it'd seem like this is an Apple issue. Not that https://developer.apple.com/system-status/ has any indication things aren't working.

Hello from Austria :)
still experiencing the issue here.
We use on-prem JSS 10.23.0-t1595614145

Just checking in; anyone else experiencing profiles being installed due ADE/PreStage enrollment are looping and taking ages?

@txhaflaire yes we have the same issue...what we already found out is that when you "cancel all" pending and failed commands the loop is solved and device continues to "time zone" selection.

@txhaflaire & @patrick030 Yes, we are facing the same issue. DEP enrollments are stuck on a loop, in our case directory binding is failing & after almost 10 minutes, the Computer hangs. We did a force reboot & again it gets in the same loop. When I check the computer record on Jamf, I see an Unmanaged entry & multiple failed commands for Directory Binding. Informed Jamf Support, waiting for their reply.