Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacBiter

macrumors 6502
Original poster
Jun 2, 2021
319
53
After a restart yesterday due to a Bluetooth problem, I suddenly found I couldn't Facetime (as I do nearly every day) without a sign-in. That alone didn't bother me - I entered my Apple ID, password + 2FA digits, but got the message "The server encountered an error processing registration...", even after restoring every component with yesterday's date containing "facetime" via Time Machine, from 3 days ago.

How do I get FT back to how it was?
 
Double-check the Date & Time setting in Mavericks. It may not be automatically syncing with a time server.
 
Double-check the Date & Time setting in Mavericks. It may not be automatically syncing with a time server.
It's not that - I've just seen another post on this very topic. I fear FT is now broken in Mavericks but only shows the error after a restart and request to sign in.
 
After a restart yesterday due to a Bluetooth problem, I suddenly found I couldn't Facetime (as I do nearly every day) without a sign-in. That alone didn't bother me - I entered my Apple ID, password + 2FA digits, but got the message "The server encountered an error processing registration...", even after restoring every component with yesterday's date containing "facetime" via Time Machine, from 3 days ago.

How do I get FT back to how it was?
were you able to make outgoing calls too?
 
Hi MacBiter, okay, Thanks for responses everyone,

I've just seen another post on this very topic. I fear FT is now broken in Mavericks but only shows the error after a restart and request to sign in

um The other topic response is true, Mavericks if from 2013, For apple this is too "old" for new support (sorry for the English i am french)

 
Hi MacBiter, okay, Thanks for responses everyone,

I've just seen another post on this very topic. I fear FT is now broken in Mavericks but only shows the error after a restart and request to sign in

um The other topic response is true, Mavericks if from 2013, For apple this is too "old" for new support (sorry for the English i am french)

there is a fix for it. the issue here is that the endpoint seems to be blocking requests with plain usernames and passwords. 10.11 and later use the grandslam authentication system, which sends a hashed version of the password. the server gives back a username and password token that expires after 5 minutes. new os x uses these credentials to log in.
 
there is a fix for it. the issue here is that the endpoint seems to be blocking requests with plain usernames and passwords. 10.11 and later use the grandslam authentication system, which sends a hashed version of the password. the server gives back a username and password token that expires after 5 minutes. new os x uses these credentials to log in.
Oh... Sorry, i have mavericks but everything is broken, idk this before...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.