Backup: restore a backup - A server problem is blocking Apple ID sign in
Updated on Apr 22, 2026
Reading time ~4 minutes
After restoring a backup, iOS prompts you to sign in to your Apple Account during the Setup Assistant. In some cases, this step fails with the following error:
Could not sign in. A server problem is blocking Apple ID sign in. Try again later.
This is a known iOS bug, present since iOS 5 and never resolved by Apple. It is not specific to iMazing: it can occur after any restore performed via Finder, Apple Devices, iMazing, Quick Start, or iCloud. The root cause is a conflict in Apple's device registration service: after a restore, Apple's servers may still see the device under its previous state, with Find My active or a stale authentication token, which blocks the sign-in request.
The solutions below are ordered from least disruptive to most involved. Try them in sequence.
Skip Apple ID sign-in
If the Setup Assistant shows a Set Up Later in Settings option below the sign-in prompt, select it.
Once setup is complete, open the Settings app on your device, tap your name at the top (or Sign in to your iPhone/iPad), and sign in to your Apple Account from there.
Note: Signing in from Settings after setup is fully equivalent to signing in during the Setup Assistant. No data or functionality is affected.
If the Set Up Later in Settings option is not visible, proceed to Step 2.
Enable Airplane Mode during setup
Enabling Airplane Mode before the Apple Account sign-in step forces iOS to skip server authentication entirely. You can sign in after setup is complete.
Enable Airplane Mode
At the Apple Account sign-in screen, swipe down from the top-right corner of the screen (or up from the bottom on older devices) to open Control Center, then tap the Airplane Mode icon.
Complete setup without signing in
With Airplane Mode enabled, select Set Up Later in Settings or skip the sign-in step when it appears.
Continue through the remaining Setup Assistant screens.
Sign in to your Apple Account from Settings
Once setup is complete:
- Disable Airplane Mode to restore your internet connection.
- Open the Settings app.
- Tap Sign in to your iPhone/iPad at the top of the screen.
- Enter your Apple Account credentials and complete sign-in.
Remove the device from your Apple Account
Apple's server conflict can be resolved by removing the device from your Apple Account before or after the restore. This clears the stale registration and allows a clean sign-in.
Important: Removing a device from your Apple Account disables Find My for that device. Re-enabling Find My after sign-in restores protection.
Remove the device from another Apple device
- On a trusted iPhone, iPad, or Mac, open Settings (or System Settings on macOS) and tap or click your name.
- Scroll down to the list of devices linked to your account.
- Tap the device you are setting up.
- Select Remove from Account and confirm.
Remove the device via account.apple.com
- On a Mac or Windows PC, open a browser and go to account.apple.com.
- Sign in with your Apple Account.
- In the Devices section, locate the device you are setting up.
- Click Remove from Account and confirm.
After removing the device, return to the Setup Assistant and attempt to sign in again.
Erase and set up again
If none of the above solutions resolves the error, a double-erase sequence can break the conflict.
Important: This process erases all content on the device twice. Your data remains safe in your backup, but complete the process carefully before restoring again.
- Complete the Setup Assistant without signing in to your Apple Account (use Set Up Later in Settings or skip).
- Once on the Home Screen, open Settings > General > Transfer or Reset iPhone/iPad.
- Select Erase All Content and Settings and confirm.
- After the device restarts and returns to the Setup Assistant, proceed through setup normally and sign in to your Apple Account when prompted.
- Once signed in and setup is complete, restore your backup.
This sequence forces Apple's servers to recognize the device as freshly registered, clearing the stale token that caused the original error.
Prevent this issue in future restores
The conflict originates on Apple's servers, but one factor that contributes to it is Find My remaining active on the target device at the time of restore. Erasing the target device before restoring removes Find My registration and reduces the likelihood of the conflict occurring.
In iMazing (macOS and Windows), an option is available during the restore workflow to erase the target device before the restore begins. Enabling it is recommended when restoring to a device that was previously associated with an Apple Account.