The connection is being refused. Is there some firewall block on your end? Our server IP is: 72.34.59.139.
From the phrets.php class, the debug shows:
* Trying 208.93.242.167...
* TCP_NODELAY set
* connect to 208.93.242.167 port 80 failed: Connection refused
* Failed to connect to neren.rets.paragonrels.com port 80: Connection refused
* Closing connection 0
I tried directly from curl and the response is (password blanked out):
# curl -k -u bia0617:################### https://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.5
curl: (7) couldn't connect to host
I tried curl from my local machine and it seems to work fine:
$ curl -k -u bia0617:################### https://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.5
<RETS ReplyCode="0" ReplyText="Login Request" >
<RETS-RESPONSE>
MemberName=Ski Cntry RE IDX RETS User
User=bia0617,1,21,279113
Broker=4838,4838
MetadataVersion=18.12.8208
MinMetadataVersion=18.12.8208
TimeoutSeconds=7200
GetMetadata=/rets/fnisrets.aspx/NEREN/getmetadata
GetObject=/rets/fnisrets.aspx/NEREN/getobject
Login=/rets/fnisrets.aspx/NEREN/login
Logout=/rets/fnisrets.aspx/NEREN/logout
Search=/rets/fnisrets.aspx/NEREN/search
</RETS-RESPONSE>
</RETS>
BTW: without the -k option, curl complains that the SSL certificate is not valid. And so does Google Chrome, when I try to connect directly from a browser. Probably because the certificate is a wildcard cert *.paragonrels.com.
Is it the actual login request that is failing?