Error connecting to the Apple ID server

Yes!!! This works for me. I have Little Snitch turned off in Silent Mode. I don't have Kasbersky, so this is the cause of it.

Try adding Google DNS to Network in System Preference, this will fix it, at least for me:
8.8.8.8

8.8.4.4

@hendricksbj. Thanks for that. It reminded that I changed the CRL to be more restrictive to avoid issues with Safari happily loading webpages with revoked certificates - remember HeartBleed! Set the OCSP and CRL fields back to "Best Attempt" from "Require if certificate indicates" to restore Apple ID server connection. Not sure why this happens, but use Firefox since the app automatically checks for valid certs.

-ish

Spent hours on this. Called Apple several times and no one could figure out what was wrong with my computer and why I kept having problems signing in. As per an Apple employee, I was told I needed to reboot my entire computer. This process took over 36 hours and was no help at all. I felt incredibly frustrated and gave up doing anything about this issue for months.

...Then I FINALLY stumbled upon your post. I think it needs it's own place because the kapersky stuff is extremely frustrating to read through when you don't have the software on your computer. Your directions took me less than 5 minutes and I am so happy I saw it! THANK YOU!!!

how do you connect to apple server, trying to login in to iCloud and popping up that i cat connect

Had the same problem. Closed my VPN and Dropbox and tried again. No problem.....

I came across this issue before, but it was of my own doing. I had made KeyChain Access preference options; Online Certificate Status Protocol (OSCP), and the Certificate Revocation List (CRL), restrictive. For some reason making the CRL restrictive disrupted communications with the AppleID server.

IF YOU HAVE KASPERSKY INSTALLED, THEN SEARCH THE FORUMS TO ALLOW THE APP STORE THROUGH THIS APP.

See recommend (default) KeyCHain certificate settings.

Hi, I experienced the same connection error to "Apple ID Server" after hardening certificate management (OCSP+CRL) in KeyChain. I don't use Kaspersky.

After a short analysis of network traffic, I discovered that everytime I access iCloud, Apple Store, ... my Macbook opens a network connection to server 'https://gsa.apple.com.akadns.net' and this fail since certificate on that server is invalid (generatd for server 'gsa.apple.com').

I signaled this to Apple some weeks ago but nothing changed.

Personally I think Apple should fix its certificates and not ask us to decrease security level on our Macbook by skipping certificate cerification. Recent history teaches that too many times personal data has been stolen by, for example, malicious sites that cloned official ones. CRL and OCSP can help preventing this.

Waiting for Apple to correct their certificates, I use to switch temporary KeyChain preference from "Require" to "Best Attemp" whenever I need to authenticate my credentials (fortunately they are usually cached so I need them only for buying new Apps).

i have the same problem but i haven't Antivirus

I have the exact same problem as you. I switched from an iPhone 6 oto a 7. I did a reset all settings first, and can't erase my content and settings now. Have you found a solution yet?

Clearly, as some have said, Apple doesn't care about this. The problem for me is I have a new iPhone 7 to use and I can't erase my old phone because I can't get logged into the Apple site. I've tried wifi, cellular, you name it. At first I wanted to blame my ISP, but that is clearly not the case. It is Apple and Apple alone that seems to be oblivious to the impact this has on itheir loyal customers. Maybe an ANDROID phone is in my future.

Send Apple feedback. They won't answer, but at least will know there is a problem or a suggestion for change. If enough people send feedback, it may get the problem/suggested change solved sooner.

Feedback

FYI - for anyone running into this problem and having AVAST antivirus installed, you must disable the live antivirus protection to access the ID server. No idea why, but this fixed it with Avast 2016 12.3.

Feel free to ping me if I can clarify further -- I was on the phone with AppleCare when I figured it out.

dsaenz28

dsaenz28