Select to view content in your preferred language

Unable to establish connection to https://www.arcgis.com/

346
7
3 weeks ago
luckachi
Frequent Contributor

I am trying to start Pro on one of our machines and I keep getting an "Unable to establish connection to https://www.arcgis.com/" error. I stumbled upon this article but I don't even get a sign in screen

https://support.esri.com/en-us/knowledge-base/problem-unable-to-sign-in-to-arcgis-online-or-portal-f...

Any help would be appreciated as some of our public facing tools are not working.

 

pro_Error.png

Tags (3)
0 Kudos
7 Replies
CodyPatterson
MVP Regular Contributor

Hey @luckachi 

Would it be possible to restart the machine? It may be a DNS or DHCP issue on the machine side that could be stopping it, I would try using the command prompt to ping "www.arcgis.com" and see if it hits properly as well.

Cody

0 Kudos
luckachi
Frequent Contributor

I restarted the machine this morning and no change. I will try the command prompt ping right now

0 Kudos
luckachi
Frequent Contributor

luckachi_1-1762194115751.png

 

0 Kudos
CodyPatterson
MVP Regular Contributor

Hey @luckachi 

Thank you for testing this out! Since the ping goes through you can connect which is good! I would try giving Pro a soft reset like this here:ArcGIS Pro Soft Reset 

After this, my only other suggestion would be to reinstall ArcGIS Pro, then contact Esri Support, could you also attach a screenshot of the connection error?

Cody

0 Kudos
luckachi
Frequent Contributor

Thanks Cody! Appreciate your help with this - I will try the soft reset and see what happens.

0 Kudos
luckachi
Frequent Contributor

Soft reset didn't work 😞 but I noticed that the StrongName folder doesn't exist in my local folder (even after the restart ). Will be following up with ESRI support.

0 Kudos
luckachi
Frequent Contributor

In case anyone else experiences this issue. This machine runs Windows Server 2019 with IIS Crypto security. We had to enable the 'best practices' option for TLS which enabled TLS 1.0, 1.1 and 1.2 (1.2 had already been enabled and we disabled 1.0) - apparently TLS 1.1 was necessary to establish a connection via Pro.

0 Kudos