Domain Always Not Available To Register

[1983ltd]

I think I asked you guys about this in early V3....

 

Still having the same problems.

 

Using Namescheap API NOT in sandbox mode.

 

See attached...

 

No matter what domain is attempted to be registered they are ALWAYS returned as not available for registration. No logs are kept after it does a whois so not sure if its using the API to look up the domain availability or not??

 

Also clicking on 'Check availability' hangs the browser for around 60-80 seconds or more before the Not Available page displays!!!!!

[Michael]

I think I asked you guys about this in early V3....

 

Still having the same problems.

 

Using Namescheap API NOT in sandbox mode.

 

See attached...

 

No matter what domain is attempted to be registered they are ALWAYS returned as not available for registration. No logs are kept after it does a whois so not sure if its using the API to look up the domain availability or not??

 

Also clicking on 'Check availability' hangs the browser for around 60-80 seconds or more before the Not Available page displays!!!!!

 

How do you get a domain reseller with Namecheap so I can try their module mate?

[1983ltd]

How do you get a domain reseller with Namecheap so I can try their module mate?

Sign up for one? Namescheap.com The Sandbox is free... But this problem isnt to do with Namescheap I dont think as its not using the module to check if the domain is available... I think...

[Michael]

Sign up for one? Namescheap.com The Sandbox is free... But this problem isnt to do with Namescheap I dont think as its not using the module to check if the domain is available... I think...

 

I think it is the module, as I use Logicboxes module myself and I get that domain is available.

[1983ltd]

I think it is the module, as I use Logicboxes module myself and I get that domain is available.

So a blesta bug then??

[Michael]

So a blesta bug then??

 

I would say it's something to do with the connection of the namecheap module and the namecheap API mate.

[1983ltd]

I registered a domain fine through the module.....? I even transferred a domain just fine... Blesta isnt including any name server info in the output log, so..... Blesta, not API...???

[Bloory]

I'm finding this too.  Not sure what the solution, not a fan of Logicboxes.  I'm happy(ish) to use it until Enom comes out

[Evaske]

Also having this problem with Namecheap

[1983ltd]

I would say it's something to do with the connection of the namecheap module and the namecheap API mate.

I think the above comments are proof its Blesta and not Namescheap...?

 

Any ideas when we can all get this fixed?

[Zoltan]

Same problem here...

[Evaske]

Any fix for this then?

[Michael]

Any fix for this then?

It would be better if someone can open a bug report for the devs to look into it more closely.

[Paul]

We are looking into this, but any solution is unlikely to be in 3.0.4 as that will probably be out today. We will release any updates to the module on the forums as soon as we have something to test.

[Tyson]

This is fixed in v3.0.4.

[1983ltd]

This is fixed in v3.0.4.

Is 3.0.4 out today?

[Paul]

Is 3.0.4 out today?

 

Most likely, it's built and in QA

[1983ltd]

This is fixed in v3.0.4.

 

Doesnt look like it is... Getting exactly the same problem in 3.0.4!

[Michael]

Doesnt look like it is... Getting exactly the same problem in 3.0.4!

 

Did you upgrade the module?

[1983ltd]

yes

[Zoltan]

3.0.4 fixed it for me.

[mitsos]

Hit this bug today.

Blesta v3.0.4

namecheap module v1.0.6

 

If I click transfer the domain is available.

 

If I click check availability the domain is always unavailable.

 

Checking on the namecheap site the domain is available.

 

Checked the namecheap module folder, in v3.0.4 of blesta the .php file says that the namecheap module is 1.0.6. Reuploaded the folder just in case, same thing happens.

 

Did the bug fix change any files outside of the module? Need to upload any other file?

 

EDIT: diff between the two files:

<     private static $version = "1.0.5";
---
>     private static $version = "1.0.6";
1174c1174
<         return $response->DomainCheckResult->{"@attributes"}->Available == "true";
---
>         return strtolower($response->DomainCheckResult->{"@attributes"}->Available) == "true";

[Tyson]

Can you attempt to debug this on your system?

 

Change /components/modules/namecheap/namecheap.php (line 1173):

$response = $result->response();
return strtolower($response->DomainCheckResult->{"@attributes"}->Available) == "true";

to:

$response = $result->response();
var_dump($response);
die;
return strtolower($response->DomainCheckResult->{"@attributes"}->Available) == "true";

 

Then test it again, and let us know the output. And of course, remove these code changes afterward if you're in a live environment.

[Evaske]

3.0.4 fixed this issue for me.

[mitsos]

Can you attempt to debug this on your system?

 

Change /components/modules/namecheap/namecheap.php (line 1173):

$response = $result->response();
return strtolower($response->DomainCheckResult->{"@attributes"}->Available) == "true";

to:

$response = $result->response();
var_dump($response);
die;
return strtolower($response->DomainCheckResult->{"@attributes"}->Available) == "true";

 

Then test it again, and let us know the output. And of course, remove these code changes afterward if you're in a live environment.

 

 

Absolutely no change. Module log is empty as well.

[Tyson]

Absolutely no change. Module log is empty as well.

 

Then it sounds like an OK response was not received from the API, or was not handled.

 

You can update /components/modules/namecheap/apis/namecheap_api.php (line 99):

$response = curl_exec($ch);

 

to:

$response = curl_exec($ch);
if ($response === false)
	echo "ERROR: " . curl_error($ch);

And try checking the availability of a domain again. If you receive an error regarding a hostname unable to resolve, this is likely a DNS configuration issue with your server related to cURL requests.