First time here? Check out the FAQ!

Getting Unauthorized error randomly

  • retag add tags

When we call below url to get data, sometimes data comes correctly, but most of the time we get Unauthorized error.

We have double checked the credentials and its correct. Is there anything in the url below that needs to be corrected?

edit: do we need to whitelist our development server with IRMLS? We've setup a feed successfully for MIBOR, but are running into some errors with IRMLS. If this is an issue on our end, any guidance would be much appreciated! Thank you for the support!

daniel.williams's avatar
asked 2018-05-02 08:59:45 -0500, updated 2018-05-02 09:06:04 -0500
edit flag offensive 0 remove flag close merge delete


Are you still having issues with this after about 6 AM CST this morning?

bwolven's avatar bwolven (2018-05-02 11:12:37 -0500) edit

Yes, we are getting below error:

401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission to view this directory or page using the credentials that you supplied.

daniel.williams's avatar daniel.williams (2018-05-03 00:30:50 -0500) edit

What account name are you using on IRMLS (NO PASSWORDS PLEASE)?

bwolven's avatar bwolven (2018-05-03 10:42:51 -0500) edit

We are using LaFTCKVOW. We are able to connect using a different server, but not on our development server.

daniel.williams's avatar daniel.williams (2018-05-03 11:32:17 -0500) edit

IRMLS has a scheduled weekly refresh that ran from 8:30 pm to 9:30 pm CST last night. You would have been locked out during that period of time. And when I look in our RETS logs I see that's when your logins were failing. One other thing, I don't see in our logs where you are sending any LOGOUT transactions.

bwolven's avatar bwolven (2018-05-03 12:05:06 -0500) edit

Also what is the external IP address for your development server so I can see if it is blocked. Our logs shows requests for this IP:

bwolven's avatar bwolven (2018-05-03 13:43:43 -0500) edit

Hello, I'm checking with my developers.

daniel.williams's avatar daniel.williams (2018-05-04 10:56:53 -0500) edit

While I'm thinking about it, does this forum have the documentation for IRMLS rets? If we aren't doing logout transactions, I would like our dev team to ensure we are following correct procedures.

daniel.williams's avatar daniel.williams (2018-05-04 10:58:18 -0500) edit

Current CST time is 12:12 AM and still we are getting same error. Our IP address is from where we are requesting above url.

daniel.williams's avatar daniel.williams (2018-05-05 00:14:03 -0500) edit

Do you need any additional information from our end to sort this out?

daniel.williams's avatar daniel.williams (2018-05-08 01:18:35 -0500) edit

We put in a request to see if IP: is being blocked. Will let you know when we hear back.

bwolven's avatar bwolven (2018-05-08 10:15:09 -0500) edit

Thank you! We're eager to move forward!

daniel.williams's avatar daniel.williams (2018-05-08 10:16:07 -0500) edit

According to our network personnel, that IP isn't being blocked. Are you sure that is the external IP address? Have you verified the RETS URL and account information you are using is correct? Have you tried doing a login request in a browser like chrome on the development box?

bwolven's avatar bwolven (2018-05-08 13:30:37 -0500) edit

External IP address is correct. RETS URL I already mentioned in the question and account information is correct because it returns data sometime. We already tried in chrome browser.

If you can share email address I can send you screenshot for this as well.

daniel.williams's avatar daniel.williams (2018-05-09 00:48:21 -0500) edit
add a comment see more comments

1 Answer


I wonder if your application isn't handling the Digest CNONCE expiration properly? Some of the older CURL libraries didn't handle this properly for example. If so, that could cause the issue.

Try connecting using HTTPS with Basic authentication and see if the issue persists.

(NOTE: the dash in the URL after MLSID)


bwolven's avatar
answered 2018-05-09 14:32:39 -0500
edit flag offensive 0 remove flag delete link


When we use this url it works fine as you can see in the screenshot

But when we use above url that you mentioned with https it still gives error with same credentials as first url . Please see the screenshot - Error

Can you check the access logs from your end.

daniel.williams's avatar daniel.williams (2018-05-10 01:30:35 -0500) edit

Sorry. You have to do a login first before doing a search request with HTTPS. "" I meant to say try using the HTTPS version of the URL to do your RETS access and see if you still have issues.

bwolven's avatar bwolven (2018-05-10 05:10:25 -0500) edit

Were you able to get it working with HTTPS?

bwolven's avatar bwolven (2018-05-10 15:59:29 -0500) edit

Yes, its working fine with HTTPS. Thanks a lot.

daniel.williams's avatar daniel.williams (2018-05-11 08:18:32 -0500) edit

If it works with HTTPS, it is probably an issue with the Digest NONCE expiration handling I mentioned above. Good to hear it is working.

bwolven's avatar bwolven (2018-05-11 09:12:50 -0500) edit

Thank you again! I sincerely appreciate your help!

daniel.williams's avatar daniel.williams (2018-05-11 09:15:31 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer