mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #1270] Cannot create/renew Let's Encrypt certificates after fresh VM reinstallation - Create Certificate button disabled #700
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#700
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 @Rossigg on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1270
Describe the bug
After a clean reinstallation of the VM and Nginx UI, the "Create Certificate" button in the Nginx UI web interface is disabled, preventing the creation of new Let's Encrypt SSL certificates. This issue follows a previous problem where automatic and manual certificate renewals for existing sites failed with a 404 Not Found error during the ACME HTTP-01 challenge.
To Reproduce
Note: The exact steps to reach the disabled button state are due to a full VM reinstallation after previous failures. The initial failure steps are provided for context.
Initial Failure Scenario (before reinstallation):
Current Bug (after VM reinstallation):
Expected behavior
Screenshots
Info (please complete the following information):
Additional context
The issue initially started on Saturday morning (July 26, 2025) with automatic certificate renewals failing. Manual attempts to renew or create new certificates via the web interface also failed. The recurring error was:
[Nginx UI] Preparing lego configurations [Nginx UI] ACME User: System Initial User, Email: rossiggws@gmail.com, CA Dir: https://acme-v02.api.letsencrypt.org/directory [Nginx UI] Creating client facilitates communication with the CA server [Nginx UI] Setting HTTP01 challenge provider 2025/07/26 20:20:26 [INFO] [grafana.rossigg.duckdns.org] acme: Trying renewal with 1980 hours remaining 2025/07/26 20:20:26 [INFO] [grafana.rossigg.duckdns.org] acme: Obtaining bundled SAN certificate 2025/07/26 20:20:27 [INFO] [grafana.rossigg.duckdns.org] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/2479542571/559358738651 2025/07/26 20:20:27 [INFO] [grafana.rossigg.duckdns.org] acme: Could not find solver for: tls-alpn-01 2025/07/26 20:20:27 [INFO] [grafana.rossigg.duckdns.org] acme: use http-01 solver 2025/07/26 20:20:27 [INFO] [grafana.rossigg.duckdns.org] acme: Trying to solve HTTP-01 2025/07/26 20:20:32 [INFO] Deactivating auth: https://acme-v02.api.letsencrypt.org/acme/authz/2479542571/559358738651 renew cert error: error: one or more domains had a problem: [grafana.rossigg.duckdns.org] invalid authorization: acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: 77.83.113.151: Invalid response from http://grafana.rossigg.duckdns.org/.well-known/acme-challenge/inRbjGUGGpPmhIYhKUhq6xah_9kIfdO3mtmVcYN_2WWk: 404Despite verifying public IP and DuckDNS resolution for the domains (e.g., grafana.rossigg.duckdns.org), the 404 error persisted. After reinstalling the entire VM to attempt a fresh start, the "Create Certificate" button is now disabled, preventing any certificate management. This suggests a deeper configuration or Nginx UI state issue after reinstallation, or a dependency problem.
@0xJacky commented on GitHub (Jul 28, 2025):
Please provide the content of the current site's configuration file.
@Rossigg commented on GitHub (Jul 28, 2025):
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name homeassistant.rossigg.duckdns.org;
location / {
proxy_pass http://homeassistant.home.lan/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffering off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 90;
}
location ~ /.well-known/acme-challenge {
proxy_set_header Host $host;
proxy_set_header X-Real_IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr:$remote_port;
proxy_pass http://127.0.0.1:9180;
}
}
@0xJacky commented on GitHub (Jul 29, 2025):
It seems that
http://grafana.rossigg.duckdns.orgis not match the server_name of your config (homeassistant.rossigg.duckdns.org)