First time here? Check out the FAQ!

Querying multiple values for a field

I've started getting 500 Errors when when doing a query containing this: (L_Area=|2,18,25,45,56,75,78,86,94,131) It will work if I cut it down to just 2 values: (L_Area=|2,18)

I'm having a similar issue with status: (L_Status=|1_0,3_0,1_1) doesn't work but (L_Status=|1_0,3_0) does.

It has the same issue with and without the |.

It has run correctly for years but it started failing Nov 12. Also, it is across multiple MLS providers so it is like an issue on the Paragon side of things.

weezer311's avatar
asked 2022-11-14 09:59:11 -0500
bwolven's avatar
updated 2022-11-16 08:37:39 -0500
edit flag offensive 0 remove flag close merge delete


I am seeing a similar issue on different fields across all MLSs. Seems to have started on Saturday morning. For example, this returns a 500:

We're basically dead in the water across the board since our sync jobs are all dying.

jflaig's avatar jflaig (2022-11-14 10:23:02 -0500) edit

I'm using this workaround for now. ((L_Status=1_0)|(L_Status=3_0)|(L_Status=1_1))

weezer311's avatar weezer311 (2022-11-14 10:46:25 -0500) edit

What account name are you using?
I tested it with another account and your original queries work without issue.

bwolven's avatar bwolven (2022-11-14 11:53:33 -0500) edit

our login is T101597

jflaig's avatar jflaig (2022-11-14 12:03:45 -0500) edit

I don't see that account on SJSR?

bwolven's avatar bwolven (2022-11-14 12:11:49 -0500) edit

that login is for this:

As I said this problem suddenly started happening for all MLSs on Saturday .We're also seeing login timeouts intermittently.

jflaig's avatar jflaig (2022-11-14 12:13:44 -0500) edit

NGLRMLS with your account and the area search listed above worked fine.
Status search (L_Status=|1_0,3_0,1_1) also worked without issue.

bwolven's avatar bwolven (2022-11-14 12:23:32 -0500) edit

look in your logs at our requests for that login since saturday. Also we don't search on L_Status.

jflaig's avatar jflaig (2022-11-14 12:31:29 -0500) edit

I am also able to replicate the original issue in this thread.

jflaig's avatar jflaig (2022-11-14 12:32:59 -0500) edit

We get a connection reset by peer error. I have to wonder if there isn't some sort of network or security issue at play here. When we make queries from AWS they all fail on this error.

jflaig's avatar jflaig (2022-11-14 12:34:43 -0500) edit

OR actually, maybe this is a credentials issue?

RAW Request from Fiddler:

GET HTTP/1.1 Host: RETS-Version: RETS/1.5 Accept: / User-Agent: Top Producer/1.0 Cookie: RETS-Session-ID=-883ee5ce-d9a5-4d9a-879a-a7f456206ecc-

RAW Response:

HTTP/1.1 401 Unauthorized Cache-Control: private Content-Type: text/html Expires: Mon, 01 Jan 0001 00:00:00 GMT RETS-Server: RETS-Paragon/1.0 RETS-Version: RETS/1.5 WWW-Authenticate: Digest qop="auth",realm="NGLRMLS",nonce="2022-11-14T18:48:00",opaque="",stale="false",domain="\rets\fnisrets.aspx\nglrmls" X-Server: A070-01 Date: Mon, 14 Nov 2022 18:37:59 GMT Content-Length: 1293 Vary: Accept-Encoding

<html xmlns=""> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> <title>401 - Unauthorized: Access is denied due to invalid credentials.</title> <style type="text/css"> </style> </head> <body>

Server Error


401 - Unauthorized:

jflaig's avatar jflaig (2022-11-14 12:40:16 -0500) edit

This happening for me on CAAR and NRV. I've confirmed that office search example also doesn't work for me. It is definitely not an auth issue. If I remove that part of the query it works and if I write it out long form ((L_Status=1_0)|(L_Status=3_0)|(L_Status=1_1))

(L_Status=|1_0,2_0) works with 2 values. Once you add the 3rd one it breaks.

weezer311's avatar weezer311 (2022-11-14 12:46:49 -0500) edit

ok, so the pattern seems consistent. If I do this the query works fine:


but if I do this:


we run into the errors.

jflaig's avatar jflaig (2022-11-14 12:52:05 -0500) edit

Another example... This query:

returns a 500 error, but this version works fine:

Can you comment? It doesn't help that it works on your end. If you check out the logs something should be obvious. We haven't changed anything on this end.

jflaig's avatar jflaig (2022-11-14 14:39:28 -0500) edit

I was able to run both of those NGLRMLS queries you listed with your account without issue.

bwolven's avatar bwolven (2022-11-14 15:12:18 -0500) edit

That's not very helpful. What would be helpful, is if you could examine your logs and see why we get a 500 error on the first version. Something has changed on your end and it needs to be investigated. If you are unwilling to do anything else please be clear and let me know so we're no waiting on you.

jflaig's avatar jflaig (2022-11-14 15:14:49 -0500) edit

I should add, I didn't open this thread, it was weezer311 who is experiencing the same problem starting on the same day as us. If it was only us complaining maybe if I were you I would be a little skeptical, but this is not the case and no doubt others may be experiencing this problem as well.

jflaig's avatar jflaig (2022-11-14 15:17:52 -0500) edit

Are you having this issue on more than NGLRMLS?
If so, what other MLS's?

bwolven's avatar bwolven (2022-11-14 15:18:59 -0500) edit

yes, the same issue for 60+ MLSs.

jflaig's avatar jflaig (2022-11-14 15:19:51 -0500) edit

Can you try

It doesn't work on CAAR and NRV but does work on CGAR and CWTAR.

weezer311's avatar weezer311 (2022-11-14 15:19:56 -0500) edit

odd, it doesn't seem to work for us for anything

jflaig's avatar jflaig (2022-11-14 15:34:14 -0500) edit

And it does work on SCWMLS. So 2 out of 5 have the same issue.

weezer311's avatar weezer311 (2022-11-14 15:38:48 -0500) edit

Can you try switching to RETS/1.7.2 or RETS/1.8 and see if it makes a difference?
I do see lots of successful requests coming through on NGLRMLS.

bwolven's avatar bwolven (2022-11-14 15:39:04 -0500) edit

Switching to 1.8 did not fix it for me on CAAR or NRV.

weezer311's avatar weezer311 (2022-11-14 15:48:21 -0500) edit

yeah, that doesn't seem to matter

jflaig's avatar jflaig (2022-11-14 15:55:48 -0500) edit

Are both weezer311 and jflaig from the same company or different ones?

bwolven's avatar bwolven (2022-11-14 16:10:56 -0500) edit


jflaig's avatar jflaig (2022-11-14 16:12:19 -0500) edit

The NGLRMLS query from above: (L_ListingID=1%2b),((L_StatusCatID=1)|(L_StatusCatID=3)),(L_DisplayId="1905045","1906612","1906613","1906610")
Where you said you get the 500 error.
What day was that sent?
I'm trying to track it down in the logs.

bwolven's avatar bwolven (2022-11-14 16:20:26 -0500) edit

today. shortly before I posted the message

jflaig's avatar jflaig (2022-11-14 16:21:29 -0500) edit

but we're hitting searches every 15 minutes for NGLRMLS using that format that are failing. so you should see it all over for that login.

jflaig's avatar jflaig (2022-11-14 16:22:16 -0500) edit

I've tested it a bunch today on CAAR. I just did one right before posting this.

weezer311's avatar weezer311 (2022-11-14 16:23:53 -0500) edit

I'm trying to focus on NGLRMLS at the moment instead of jumping all around.
But what application or library are you both using to connect to RETS?

bwolven's avatar bwolven (2022-11-14 16:36:24 -0500) edit

we're using custom RETS client hosted in AWS. I would guess weezer311 is doing something else. It's worked fine up until Saturday.

jflaig's avatar jflaig (2022-11-14 16:37:54 -0500) edit

Is it using multiple IP addresses in AWS?
If so, it could be that some are being blocked.
In my logs I show for NGLRMLS these two: many with: and a very few with:

bwolven's avatar bwolven (2022-11-14 16:48:42 -0500) edit

Mine is custom written coming from a Rackspace server. In my case it is a single IP and it is not being blocked. I can toggle back and forth from the working and non working query. Additionally the 3 working sites are coming from the same IP. I would expect an error in the 400 range if it was a block. 500 error indicates that it is an issue on the server side where some fatal error is not caught.

weezer311's avatar weezer311 (2022-11-14 17:01:41 -0500) edit

@weezer311 what MLS and account name are you having the issue with?

bwolven's avatar bwolven (2022-11-14 17:03:43 -0500) edit

CAAR with user CAAR_RETS_19

weezer311's avatar weezer311 (2022-11-14 17:04:59 -0500) edit

You can ignore the, that's my local. The AWS IP is I believe our requests should only be coming from one IP in AWs.

jflaig's avatar jflaig (2022-11-14 17:05:07 -0500) edit

@jflaig Can you try the same request that you get the 500 error in a browser?
Do the login request making sure to pass the RETS-Version parameter in the URL.
Then change it to search and pass your failing search parameters along with the RETS-Version parameter and see if you get the exact same error that way too?

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

While waiting for @jflaig I've confirmed mine fails the same way in a browser.

weezer311's avatar weezer311 (2022-11-14 17:20:45 -0500) edit

@weezer311 so you get the same 500 error in the browser?
Can you give me the exact CAAR query you are using for your test?

bwolven's avatar bwolven (2022-11-14 17:21:54 -0500) edit

Yes. I've figured out the issue. It works when encoding the commas as %2C. So something changed recently that requires more than one comma to need to be URL encoded. The ones that were working for me had no more than one comma in the values.

weezer311's avatar weezer311 (2022-11-14 17:28:13 -0500) edit

That is weird. We haven't changed anything on our side recently.
When I send my requests out they aren't encoding the commas.

bwolven's avatar bwolven (2022-11-14 17:34:32 -0500) edit

I tried it both with POST request and in a browser URL and it worked in both cases.
So it doesn't really answer the why or what changed that would cause yours to break.
I'm sure we would have heard from many more vendors if it were a far reaching issues.

bwolven's avatar bwolven (2022-11-14 17:48:02 -0500) edit

Try changing the domain in your rets URL to "" with the DASH in it
Then see if your query works without escaping the quotes.

bwolven's avatar bwolven (2022-11-14 18:09:22 -0500) edit

I ran that exact query and it doesn't work for me. When I change the commas to %2C it does work.

weezer311's avatar weezer311 (2022-11-14 18:12:16 -0500) edit

This is the URL I am using. I don't have NGLMLS.

weezer311's avatar weezer311 (2022-11-14 18:13:51 -0500) edit

You tried it with the DASH instead of period in the domain name?

bwolven's avatar bwolven (2022-11-14 18:14:52 -0500) edit

Try it with HTTPS instead of HTTP.
Make sure to set to BASIC authentication for HTTPS.

bwolven's avatar bwolven (2022-11-14 18:16:05 -0500) edit

I was just testing that. The 2 that weren't working were using HTTP. I changed them to HTTPS and it works with multiple commas.

weezer311's avatar weezer311 (2022-11-14 18:40:54 -0500) edit

the version and using https doesn't seem to matter on our end. So what is the take away, that we now have to encode the commas?

jflaig's avatar jflaig (2022-11-15 07:34:07 -0500) edit

@jflaig Were you able to successfully login with HTTPS?
And with HTTPS, did you get the exact same error when commas were included?
Make sure the domain name has the DASH and NOT the DOT when using HTTPS.

bwolven's avatar bwolven (2022-11-15 08:03:45 -0500) edit

Yes. That fixed the original issue.

weezer311's avatar weezer311 (2022-11-15 08:05:46 -0500) edit

yes, but using http vs https seems to have no bearing on this issue, although is weezer311 is saying it fixed the original issue, there is one thing I can try befoire totally ruling that out. Hang on.

jflaig's avatar jflaig (2022-11-15 08:06:06 -0500) edit

Switching from HTTP to HTTPS is what solved the issue of 500 error when passing in more than 2 values separated by commas. Typically I would think these would both being going to the same endpoint but it seems that they are different. Ultimately they should be HTTPS anyway. I just missed converting a few over.

weezer311's avatar weezer311 (2022-11-15 08:13:29 -0500) edit

we have RETS sessions manager which caching the session info, so I have to wait for that to expire for the change to https to take affect.

jflaig's avatar jflaig (2022-11-15 08:27:56 -0500) edit

do you know why I would get this error:

The remote certificate is invalid according to the validation procedure.

trying this https url:

You should see the errors from the last 10 minutes from this ip:

jflaig's avatar jflaig (2022-11-15 09:15:17 -0500) edit

If you change nglmls.rets to nglmls-rets the SSL will be valid.

weezer311's avatar weezer311 (2022-11-15 09:18:54 -0500) edit

I can get that URL to work, but I have to ignore the error basically, which in .Net is done like so when setting up the HttpClient to make the login request:

handler.ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator

jflaig's avatar jflaig (2022-11-15 09:19:07 -0500) edit

ok, I will try that

jflaig's avatar jflaig (2022-11-15 09:24:04 -0500) edit

ok, I think the dash and https solves the problem for us.

jflaig's avatar jflaig (2022-11-15 09:40:02 -0500) edit
add a comment see more comments

1 Answer


@jflaig So you were able to get all your sites working now by switching to HTTPS?

bwolven's avatar
answered 2022-11-16 08:24:13 -0500
edit flag offensive 0 remove flag delete link


yes. I can''t recall seeing any noticed about the url format change.

jflaig's avatar jflaig (2022-11-16 08:26:09 -0500) edit

There are are a few questions highlighted in RED on this site.
There isn't really a way to make them stick to the top but I move them up occasionally
The one about HTTPS mentions the DASH and Basic authentication for HTTPS.
HTTP should still work for a little while yet, but HTTP access will be going away.
I imagine that maybe a firewall or proxy is causing the issue with commas but haven't figured out exactly what yet.

bwolven's avatar bwolven (2022-11-16 08:30:55 -0500) edit

I see. Email blasts would help to.

jflaig's avatar jflaig (2022-11-16 08:38:17 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer