First time here? Check out the FAQ!

Paragon Outage

  • retag add tags

I don't see it posted here, so I will ask. Is there a blanket outage going on? Here's an example of a basic query that returns "miscellaneous server error".

I have about 50 feeds down at the moment.

JoeW's avatar
asked 2022-08-17 09:21:04 -0500
edit flag offensive 0 remove flag close merge delete


Not that I know of. I was able to pull data from two different sites without issue.

bwolven's avatar bwolven (2022-08-17 09:25:57 -0500) edit

Just tried aabrky and it is working too.

bwolven's avatar bwolven (2022-08-17 09:29:39 -0500) edit

Do they all connect through the same external IP address?
If so, what is the IP address, it could be blocked for some reason?
Also, have you tried doing a login from the browser on a different computer?

bwolven's avatar bwolven (2022-08-17 09:43:33 -0500) edit

Basically, every RETS query for every MLS we have access to, which is dozens, starting at around 9:20pm CST last night to return this error:

'miscellaneous server error.'

For the aabrky example above the login is RETSField. Is there anyway you can dig into the logs on your end to see what the underlying issue is? This problem is happening from multiple completely different systems with different IPs.

jflaig's avatar jflaig (2022-08-17 10:09:04 -0500) edit

No, these requests originate on multiple servers, including one in AWS, so the IP probably won't be constant. Browser returns the same "miscellaneous" error that RETS client requests return. Metadata requests work. Agent/office/property requests do not. I'm troubleshooting at this end, but any log data you might have available would be appreciated.

JoeW's avatar JoeW (2022-08-17 10:09:34 -0500) edit

Is it just the search that is failing for these sites?
In other words, are you able to login and logout?

bwolven's avatar bwolven (2022-08-17 10:29:51 -0500) edit

we can login and out

jflaig's avatar jflaig (2022-08-17 10:30:45 -0500) edit
add a comment see more comments

1 Answer


Hi Bryce, we had to modify a setting in our RETS software for all but a couple Paragon feeds. The setting to scrub the session cookie down to just the ID had to be invoked. Do you know if something related to that changed in Paragon? All of this was working until about 10pm CDT last night.

We're ok now.

JoeW's avatar
answered 2022-08-17 11:01:14 -0500
edit flag offensive 0 remove flag delete link


From what I can tell, nothing was changed that would have effected session cookies.

bwolven's avatar bwolven (2022-08-17 11:13:08 -0500) edit

@JoeW Thank you for sharing your put us on a path to restore the updates to our feeds as well!!

remax's avatar remax (2022-08-17 13:14:02 -0500) edit

Glad it helped!

JoeW's avatar JoeW (2022-08-17 13:37:05 -0500) edit

I wonder if your client library isn't handling possible multiple cookies properly.
What I see coming from the server is:

Set-Cookie: RETS-Session-ID=-371db403-044f-4b4e-8a9c-7a13472cb2a3-; path=/
Set-Cookie: TS01b4ff87=01689bcfc5c6023ecae275e39b8631f5b9d3e50417f8a5f1969feb1766c12b1de27f0d5d601dfb844196f127f892ae83f21b8a2aef3bd48e64dc63d092880a2cc480f27d84; Path=/

And LIBRETS client sends the Cookie back as:

Cookie: RETS-Session-ID=-371db403-044f-4b4e-8a9c-7a13472cb2a3-; TS01b4ff87=01689bcfc5c6023ecae275e39b8631f5b9d3e50417f8a5f1969feb1766c12b1de27f0d

bwolven's avatar bwolven (2022-08-17 16:12:24 -0500) edit

It's possible. Wasn't a problem until last night, and most of this code is years old.

JoeW's avatar JoeW (2022-08-17 16:22:22 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer