Skip to main content

Self Service Error - Can't Connect to Server after Jamf Pro Re-enrollment

Updated over a month ago

Issue Description

Users are unable to log into Self Service. They are seeing the following error when opening Self Service "can't connect to server."

Self Service logs are showing the following error related to the server connection issue: [] Device not enrolled - Attempting to enroll app.
​

Computer was re-enrolled without removing the old Jamf Framework, leaving both "com.jamfsoftware.selfservice.publickey and com.jamfsoftware.selfservice.privatekey" behind in the keychain.

Troubleshooting Steps

  1. Send Unenroll command from Jamf Pro.

  2. Confirm MDM profiles are removed.

  3. Manually delete any com.jamfsoftware.SelfService.privatekey or com.jamfsoftware.SelfService.publickey under Local Items in Keychain Access.

  4. Ensure /Library/Preferences/com.jamfsoftware.jamf.plist doesn't exist on machine

  5. Re-enroll via Terminal using the command sudo profiles renew -type enrollment

Related Articles
Using profiles -type enrollment commands with Jamf School
Computers not enrolling into Jamf School using Automated Device Enrollment
Re-enrolling a Mobile Device in Jamf Now that was Previously Enrolled using a Different APNs
When Jamf Now deploys Self Service it displays "Cannot reach a Jamf MDM server"
Troubleshooting Automated Device Enrollment
Did this answer your question?