Facetime is one of the most intuitive and reliable video calling apps in the world, which is a real pity when Apple keeps it to itself. Of course, no software is perfect, and now and then users can get the error “server encountered an error while registering error handling”. Usually at the time of least opportunity!
What does this error mean?
For a somewhat confusing error message, its meaning is quite simple. FaceTime is trying to sign you in to the service, but something is wrong in the process. This is especially annoying when you seem to be doing everything correctly. Using Apple ID works for everything else, but not on FaceTime.
Sadly, this one error can have many causes, which means you’ll have to rely a bit on trial and error to fix it. We will look at different possible fixes from the easiest to the most effortful.
The tips and tricks below are geared towards Mac users, if you’re having trouble on your iOS device, start here.
Is that really you?
Do not assume that in this transaction between your computer and the remote server, it is necessarily your computer that is the culprit. Try to check social media or Apple’s official channels for any signs of a service outage or some other general issue.
If other people are experiencing the same problem at the same time as you, then you should wait a while to see if the problem resolves itself.
Update, Update, Update
Yes, this is a basic, tedious piece of advice. However, running the latest version of macOS and having the latest version of Facetime can’t do any harm. Any issues that are causing this error can be resolved in newer versions of the software. That means you don’t have to try to fix the problem.
Restart your Mac and connect to the network, or try a different Internet connection
Perform a restart of your Mac and reset your router or another device that is providing internet connection. Just in case something weird is going on with your internet connection.
If resetting your internet connection doesn’t work, that doesn’t mean your internet connection isn’t the problem. Try using the device that is giving you the error on a different internet connection, such as a temporary hotspot on your smartphone.
If switching connections doesn’t do the trick at all and that’s not the problem anyone else seems to be having, the problem is likely local to your device. However, to solve this problem, we need one more diagnostic step.
Try another device
This may not work for everyone, but if you have another Mac, iPad, or iPhone with Facetime on it, try using it and see if the problem persists. Otherwise we can be sure it’s a local problem with your Mac.
If it tracks you from device to device, you’ll have to wait for a server-side issue or contact Apple Support to check if there’s something wrong with your Apple ID.
Log Out & Sign In Again
If you’ve determined that the problem only occurs on your Mac, the next step is to sign out of your Apple ID in FaceTime and then sign back in. This is pretty easy to do:
- Open FaceTime
- Click FaceTime > Preferences
- Click Log out
You will then see this login page where you can try logging in again.
Check Date & Time
Is the date and time on your Mac correct? Simply go to Date and time widget (fastest via Spotlight Search) and check if the date and time are correct.
You should also check that the automatic date and time option is selected, so your Mac will get the correct date and time from the internet whenever it connects.
Older methods are not supported
If you are looking for a way to fix the “server crashes while handling registration error” problem, you may have come across a number of tutorials and articles from 2010 to 2015 detailing other ways. each other to solve problems. While some of that information is still valid, there are two that appear to be no longer relevant.
The first has to do with editing the macOS “hosts” file. While there are various reasons for an error with this file, we couldn’t find any evidence that this particular FaceTime error has something to do with the macOS hosts file, so it’s not the case. what we recommend you do.
Another commonly cited fix is to look for the specific certificate in the Keychain Access app and delete it. This no longer seems to be a suitable fix in modern times. Indeed, the certificate in question does not appear to be present anymore. So feel free to skip that tip if you run into it too.