Ever since the switch to TLS1.2, can not connect to RETS

asked 2022-05-02 07:57:52 -0500

Even when I try to use RETSConnector, it will not make a connection. I get error "Could not create SSL/TLS secure channel". I do connect with other vendors using TLS1.2 and do not have an issue. I do not know what to try next. Appreciate any direction you may be able to provide.

edit retag flag offensive close merge delete

Comments

What is your URL and login name?

bwolven gravatar imagebwolven ( 2022-05-02 08:34:50 -0500 )edit

https://nrv-rets.paragonrels.com/rets... and sei is login name... just some additional info... If I paste that url into a web browser and log in, it seems to log in fine. I think this tells me that there is some issue within my code that connects to the Rets server but I'm not clear what that may be. I have tried many suggestions from StackOverflow but none seem to work.

TSetliff gravatar imageTSetliff ( 2022-05-02 08:43:20 -0500 )edit

With HTTPS we require Basic authentication, Are you using that?
Also, can you connect to other Paragon RETS sites or just other MLSs?

bwolven gravatar imagebwolven ( 2022-05-02 08:51:44 -0500 )edit

We do connect to http://bcar.rets.paragonrels.com/rets... but that doesnt appear to have been switched over to https yet. I am using basic authentication. We can connect with CoreLogic and Matrix, both of which use https and TLS12 if I'm not mistaken.

TSetliff gravatar imageTSetliff ( 2022-05-02 09:07:11 -0500 )edit

You can try it on BCAR, but make sure to change it to "bcar-rets.paragonrels.com".
When you checked using the browser, was it on the same computer you do your pulls from?

bwolven gravatar imagebwolven ( 2022-05-02 09:24:23 -0500 )edit

Yes sir, it was the same server

TSetliff gravatar imageTSetliff ( 2022-05-02 09:28:10 -0500 )edit

For what its worth, if I use http://nrv-rets.paragonrels.com/rets/... (no s in http), I am able to connect and pull the data but I think I read that that would eventually stop working.

TSetliff gravatar imageTSetliff ( 2022-05-02 09:30:38 -0500 )edit

I was able to connect with your account to NRV as HTTPS without issue.
I used RETS Connector version 1.2.7220.
What version are you using?

bwolven gravatar imagebwolven ( 2022-05-02 11:35:28 -0500 )edit

1.2.7220... I did a check for Upgrades but it says No Upgrades detected.

TSetliff gravatar imageTSetliff ( 2022-05-02 12:18:26 -0500 )edit

Sorry. I had a typo in the version. We are using the same one.
What OS are you running on the box where you are running your downloads?
And is it up-to-date?
You can try running this on https://nrv-rets.paragonrels.com and see if it shows anything.

https://www.ssllabs.com/ssltest/analyze.html
bwolven gravatar imagebwolven ( 2022-05-03 08:27:22 -0500 )edit

On my desktop system, I am running Windows 8.1 Pro Version 6.3.9600. It does update pretty regularly so I would think it is current. On the server where the code runs in batch, it's running Windows Server 2012 Standard. There is a fair chance that it is not up to date but I wouldnt expect it to be too far behind. On both systems, I get the same connection error when using HTTPS in the URL

TSetliff gravatar imageTSetliff ( 2022-05-03 09:03:16 -0500 )edit

Here's some things you can check:

https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client
bwolven gravatar imagebwolven ( 2022-05-03 09:30:08 -0500 )edit

Thanks!!! Appreciate your patience and suggestions to try and help resolve this. Will keep you posted!!

TSetliff gravatar imageTSetliff ( 2022-05-03 09:51:00 -0500 )edit

We had a similar issue with a Paragon WebAPI feed. Our LibRETS based application wouldn't work on a server running Windows Server 2012 due to SSL issues (although if you used a web browser it was able to log in). Running it on a Windows 10 box would work. We had to upgrade the server OS. In our case up to Windows Server 2022.

pstallings gravatar imagepstallings ( 2022-05-04 08:56:58 -0500 )edit