Jamf Migrator 503 Error

mwagner
New Contributor II

Hey all,

Anyone with experience using the JAMF Migrator tool experienced the 503 error? My destination server (currently a sandbox for v10) is putting out that error. URL & login credentials are correct. See attached screenshotd7fa3017db934338b7719e620dfd022b

11 REPLIES 11

leslie
Contributor II

Hoping by now you've resolved the issue. Only time I've hit the 503 error is when the set-up wizard (entering activation code, creating first account...) has not been completed. If yours was a different issue perhaps you could share and help others running into the same thing.

Matt
Valued Contributor

I am having the 503 error myself except it is telling me to verify I can access the API. Username, Pass, and URL's are all correct but no dice!

leslie
Contributor II

Which version of the app are you using? What does the following give when run in Terminal?

curl -sku yourAdmin https://your.jamf.server:port/JSSResource/buildings

mark_mahabir
Valued Contributor

Did anybody get any further with this?

I'm using the latest version of migrator from https://github.com/jamfprofessionalservices/JamfMigrator/releases/download/current/jamf-migrator.zip

And the error message is:

**Service Unavailable**

Verify you can manually log into the API:
https://whatever.jamfcloud.com/api
Error: 503

I've gone through Setup Assistant, and can log into the web interface as expected...

leslie
Contributor II

I've seen this a number of times shortly after completing the setup assistant on cloud hosted servers. After about 20 minutes the error has gone away. Still having an issue?

mark_mahabir
Valued Contributor

@leslie Yes, I left it a few hours but still getting the same error.

leslie
Contributor II

@mark.mahabir - Safe to say the curl command (couple posts back) works? For more verbose output use:

curl -vku yourAdmin https://whatever.jamfcloud.com/JSSResource/buildings

mark_mahabir
Valued Contributor

@leslie Yes, all looks fine - no errors there.

mark_mahabir
Valued Contributor

Strange, all seems to be just fine now when I returned to this a few days later....

leslie
Contributor II

@mark.mahabir - thanks for the update.

philipwoods
New Contributor III

We get exactly the same behaviour.

We're an MSP using Jamf Pro so have to spin up new cloud instances all the time and populate them with policy etc from a template JSS. After activating a Jamfcloud instance the migrator tool never works straight away.

We sometimes have to leave it for a couple of days before it will work, but it always does eventually.