First time here? Check out the FAQ!

Could not connect to RESO API - CRC Reality Website

Hi, we have the following error from this website:

We reviewed website error logs this morning and found the following error with the MLS connection issue (Paragon-API). The below error returns from MLS: Could not connect to RESO API ( let us know at (Network error [errno 6]: Could not resolve host:

We've spoke to Mart Caskey this morning. The Client ID and Secret that we're using to make the API connection were confirmed good this morning.

Can you please assist?

You can reach me directly at 256-712-4171.

Thanks, Andy

SWWD's avatar
asked 2023-05-01 10:07:23 -0500
Joe_Brueske's avatar
updated 2023-05-03 15:49:08 -0500
edit flag offensive 0 remove flag close merge delete


Hi Andy,

What kind of a result do you get from a traceroute from your server to Multiple users on our end have used your credentials to connect and pull data without issue. "Could not resolve host" sounds like a connection issue.

Joe_Brueske's avatar Joe_Brueske (2023-05-01 10:36:15 -0500) edit

Joe, what else can we test to find the issue?

SWWD's avatar SWWD (2023-05-02 08:45:32 -0500) edit
add a comment see more comments

2 Answers


Hi Joe, we ran a traceroute from our server and connected without an issue. See screenshot:


It's important to note that our website is connected to another MLS, ValleyMLS, and results are showing without issue.

What else can we test to find the issue?

Thanks, Andy

SWWD's avatar
answered 2023-05-02 08:15:06 -0500
edit flag offensive 0 remove flag delete link


Hi Andy,

I'd recommend using other applications to perform the same types of requests. For instance if you're using cURL, download Postman and follow our instructions here to verify setup. You're at the troubleshooting stage where you've narrowed it down to something with your setup.

Now, bare in mind, ValleyMLS is using RETS, which is completely different. So, if you've been treating the Web API URI as you have been with ValleyMLS, then you need to change everything up.

Joe_Brueske's avatar Joe_Brueske (2023-05-02 08:49:04 -0500) edit

Joe, we are using WebAPI for ValleyMLS not RETS. We switch over to the API connection over a year ago.

SWWD's avatar SWWD (2023-05-02 09:20:13 -0500) edit

Hi Andy,

Then they must be using a different provider other than our PIC or OpenMLS solutions. Regardless, my troubleshooting steps remain unchanged.

Joe_Brueske's avatar Joe_Brueske (2023-05-02 09:22:44 -0500) edit

Ok, understood. What else can we test to find the issue?

SWWD's avatar SWWD (2023-05-02 09:30:30 -0500) edit

Please download Postman and continue your troubleshooting following our guide here has mentioned above.

Joe_Brueske's avatar Joe_Brueske (2023-05-02 09:32:36 -0500) edit

Joe, I ran the Postman job and received an error. What's your email address so I can add you to Postman account to review?

SWWD's avatar SWWD (2023-05-02 10:01:58 -0500) edit
Joe_Brueske's avatar Joe_Brueske (2023-05-02 10:05:55 -0500) edit

invite sent

SWWD's avatar SWWD (2023-05-02 10:15:23 -0500) edit

Receiving this error: 504 Gateway Time-out

SWWD's avatar SWWD (2023-05-02 10:16:10 -0500) edit

client id and secret added to your BK OpenMLS Test. what else do you need to test?

SWWD's avatar SWWD (2023-05-02 10:26:19 -0500) edit

Hi Andy,

I import a JSON collection to the team workspace and received an authorization token, and pulled metadata:

1690 ms

Request Headers
Content-Type: application/x-www-form-urlencoded
Authorization: Basic c21sc2FTaG9hbHNXb3JrczpOWUc2TUlwOTJsaWg=
User-Agent: PostmanRuntime/7.32.2
Accept: */*
Cache-Control: no-cache
Postman-Token: c1b3f914-0dd0-479e-b771-327ea0dbd302
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Request Body

Response Headers
Response Body

Please review at your leisure. I did not see any setup collections or printout in the Console for your query.

Joe_Brueske's avatar Joe_Brueske (2023-05-02 10:27:26 -0500) edit

Joe, what does the above mean? Not familiar with the Postman tool. If setup collections or printout are needed to test, can you add them?

SWWD's avatar SWWD (2023-05-02 10:29:34 -0500) edit

Hi Andy,

Your server is returning can't resolve host. You're troubleshooting to figure out why that's happening. Postman is just a testing tool to compare your setup with. The Collection in Postman here is just a set of HTTP Requests. The output above shows that Postman was able to resolve the host and negotiate authorization to obtain a token. That at least tells you that it's working somewhere else with a different setup. I would recommend checking the Authorization section of the Postman setup, and make sure your client is configured the same way.

Outside of that, I can really only tell you that I'm not a network/server admin, and would be little help to you in troubleshooting server configurations.

Joe_Brueske's avatar Joe_Brueske (2023-05-02 10:36:48 -0500) edit

Joe, can you confirm the MLS ID for Strategic MLS Alliance?

SWWD's avatar SWWD (2023-05-02 10:41:28 -0500) edit

Token URL:

DD 1.7 SystemName:

Metadata URI:

EDIT: The MLSID is smlsa and is part of the URI schema

Joe_Brueske's avatar Joe_Brueske (2023-05-02 10:43:27 -0500) edit

Hi Andy,

I wanted to check in to see if this is now working for you. Also, one of our developers suggested asking you folks for the IP address(es) that you're using. We can check to see if we're blocking any of them.

Also, I forgot to ask, which API client are you folks using?

Joe_Brueske's avatar Joe_Brueske (2023-05-03 15:26:31 -0500) edit


I just noticed higher up you mentioned the error you got using Postman was 504 Gateway Timeout error. Like I said, I'm not a network admin, but maybe there's something within your setup where proxy is involved. Maybe the tracert command works because it's setup correctly, and maybe other pieces aren't? I don't know. Just a suggestion.

Joe_Brueske's avatar Joe_Brueske (2023-05-03 15:37:01 -0500) edit

Joe, the server IP is We are using Realtyna to make the API connection to Strategic MLS Alliance.

It's important to note again, we use Realtyna to connect to 2 separate MLS accounts for CRC Reality; Strategic MLS Alliance (this one is not functioning properly) and ValleyMLS (this one is functioning without issue.

Let me know what your developers say about our IP address, thanks.

SWWD's avatar SWWD (2023-05-04 09:46:16 -0500) edit

Thank you, Andy.

Just to clarify, the API requests are going to come from Realtyna? Do you happen to know the IP or range of IP's they're using?

I'll keep you updated.

Joe_Brueske's avatar Joe_Brueske (2023-05-04 09:50:30 -0500) edit

So are you working with a WordPress site and using the Realtyna plugin to get the API data?
Or is Realtyna actually hosting your site too?

bwolven's avatar bwolven (2023-05-04 10:16:56 -0500) edit

Joe, API requests come from our website via the Realtyna plugin. This has been the exact configuration since the site was launched a few years ago.

Bruce, we host the WordPress site and use the Realtyna plugin to retrieve API data. Again, this has been the exact configuration since the site was launched a few years ago.

SWWD's avatar SWWD (2023-05-04 15:01:36 -0500) edit

Thank you Andy,

Is the plugin running the requests through or a different server? Just want to make sure I understand where that IP address is assigned.

EDIT: Infrastructure checked that IP address already, and we're seeing traffic passing through.

Joe_Brueske's avatar Joe_Brueske (2023-05-04 15:11:16 -0500) edit

Joe and Bruce, do you know if the MLS query based on MlsStatus is still supported to retrieve listings?

SWWD's avatar SWWD (2023-05-04 15:41:20 -0500) edit

The following

Property/$filter=MlsStatus eq 'Active'

gave me the following count:

"@odata.count": 927,
Joe_Brueske's avatar Joe_Brueske (2023-05-04 15:55:37 -0500) edit

Hi Andy,

Both MlsStatus and StandardStatus are valid DD fields. The use is different. StandardStatus has RESO specified lookups, and reflects the state of the contract. MlsStatus however, is used for local or regional statuses. Our view on MlsStatus is that it's the Category vs the individual Statuses. Hope that helps.

Also, we are working on adding messaging so when requested values don't exist, client side messaging isn't just a HTTP 500 error.

Joe_Brueske's avatar Joe_Brueske (2023-05-04 16:37:00 -0500) edit
add a comment see more comments

Joe, Realtyna's support staff discovered the issue. The sync process is working again and new listings are importing.

Here's a breakdown of the issue: The original MLS query we setup to run after migrating from RETS to the API feed stopped retrieving data on March 28, 2023, but ran without issue up to then. We tested the original query this afternoon and it did not return listing data.

Original query: (MlsStatus eq '(11) Active - Active Under Contract' or MlsStatus eq '(10) Active - Active') and ModificationTimestamp ge date+tz

Updated query: We updated the MLS query this afternoon and set it based on StandardStatus: (StandardStatus eq 'Active' or StandardStatus eq 'Active Under Contract') and ModificationTimestamp ge date+tz

Based on the original query no longer retrieving data, Realtyna's support staff believes the MLS query based on MlsStatus is deprecated and no longer supported.

SWWD's avatar
answered 2023-05-04 16:23:29 -0500, updated 2023-05-04 16:56:41 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments

Your Answer

Login/Signup to Answer