Calling all Racers for the Alteryx Grand Prix! It's time to rev your engines and race to the stage at Inspire! Sign up here.

Alteryx Designer Discussions

Find answers, ask questions, and share expertise about Alteryx Designer and Intelligence Suite.

SSL Connect Error in 2019.1

AndrewCrayford
8 - Asteroid

HI

 

I have a workflow that download a json file from a URL, it works correctly for 11.7.4 but when i run it in 2019.1 i am getting an the following error message 

 

"Error: Download (12): Error transferring data: SSL connect error"

 

I dont understand why it works for the old version of Alteyx but not in 2019.1 

 

Any advise would be great

22 REPLIES 22
MichalM
Alteryx
Alteryx

It's already out!

KennyD
6 - Meteoroid

Hey @AndrewCrayford,

 

Were you able to resolve? We have a similar issue over at my work place. We are on version 2019.2. 

ebarr
7 - Meteor

Has this issue been fixed?  I'm also getting the same error

Regular
7 - Meteor

Hi,

 

I am getting same SSL Connect error in 2020.2 while using download tool for API call.

Should I downgraded the Alterx designer to version 2018.3? Will my license work with 2018.3? Please advise.

 

Thanks & Regards

 

prashantnahar
7 - Meteor

Anyone found a work around ? This is causing on and off failures with 2019.3 version as well

prashantnahar
7 - Meteor

@MichalM Do we need to do any additional configuration to fix this. We are still facing the error in 2019.3 version. Really appreciate any feedback in this regard

prashantnahar
7 - Meteor

@AndrewCrayford Really appreciate if you could stop marking my question as solution. This is not helping. If you have or know the solution please do reply with a link. I would very much appreciate that. 

MichalM
Alteryx
Alteryx

@prashantnahar 

 

Could you please share more detail about the error?

What is the resource you're trying to access? Do you use proxy? What is the error?

AndrewCrayford
8 - Asteroid

I not sure what happen, as it seems to accept this as a solution and i have remove it.

 

The issue is fixed when the latest revision came out.

JonathanAllenby
8 - Asteroid

We experienced this issue recently after upgrading from 2019 to 2020.3.

The cause was determined to be a computer policy issue.

The user registry policy had todays date whilst the machine had a different date (yesterdays).

Labels