First time here? Check out the FAQ!

Paragon Feeds - 404 Errors

  • retag add tags

It looks like all of our Paragon feeds are throwing intermittent 404 errors when attempting to import data. This looks to have begun yesterday around noon.

dhasler's avatar
asked 2019-09-16 08:40:44 -0500
edit flag offensive 0 remove flag close merge delete


Can you provide a some URLs and account names?
What are you doing when you get the errors: login, search, getobject, etc.
Can you verify the URLs you are using too?
We seen vendor issues where URLs were built incorrectly and contained duplicated parts.

bwolven's avatar bwolven (2019-09-16 08:48:49 -0500) edit


We are getting the 404 error intermittently. Sometimes it's during the login, sometimes when sending a search query. Here is the most recent error for Alliance, which occurred when pulling ActiveOffice records (other data had been pulled successfully):

Could not get URL [] - HTTP 404

dhasler's avatar dhasler (2019-09-16 08:54:05 -0500) edit

This looks like it's happening on all Paragon feeds. We haven't changed anything on our end and starting at noon yesterday, all imports began failing.

dhasler's avatar dhasler (2019-09-16 08:55:30 -0500) edit

Other feeds with issues:

Global MLS rely

Northern NH RN4611

dhasler's avatar dhasler (2019-09-16 09:09:25 -0500) edit

Are you still getting them today?

bwolven's avatar bwolven (2019-09-16 09:13:23 -0500) edit

Yes, everything is currently down.

dhasler's avatar dhasler (2019-09-16 09:15:44 -0500) edit

For example, I just tried pulling data from Illinois Alliance.

ActiveOffice, LA_5, MF_3, RE_1 classes pulled fine. But sending the same query to RN_6 then threw this error

2019-09-16 07:18:52 : Sending Query to RETS Server: (L_StatusCatID=|3,1),((L_UpdateDate=2019-09-15T13:13:07+)|(L_Last_Photo_updt=2019-09-15T13:13:07+))

2019-09-16 07:19:13 : CATCH SENDING SEARCH: RN_6 Could not get URL [] - HTTP response code: 404

dhasler's avatar dhasler (2019-09-16 09:21:12 -0500) edit

Can you try one and change one URL to use HTTP instead of HTTPS and see if it makes a difference?

bwolven's avatar bwolven (2019-09-16 09:24:34 -0500) edit

Same intermittent issue:

2019-09-16 07:29:34 : EXCEPTION IN LOGIN TRY librets.RetsSession Could not get URL [] - HTTP response code: 404 cURL reports unable to connect..Exception.Message

2019-09-16 07:29:34 : *LOGIN UNSUCCESSFUL**

dhasler's avatar dhasler (2019-09-16 09:30:27 -0500) edit

What librets version are you using?

bwolven's avatar bwolven (2019-09-16 09:37:23 -0500) edit
add a comment see more comments

1 Answer


We have been using the librets 64bit .NET library. We do have a version of librets that Trestle created for us due to librets not supporting TLS, but we had only been using that on Trestle feeds. On a lark I tried using that. It looks like that did it. I have no idea why the previous librets library suddenly decided to stop working, but I'll take it. I've updated all our jobs to use that librets library, and initial testing looks promising.

Really appreciate your help on this one.

dhasler's avatar
answered 2019-09-16 09:54:52 -0500
edit flag offensive 0 remove flag delete link


Ok. Let me know how well it works.

bwolven's avatar bwolven (2019-09-16 10:15:29 -0500) edit

I think we're good. All 100+ feeds have updated successfully. Still scratching my head as to the sudden cause, but oh well.

dhasler's avatar dhasler (2019-09-16 10:32:16 -0500) edit

That's good to hear.
librets 1.6.2 uses VS 2010 MSVC runtime which isn't listed as supported on Server 2016.
It does seem to work but don't know if there are intermittent issues.

bwolven's avatar bwolven (2019-09-16 10:43:32 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer