Paragon - South Central Kentucky

[Andy Wallace]

We've been having an issue for the last week or so - our PHRETS code cannot connect to this MLS's server,  even though our older process using cURL is working fine, with the same credentials. RETSMd is able to get in without issue.  Anyone have a suggestion? It had been working at one point.

[Eric Culus]

What error message are you getting?

I would advice to work in steps. Connect using sheets and see which error you get back

Is could be rets version not correct

On Wed, 13 Jul 2022, 07:41 Andy Wallace, <awal...@ihouseweb.com> wrote:

We've been having an issue for the last week or so - our PHRETS code cannot connect to this MLS's server,  even though our older process using cURL is working fine, with the same credentials. RETSMd is able to get in without issue.  Anyone have a suggestion? It had been working at one point.

--
You received this message because you are subscribed to the Google Groups "PHRETS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phrets+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/phrets/7f115cd9-928c-4cc6-a779-ae8b56069698n%40googlegroups.com.

[Andy Wallace]

The error we get is:

GET http://gbrmls.apps.retsiq.com/contactlps/rets/login` resulted in a `401 Unauthorized` response

I'm using the same credentials in RETSMd, and they work fine.   I don't understand what you mean "Connect using sheets". This is only one of the MLSes we're connecting to, but this one and one other are suddenly giving us problems.

[Eric Culus]

Oh, yeah, this must be the autocorrect ;)

Using phrets you can var_dump the whole error message.

Alternatively, is paragon blocking the IP? Some rets services can only work on specific agreed IP addresses. Check your technology vendor contract on this.

To view this discussion on the web visit https://groups.google.com/d/msgid/phrets/920e796d-1dfe-41eb-a4fe-2bf1285affbbn%40googlegroups.com.

[Andy Wallace]

Hm... well, the rets session Login function throws an exception, and all I get in the exception is that text. I'll check on the static IP possibility