Importers Failing for Multiple Sources
After we switched the below MLSs to TLS 1.2 protocol, our importers for these sources are failing with 401 error. Can you help investigate? Thanks!
Spartanburg MLS (both listing and photo importers failing): RETS UN: RedFin https://sptbgmls.rets.paragonrels.com...
Santa Fe MLS (only photo importers failing): RETS UN: 7343 https://sfar.rets.paragonrels.com/ret...
South Central Kansas MLS, Inc (only photo importers failing): RETS UN: rets_redfin_vow https://sckmls.rets.paragonrels.com/r...
Try switching URL to:
Notice the "dash" between mlsid and rets instead of "dot"
If that doesn't work you can try using HTTP with Digest authentication.
I’ve tried the ‘dash’ url, but it also didn’t work.
Will this (HTTP with Digest authentication) work after the deprecation?
Yes. We prefer vendors to us HTTPS if possible.
But HTTP will still be an option at least for the near future.
Do you have other sites that are currently working using HTTPS?
we converted four MLSes to TLS 1.2 protocol. From those four, one mls (TMLS) is working just fine and two others (SCKMLS and SFARMLSNM) are failing only on photo importer (listing importer for these two is working also) and one mls (SPMLS) is failing on both (listing and photo) importers.
Can you provide list the 4 URLs you are using and all have been changed to use dash (I assume).
TMLS: https://triangle.apps.retsiq.com/rets... SCKMLS: https://sckmls.rets.paragonrels.com/r... SFARMLSNM: https://sfar.rets.paragonrels.com/ret... SPMLS: https://sptbgmls.rets.paragonrels.com...
yes, we have tried using dash instead of dot; didn't work
What is failing with your photo importers?
How are they downloading the images and where is it failing?
This is the error message we are seeing:
Caused by :org.realtor.rets.retsapi.RETSConnection$RETSConnectionNonRetsResponseContentException: Invalid RETS response; HTTP status code: 401;
so, we cannot connect to the server
Are you sure you are using the same URL and credentials for listing and photo pulls?
And that both have the dash instead of dot?
Yes, we are using the same url for both, and we are currently using the dot one because the dash one didn't work.
We have switched back to the old protocol and our importers are working now, but it would be great if we could fix the issue and switch to the new protocol.