Can't login to iMessage and FaceTime

Finally it looks like Apple have fixed the issue, all working ok now

My issues fixed also after call to Apple Support, not sure if it was coincidental though with a global fix by Apple...

Finally everything works like a charm 🙂

Sadly I've been fighting the seemingly same issue with Apple for about 8 months and they can't seem to resolve the problem. It appears that we need to create bug reports (http://bugreport.apple.com/) and really complain to the proper venue here because, while this is not new, it is a real nightmare to resolve. I've been able to reproduce it in a virtual machine fresh vanilla install of OS X 10.11. For those of us who have not seen resolution, please keep pounding because there is most certainly something askew on the server side from what a couple folks have told me who work at Apple, even though they can't seem to resolve it (for everyone).

So I'm still having the issue

"There was an error connecting to the Apple ID server."

I checked in Console and every time I try to login I see this 3 times.

3/24/16 5:50:15.736 PM akd[288]: NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802)

I had this same issue in El Capitan 10.11.3 on my MacPro almost a month ago. I couldn't use Messages or FaceTime on my MacPro, but I could log into iCloud services, the iCloud website, and MyAppleID with no issues. I was give a list of things to try, both on my iPhone 6S running 9.2.1 and the MacPro. After over a week of back and forth with Apple Support and an Apple Engineer, my issue was resolved simply by zapping the PRAM on my MacPro. After that, all was well.

Give it a try. You'll only lose a few settings, but maybe it will fix your issue. 🙂

The only bad thing is now I am hesitant to install 10.11.4. I already have iOS 9.3 on my iPhone and things are working just fine at the moment.

Update: I have updated to El Capitan 10.11.4 and everything is still working. It took a long time for FaceTime to authenticate as well as for me to get authenticated back into the discussion boards, but I did eventually. Not sure if the root cause of the issue(s) has been addressed or not, but at least I am still working after the update.

Hope the PRAM zap works for someone else also... at least with a MacPro.

I'm still having the same issue. I have updated to 10.11.4, no help. The odd thing is, when i type in my password and click 'Sign In' if I click on one of the other accounts then click back on iMessage, I can see all my settings. I can even uncheck the 'Enable this account' check box. If I do that. it will not generate an error. If I recheck the box, the 'unable to authenticate' error will pop back up.

My Early 2009 Mac Pro responded to zapped PRAM. I now have iMessage back -- planned on making it my last attempt before moving to a clone of my Yosemite startup drive. No need now :-)

fwiw: I moved to El Capitan only after the .4 release came out. From the days of OS 7.1, I practiced early adoption as each new release emerged. Now I follow bug reports until it appears they've got a very stable release. That Apple almost had it with a fourth version speaks to the complexity of this software.

Have had this problem since before JULY 2015 and to say that I'm upset is a severe understatement, especially since I'm a paying customer of iCloud. I surely wish Apple would get their proverbial heads out of their rear ends and resolve this. I've gone through 3 customer service reps and have 2 dev tickets open with no joy whatsoever. I've tried to explain that this is a server side issue from the information gathered on the logs that they've requested, but it just seems to fall on deaf ears.

Hi,

I take it you can see the Serial Number ?

That you have tried another Mac User account with the same iMessages ID ?

That a NVRAM reset and Safe Boot also have not produce a satisfactory result ?

In the Applications/Utilities folder open the Keychain Access app.

Select "Login' top left and "Passwords" lower left and then the IDS: AppleIDforiMessages-Auth Token (where the italics bit is the actual email ID used).

Now access the ~/Library/Preferences and delete the com.apple.ids.service.com.apple.madrid.plist (Dragging to the Trash is good enough).

Now re-open Messages and add back the Apple ID. (it was stored in the madrid item but you just deleted that).

Hopefully this will cause the Login to be refreshed completely.

The Serial Number is used as well as the ID and Password and the deletion of the Keychain items should resolve any issues if the account/Keychain was Migrated.

A Reinstall, which they sometimes suggest at Apple Support, will not clear a migration issue.

Nor does Updating or Upgrading as the Keychain is unchanged.

Try Apple Support once more and ask them to rest the iMessages server is relation to your Apple ID and the Mac's use of it.

I am working from a position of not having this problem.

The Serial Number part was added at the OS X 10.8.2 update which updated Messages 7 to version 7.0.1

It was obviously designed to be a security feature.

It is clear that for some reason it gets triggered for some people.

Reading many posts on this issue it seems clear that at some level Apple are aware of the issue as the apparent "cause" then varies across Mavericks, Yosemite and El Capitan.

In EL Capitan it seem it is triggered by just Upgrading to El Capitan for some. Others state it was when they moved to OS X 10.11.3

People who have reported back do say that currently Level 2 responders ask Engineers to get involved and that they are told Resets take 24 hours (although many post that "overnight" sees results).

IF the Keychain item deletion works for iMessages then do the same for FaceTime

8:41 pm Saturday; April 2, 2016

Thanks Ralph, I followed your suggestions, and really hoped deleting the "madrid" pref file was going to do the trick. In the end, none of it helped. P-RAM on startup is what finally worked for me.

Thanks for letting us know.

9:35 pm Saturday; April 16, 2016

So just an FYI the steps you enumerated above did not work re: keychain and the madrid pref. The other precursory steps were fine. Sadly it seems I can't reach Apple. The last attempt to try to contact support ended up in their refusal to offer free assistance saying that I have to buy a new support plan, etc. and so I've given up on iCloud. I think I'm going to just cancel their junk service altogether.

Hi,

Apple Support (or Apple Care) is a paid for service for regular issues after the complimentary period has run out.

(You can of course pay to extend that care).

They will however sort out Apple ID issues for free.

Level 1 people at Apple Support are very script led and hence the "you have to pay" if they don't think it is Hardware or Software related.

If you let them they will run the whole script trying to prove it is one or the other.

Try asking for a Level 2 support person or higher.

These are more likely to take the issue of an Apple ID problem more seriously.

iTunes, FaceTime, Messages, The App Store, Games Centre, Developer access are some of the separate servers that your Apple ID can be used with.

The Serial Number of the Mac is used to create the Auth Token in the Keychain.

It "proves" it is you calling. (It has done so since Messages 7.0.2 at OS X 10.8.2)

Migrating a Keychain from another computer can get the iMessages Server to block your use of the Apple ID when used by your Mac. (i.e. it is App., ID and Server specific depending which way you are looking at it).

The Original issue in OS X 10.8.2 tended to be missing Serial Numbers that were not put back on to Repaired Logic/Motherboards.

After that the server needed resetting.

The problem has occurred during both version 8s in Mavericks and Yosemite but seems to have increased slightly at the OS X 10.11 Upgrade and again at the OS X 10.11.3 update.

That said the Level 2s are still likely to want you to jump though some hoops to prove it is not Hardware or Software related.

Safe Boot, NVRAM resets, testing in another Mac user are among the more common.

Reinstalling to OS, Upgrading the OS if you are using a earlier version or Updating the OS to OS X 10.11.4 are unlikely to change anything.

As I mentioned above they are like to engage with the engineers at some point.

Be polite, persist with it being an Apple ID issue, request that the server is reset regarding your Mac's use of the Apple ID on the iMessages Server.

7:33 pm Sunday; April 17, 2016