Skip to main content
Solved

AGOL Reader - WinError 10061 - target machine actively refused connection

  • December 30, 2019
  • 2 replies
  • 91 views

Forum|alt.badge.img

I have a workspace that runs in Workbench, but has issues in Server.

I have tried reading both:

  1. Private data (via the Esri ArcGIS Online (AGOL) Feature Service Reader), as well as
  2. Publicly available Living Atlas data (via the Esri ArcGIS Server Feature Service Reader)

The error messages differ slightly but are largely the same. The full text of the error message (for the publicly available Living Atlas data) is:

ArcGIS Feature Service Reader: Could not connect to server. Check that you are connected to the internet and that no firewall is blocking outbound connections. The error was 'HTTPSConnectionPool(host='services5.arcgis.com', port=443): Max retries exceeded with url: /4LKAHwqnBooVDUlX/arcgis/rest/services/ParkBoundaries/FeatureServer?f=json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x050672B0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it'))'

Any ideas on how to fix this error?

Best answer by ae_jeff

In case anyone runs into this in the future, it turned out that our IT group needed to allow access to services.arcgis.com (services5.arcgis.com for the Living Atlas data), not just arcgis.com, and loosen the policy for outbound SSL decryption.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

runneals
Supporter
Forum|alt.badge.img+29
  • Supporter
  • December 30, 2019

Is it public? If so, try using a ArcGIS Server Feature Service Reader instead of the AGOL Reader. The other idea is to contact esri support with this error.

We've gotten this error a couple times before, but it looks like it resolved itself.


Forum|alt.badge.img
  • Author
  • Best Answer
  • December 30, 2019

In case anyone runs into this in the future, it turned out that our IT group needed to allow access to services.arcgis.com (services5.arcgis.com for the Living Atlas data), not just arcgis.com, and loosen the policy for outbound SSL decryption.