mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #670] letsencrypt wildcard certificates (without aliyun) #566
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#566
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bookser on GitHub (Oct 21, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/670
I would like to be able to use letsencrypt wildcard certificates without being limited to aliyun.
https://www.aliyun.com/
@miguelwill commented on GitHub (Oct 27, 2020):
difficult to implement, since let's encrypt certificates are associated with a specific domain.
wildcard helps to use the same certificate with different sub-domains or host names, but all under one main domain.
@chaptergy commented on GitHub (Nov 5, 2020):
Letsencrypt wildcard certificates are possible using the DNS-challenge. You could request a certificate for
*.example.comand you receive a wildcard certificate. However Aliyun is not yet in the list of the supported DNS providers. You can check which providers are supported in thecertbot-dns-plugins.jsfile.@chaptergy commented on GitHub (May 10, 2021):
FYI, Aliyun has also been available a little while later.