Skip to main content
Question

Enrolling with management server Failed (502)

  • May 11, 2026
  • 5 replies
  • 169 views
A
Forum|alt.badge.img+9

Hi,

I really hope that someone here can help me with this. We have had this error for a few weeks now and I am getting a little desperate here. Jamf and Apple support have not been able to provide a solution either.

Some of our Macs are getting the “Enrolling with management server failed. An unexpected error has occurred <HTTPStatus:502>”. I know that usually means communication issues, but with those Macs that cannot be the case because I can enroll different Macs under the exact same circumstances without any problems. Same time, same cable, same server, everything is the same. On the other hand those Macs always have that problem and it wont go away no matter what I do. I have already tried enrolling via a different network, moving them to a different site, enrolling them via a different PreStage enrollment and much more. Nothing worked. And really bad part is that this issue is spreading. At first only a hand full of my Macs were affected, but now almost 50% of the Macs I try to enroll get this error and once they have it will not go away. 
Anyone got suggestions what I could try? Because I'm really out of ideas and neither Apple nor Jamf support can find the issue.
 

    5 replies

    Left
    Forum|alt.badge.img+4
    • Left
    • Contributor
    • May 14, 2026

    Sorry, I may mention some duplicates that you have checked.

    Is it local or jamf cloud in your environment? If it is a local server, when the device is connected to Jamf, will they pass through those firewalls, such as WAF? Maybe WAF will review the traffic, which will bring you strange problems. In addition, about your problem to http status code 502, in my impression, this is an old There is no effective solution to the problem.

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • May 14, 2026

    My suggestion is deleting the existing inventory records for those devices. There could be something corrupt in the database record that is causing this.

    A
    Forum|alt.badge.img+9
    • Andixon
    • Author
    • Contributor
    • May 14, 2026

    Hi,

    ​@Left 

    no problems. At this point I am happy for anyone who is trying to help. It is an on premise version of Jamf Pro. The thing is, can it really be a firewall issue if some Macs have this problem and some dont?

     

    ​@AJPinto Unfortunately I have already tried that with no effect.

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • May 15, 2026

    Hi,

    ​@Left 

    no problems. At this point I am happy for anyone who is trying to help. It is an on premise version of Jamf Pro. The thing is, can it really be a firewall issue if some Macs have this problem and some dont?

     

    ​@AJPinto Unfortunately I have already tried that with no effect.

    Other high level things to check:

    • what prestage the device is scoped to? Make sure its scopped to the one you are expecting it to be scopped to.
    • Try a different network. Rule out the possibility of a NAC block or something specifically targeting the devices MAC address. 
      • You could try unassigning the device from Jamf in ABM, activating macOS and installing the Mac Evaluation Utility or JET and running a test checking all the hosts and ports needed for MDM to work (JET is better for an unenrolled state) and see if any obvious blocks or TLS filters show up.
    • Finally, it may be time to open a ticket with Jamf. Deleting the inventory record usually resolves any database issues, but it is possible for one to persists depending on what exactly the issue is. Other high level things to check are what prestage the device is scoped to.

     

    Going deeper from here you really want Jamf Support, and ideally an engineer.

    • Put Jamf in verbose logging mode, and pull logs from the time the enrollment failed.
    • Grab the tomcat and Catalina logs off the server, and review the logs for the time of the enrollment failure.
    • If you are still running dry on what the issue is all the next steps I have would be in the database which you will want JAMF supports help with.

    502 is not a common error for Jamf, it usually suggests something network side is doing something stupid which is why I suspect something could be targeting that devices MAC address. Either way, this is Jamfs documentation on how to parse their logs that may be helpful.

    https://learn.jamf.com/r/en-US/technical-paper-integrating-ad-cs-current/Analyzing_Errors_in_the_JAMFSoftwareServer-log_File

      Left
      Forum|alt.badge.img+4
      • Left
      • Contributor
      • May 18, 2026

      Hi,

      ​@Left 

      no problems. At this point I am happy for anyone who is trying to help. It is an on premise version of Jamf Pro. The thing is, can it really be a firewall issue if some Macs have this problem and some dont?

       

      ​@AJPinto Unfortunately I have already tried that with no effect.
      From your description, there was an exception in combining the scenarios I encountered in my work with waf firewall redirecting or blocking requests.

       

      Terms & ConditionsAccessibility statement