Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Namecheap unable to renew certificates when greater than 10 sub domains using DNS validation #510

Open
1 task done
the1poet opened this issue Oct 4, 2024 · 3 comments

Comments

@the1poet
Copy link

the1poet commented Oct 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

During the certificate renewal process, when starting my docker instance, swag does not start completely when 10 or more subdomains are configured.
When reading the Namecheap API documentation (https://www.namecheap.com/support/api/methods/domains-dns/set-hosts/)
there is reference to this:

IMPORTANT: We recommend you use HTTPPOST method when setting more than 10 hostnames.

Below is a screenshot of the docker config
docker

Expected Behavior

Docker renews certificates and starts as usual.

Steps To Reproduce

  1. Configure more than 10 subdomains
  2. Start SWAG docker

Environment

- OS:Unraid 7.0.0-beta.2
- SWAG version:

CPU architecture

x86-64

Docker creation

see docker screenshot in current behavior

Container logs

dns validation via namecheap plugin is selected
Generating new certificate
Account registered.
Requesting a certificate for my.domain and 12 more domains
Remote: 21
To set: 22
Remote: 22
To set: 23
Remote: 23
To set: 24
Remote: 24
To set: 25
Remote: 25
To set: 26
Remote: 26
To set: 27
Remote: 27
To set: 28
Remote: 28
To set: 29
Remote: 29
To set: 30
Remote: 30
To set: 31
Remote: 31
To set: 32
Remote: 32
To set: 33
Remote: 33
To set: 34
An unexpected error occurred:
lexicon._private.providers.namecheap._ApiError: 1 - Did not receive 200 (Ok) response
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/namecheap.ini file.
Copy link

github-actions bot commented Oct 4, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@j0nnymoe
Copy link
Member

j0nnymoe commented Oct 4, 2024

Any reason why at this point you wouldn't just use a wildcard cert?

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Issues
Development

No branches or pull requests

3 participants