iCloud.com encountered an error while trying to connect to the server

Anonymous
2023-08-21T07:00:06+00:00

I get the pop-up that says "iCloud encountered an error connecting to the server". However, if I connect to a mobile hotspot, iCloud works without any issue on Edge!

Observations

  • I am able to access iCloud through my iOS device (iPhone) connected to the same high-speed broadband Wifi connection.
  • iCloud.com is accessible on Edge browser only if my PC is connected to the internet via a mobile (4G/5G) hotspot connection.
  • The issue does not occur at all on Firefox (irrespective of the connection mode)!

Any clues on how to solve this issue? Looks like it's an Edge issue on Windows 11 when connected to a broadband Wifi connection.   

Thanks in advance 

Roy

Microsoft Edge | Website issues | Windows 11

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-08-26T20:13:31+00:00

Hey,

I'm just here to confirm that disabling IPv6 helped me resolve this issue.

Image

Alternatively, switching to Google Public DNS also resolved the issue as per users on Reddit. To know step-by-step instruction to switch to Google Public DNS check out this guide -- <link removed>

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

69 additional answers

Sort by: Oldest
  1. Anonymous
    2023-08-24T14:21:20+00:00

    I did some research and testing after reading a post yesterday by Hahn.

    I overrode the DNS settings in Edge and Chrome and the wireless network connection I am using to one of the DNS options provided by Hahn. Specifically, I switched from using the DNS provided by my local internet service provider to Google. After making the changes late last night, I began to experience some improved results using Edge and Chrome, but there are still too many failures to connect. Firefox never failed going to iCloud.

    Unfortunately, all the testing has now corrupted my calendar on my iPhone that was synced to my Outlook calendar. I will deal with the duplicate calendar entries after (if) I get a reliable connection to iCloud.

    Again, Firefox never missed a beat. I connected to iCloud 100% of the time.

    Again, what is it about Firefox that makes it successful over Edge or Chrome in this situation? I think it now has to do with DNS.

    After reading lots of stuff last night, it appears Firefox, by default, uses a special and dedicated DNS. If I read an article correctly, I think it is Cloudflare.

    Attempts to use various DNS in Chrome and Edge have not yet yielded a 100% success rate. Sure wish there was a way to log things as you tried to connect to iCloud using either Edge or Chrome. Such info might yield a solution.

    This is super insightful. Thanks for taking time to investigate the root cause.

    BTW, I too tried the DNS options suggested by Hahn but no success.

    Hoping an expert from Microsoft will help here on how to capture the logs while connecting to iCloud.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-24T14:23:15+00:00

    Thanks for the clue about firefox, yes Firefox works fine

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-08-24T14:32:06+00:00

    I managed to login to icloud on a clean user profile using edge, it still got the error message and when logged in I got the main page but all the databases said they couldn't connect. This was using edge. Firefox is still OK, as is my android phone. I also am still able to see apple stuff on outlook

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-08-24T14:53:49+00:00

    I too tried a new Edge profile as well as trying out as a new local user (on Windows 11) - both options did not work!

    The only solution at this point is to access iCloud.com on Firefox browser.

    Seems so weird that this issue happened all of a sudden in Edge/Chrome after working fine for me since the past 4 years or so ...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments