NameCheap API

[Yalla Domains]

Hi,

I am trying to use the Queue to get a list of my domains from namecheap, but it is not working. It still says pending.  I ran the tasker, still nothing. I tried it with namesilo, it took bit long, but it pulled the domains list. Why it is not working with namecheap?

I have these:

• Registrar Account Username (saved)
• API Key (saved)
• Connecting IP Address (saved)

My API was approved by them, and my IP address is already added at namecheap. 

Still it says Pending and not able to pull the domains list.

Their support says that they need to know the API call and request to check the problem.

Any idea why it is not working and how to solve it?

Thx

[Greg Chetcuti]

If this is working for other registrars, it has to be something to do with the API credentials. I just tested domain imports with Namecheap myself and they worked just fine (screenshot: http://i.imgur.com/WC8g13s.png).

If you're trying to retrieve the full domain list, this is the command that's being run:

https://api.namecheap.com/xml.response?&ApiUser=[ACCOUNT_USERNAME]&ApiKey=[API_KEY]&UserName=[ACCOUNT_USERNAME]&Command=namecheap.domains.getList&ClientIp=[WHITELISTED_IP]&PageSize=100

The following will need to be substituted with your own information:

[ACCOUNT_USERNAME]

[API_KEY]

[WHITELISTED_IP]

[Yalla Domains]

Hi,

it is still not working with Namecheap API. I changed host and still the same problem.

if I give you the DomainMod installation admin login can you check it? 

or can you tell what else should I check for to make it work?

Namecheap confirmed that the API key is correct and the IP is whitelisted and the host confirmed that they have nothing from their end stopping it from working

[Yalla Domains]

This is what I got from namecheap:

"According to the screenshot, the settings are properly configured in your DomainMOD account. 

However, the error seems to be related to the run.php file. In order to resolve the issue, please contact DomainMOD development team for them to check it on their side."

Any idea on how to fix this?

thanks

On Sunday, April 9, 2017 at 2:11:35 AM UTC-5, Greg Chetcuti wrote:

[Greg Chetcuti]

This is very strange, I'm not sure why this wouldn't be working for you.

I'd recommend going through the Debugging section of our Troubleshooting guide, which will give us additional information that will help us better understand what's going wrong here.

https://domainmod.org/docs/userguide/troubleshooting/#debugging

[Greg Chetcuti]

Yalla Domains, I just realized that you contacted us separately with a log file, and that you'd also posted another message here (which is now deleted) with the results of an XML file.

The log file you sent gives the error, "Unable to get domain list", which means there is a problem connecting to Namecheap, and the XML file you posted here gives an error related to an incorrect IP address.

<ApiResponse xmlns="http://api.namecheap.com/xml.response" Status="ERROR">

<Errors>

<Error Number="1011105">Parameter ClientIP is invalid</Error>

</Errors>

It sounds like maybe the IP address you have recorded at Namecheap is not the IP address that your web server is connecting from. I believe I've seen this one other time in the past, that the actual hosting IP address was different from the IP address trying to connect to the registrar, and it was related to the user's web hosting setup. You may want to reach out to your hosting company and explain the situation, and see if your web server is broadcasting from a different IP address.

[Yalla Domains]

the xml response is from my browser, because my laptop IP changes.

here is where we stand now:

When I use my browser with my laptop IP whitelisted, I get the xml response that shows my domains. So from my laptop it is working now.

From the DomainMod, hosted on InmotionHosting, and another hosted on Namecheap itself,

They are saying that your script might be sending the api call from the user ip instead of the server ip, but i tried both, the server ip and the laptop ip and it did not work.

it is not working on two different hosting accounts, some reason I keep getting this error;

class.namecheap

error

Unable to get domain list

User ID: 1 Extra: "Username":"XXXXX", "API Key":"XXXXXX", "IP Address":"XXXXXXX" URL: /admin/scheduler/run.php?id=1 Insert Time: 2018-04-02 10:47:47
	2	class.namecheap	error

Unable to get domain list

User ID: 1 Extra: "Username":"XXXXXX", "API Key":"XXXXXXXXXX", "IP Address":"XXXXXXXX" URL: /admin/scheduler/run.php?id=1 Insert Time: 2018-04-02 10:47:36
	1	/admin/scheduler/run.php	info	[START] Process Domain Queue
User ID: 1 Extra: "Task ID":"1", "Name":"Domain Queue Processing", "Slug":"domain-queue", "Expression":"*/5 * * * * *", "Active":"1", "Next Run":"2018-04-02 17:50:00" URL: /admin/scheduler/run.php?id=1

I changed the username, api key and ip address to XXX but this is the exact message I get in the debugging log.

I can give you access to the admin section of the script to see it yourself, if you can help.

[Greg Chetcuti]

Unfortunately DomainMOD has no control over what IP address is used when connecting to an outside service, that's all handled by the web server.

I implemented something in a new version today that will help us figure out the IP addresses with absolute certainty though. If you install the newest version (v4.09.03), there's an area on the System Information page (Administration -> System Information) that says Web Server IP Address (Remote) (it's important that you're looking at the one that has "Remote" in the name). This is the IP address that your DomainMOD installation uses to contact the outside world.

This IP address is returned by a remote service called ipify (https://www.ipify.org), and DomainMOD connects to it using the exact same method that it uses to connect to the domain registrar APIs, so this IP address is the one you want to whitelist with the registrars.

[Greg Chetcuti]

Yalla Domains confirmed via email that the IP address shown in the Web Server IP Address (Remote) section was the correct one for registrar whitelisting, and this is now working.