Report bugs to namecheap dns api #2107
Assignees
Labels
3rd party api
report bugs to dns api, deploy hooks and notification hooks
Comments
Neilpang
added
the
3rd party api
|
Does the Namecheap API only work if the domains are actually registered WITH Namecheap? Or will it also work if you have the domains registered elsewhere but the DNS pointed to Namecheap's hosting? All of my domains are registered at Porkbun, but their DNS nameservers are pointed at Namecheap so I can manage them in cPanel. All of the domains show up in Namecheap account but say "Domain is with another registrar." and are greyed out. |
|
I think they should work but I use namecheap's web interface for managing my DNS (not cPanel). If you can call this API endpoint for your domain and get information back, then this plugin should work: https://www.namecheap.com/support/api/methods/domains-dns/get-hosts.aspx |
|
I think this |
|
I am pretty sure I am doing something wrong but when I try mutli domain (both TLD and wild card), keep getting I do see the DNS Entry in my namecheap and the logs show What am I doing wrong? |
|
Hi! The dns_namecheap is almost working for me. When I run:
it creates _acme-challenge TXT entries (I can see them with dig). However validation part is failing: And so it repeats till it runs out of tries and then stops. |
|
Soo, noone really reading these? :( |
|
Thank for reply! I'll check |
|
Wow. I fixed it. This is what it was: I was running it in home network with forced OpenDNS FamilyShield DNS servers. For some reason it considered https://dns.google as malicious address and was replacing it with different address and certificate (Cisco Umbrella CA) that is not in root certificate list. So I removed OpenDNS entries for this box and it works now.
I dont think this is correct. It uses these servers for all domains checks. |
Thank you for putting me in right direction :) |
Does not preserve Dynamic DNS entriesIt would appear that this does not preserve entries that are for Dynamic DNS. In the API, it returns "IsDDNSEnabled=true" if the entry is a Dynamic DNS entry. This gets lost after being read and reapplied. It should be a simple matter of also reading it in and copying it back out when doing the update, but I'm not really sure exactly which kind of edits would be necessary to make this work. |
|
Hmm. I dont think this is fixable anyways as it appears Namecheap's API doesn't allow you to set DDNS for any hosts as far as I can tell. I asked them directly if its possible, so maybe if they respond how to do it, I can work up a patch to fix it. |
|
I have the following error when I execute this command.
|
|
I have confirmed with Namecheap that everything is fine with my API settings. I get this as the response: immediately after trying to add the txt value |
|
For the API access you may need to add in the API of the web host rather than your API if you are running the script via the web host. |
|
The |
|
My site ( I enabled |
|
please provide the logs with |
|
I came across this problem today. Trying to verify using DNS in Namecheap, acme script reports: Which I don't understand because inside Namecheap domain details it says:
Namecheap is the registrar. Nameservers are Any idea why |
|
Hi, @raintonr. I'm no expert, but I just wanted to say that I've been working through this issue, too. I've been on a chat with Namecheap customer support for a couple of hours. We've confirmed that, for whatever reason, the API call only works using BasicDNS, specifically. They stipulate that PremiumDNS/FreeDNS aren't compatible with the API, but that seems to also include Web Hosting DNS. I tried recreating their example API request and got the same error that you showed, above, in Postman. Customer Support ran the same request with my credentials in a sandbox using 'BasicDNS', and it was successful. So, currently I'm switching over from Web Hosting DNS to BasicDNS. It might take a while, but I'll come back and report on whether it resolves the issue or not (and whether my domain records were preserved, or not). |
|
Back to confirm that the switch to BasicDNS did the trick. No more Namecheap API errors. And in case anyone in the future reads this and decides to change nameservers, note that you will need to recreate your DNS host records manually on Namecheap's website. That part threw me off. I saw that my records were still intact in cPanel, and waited for a day for the migration process to finalize, but eventually discovered that all of those records are also stored in Domain List > Advanced DNS. |
|
One last thing. I was actually going to try to suggest an edit to the wiki page, but I can't figure out how, so I'll just write it here, and if anyone smarter can tell me the proper way to do it I'll correct it:
Tonight, I contacted support again to ask them how to find this Server IP. They said there is no way to find it except to ask them for it. I can't verify if that is true or not, but I can't find it anywhere else, so it could be the only way to find it is to ask them. |
|
Thanks for the heads up. Yeah, works fine when I move the domain to Namecheap Basic DNS. FWIW, for |
Here: |
|
Hey all, I am also getting the "error API Key is invalid or API access has not been enabled" error message. I checked and I am already on NameCheap's BasicDNS, so that probably won't be the issue in my case. I have OpnSense running with the ACME Client from which I am trying to issue a wildcard certificate for my internal domain. I see a lot of requests for the --debug 2 logs, but for the life of me I cannot figure out how to trigger the script manually. When I call "acme.sh":
I end up with:
I am not very linux-savvy, so some clear instructions would be useful. |
|
Hi--when attempting Not sure what's going on on the back end, but I've found no results for this issue so I figured I'd post it here in case anyone else runs across it. [Mon May 6 13:06:02 EDT 2024] Http already initialized.
[Mon May 6 13:06:02 EDT 2024] _CURL='curl --silent --dump-header /home/XXXXX/.acme.sh/http.header -L --trace-ascii /tmp/tmp.Yf1X79JRha -g'
[Mon May 6 13:06:02 EDT 2024] _ret='0'
[Mon May 6 13:06:02 EDT 2024] response='<?xml version="1.0" encoding="utf-8"?>
<ApiResponse Status="OK" xmlns="http://api.namecheap.com/xml.response">
<Errors />
<Warnings />
<RequestedCommand>namecheap.domains.dns.gethosts</RequestedCommand>
<CommandResponse Type="namecheap.domains.dns.getHosts">
<DomainDNSGetHostsResult Domain="XXXXX.org" EmailType="NONE" IsUsingOurDNS="true" />
</CommandResponse>
<Server>PHX01APIEXT02</Server>
<GMTTimeDifference>--4:00</GMTTimeDifference>
<ExecutionTime>0.154</ExecutionTime>
</ApiResponse>'
[Mon May 6 13:06:02 EDT 2024] hosts
[Mon May 6 13:06:02 EDT 2024] Hosts not found
[Mon May 6 13:06:02 EDT 2024] Error add txt for domain:_acme-challenge.XXX.org ```
|
|
Hello - Not sure what I can troubleshoot. I even put some echo output into the script - but to no avail. It really seems that the system is stuck processing for the second day |
|
I had more luck by using the Lego Letsencrypt/ACME client. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
This is the place to report bugs in the NameCheap DNS API.
If you experience a bug, please report it in this issue.
Thanks!
The text was updated successfully, but these errors were encountered: