Netregistry

[trevor4370]

Has anybody successfully connected to netregistry (API)?

 

I get the following error

Registrar Error

SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't find in 'https://theconsole.netregistry.com.au/external/services/ResellerAPIService/?wsdl' in /home/countryb/public_html/whmcs/modules/registrars/netregistry/netregistry.php:28 Stack trace: #0 /home/countryb/public_html/whmcs/modules/registrars/netregistry/netregistry.php(28): SoapClient->SoapClient('https://thecons...', Array) #1 /home/countryb/public_html/whmcs/modules/registrars/netregistry/netregistry.php(213): getSOAPClient() #2 /home/countryb/public_html/whmcs/includes/registrarfunctions.php(0) : eval()'d code(1): netregistry_GetNameservers('BREFFB-API', 'XsX15EDhc6x2ToT...', '', '') #3 /home/countryb/public_html/whmcs/includes/registrarfunctions.php(0): unknown() #4 /home/countryb/public_html/whmcs/admin/clientsdomains.php(0): RegGetNameservers() #5 {main}

 

Netregistry said

"The URL "https://theconsole.netregistry.com.au/external/services

ResellerAPIService/?wsdl" seems to work properly via webbrowser.

It seems to say the server can't connect to the api. Make

sure it is not behind a firewall and allows connections out to port 80

from that machine. Make sure the proxy is setup correctly. "

 

 

WHMCVS support also said

"The "couldn't load from https://theconsole.netregistry.com.au/external/services/ResellerAPIService/?wsdl" error would tend to indicate some kind of server side firewall block similar to the above as the url is fine. Your server admin will need to ensure that URL can be access from your server."

 

 

There are other hosting companies who use WHMCS on this server no problems, although they are not with Netregistry. Anybody got any ideas?

 

Thanks

[MarkPBrush]

I'm getting the same error message (give or take).

 

My hosting provider has white-listed Netregistry. Netregistry aren't changing anything just for an isolated issue, but suggested I turn off Windows firewall. When pressed, they stated that port 443 is open.

 

If anyone has got past this error, I'd be very pleased to hear how they did it.

 

I don't have a huge number of domains to transfer but it may take less energy to fix the problem than to hop "out of the frying pan".

[MarkPBrush]

I've had the same problem and have noticed it dotted about these posts with no signs of resolution.

 

My hosting provider (Web Hosts Australia - who I'd have no hesitation in recommending) was quick to white-list NR but the latter wasn't able to provide much assistance.

 

Rather than start shuffling Domains about, I've applied to become a Planetdomain reseller, being up-front about my Netregistry connection. I haven't seen any problems listed here about the Planetdomain API so, fingers-crossed.

 

If anyone's still got the NR issue and is interested in how I get on, reply here and I'll keep you posted.

 

Optimistically,

Mark