cert.pem to be a symlink #2628

New issue

Open

opened 2026-02-26 07:36:16 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:36:16 +03:00

Owner

Originally created by @xinmans on GitHub (Sep 30, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4030

Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.
[9/30/2024] [10:20:50 AM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates via Aliyun for Cert #13: vscode.lab.xxxxxxx.top
[9/30/2024] [10:20:50 AM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-13" --disable-hook-validation --no-random-sleep-on-renew
[9/30/2024] [10:20:50 AM] [Global ] › ⬤ debug CMD: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-13" --disable-hook-validation --no-random-sleep-on-renew
[9/30/2024] [10:20:54 AM] [Express ] › ⚠ warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Renewal configuration file /etc/letsencrypt/renewal/npm-13.conf is broken.
The error was: expected /etc/letsencrypt/live/npm-13/cert.pem to be a symlink

.
0 renew failure(s), 1 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

Originally created by @xinmans on GitHub (Sep 30, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4030 Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details. [9/30/2024] [10:20:50 AM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates via Aliyun for Cert #13: vscode.lab.xxxxxxx.top [9/30/2024] [10:20:50 AM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-13" --disable-hook-validation --no-random-sleep-on-renew [9/30/2024] [10:20:50 AM] [Global ] › ⬤ debug CMD: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-13" --disable-hook-validation --no-random-sleep-on-renew [9/30/2024] [10:20:54 AM] [Express ] › ⚠ warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Renewal configuration file /etc/letsencrypt/renewal/npm-13.conf is broken. The error was: expected /etc/letsencrypt/live/npm-13/cert.pem to be a symlink . 0 renew failure(s), 1 parse failure(s) Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

kerem added the

stale

bug

labels

2026-02-26 07:36:16 +03:00

kerem commented

2026-02-26 07:36:16 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 16, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (May 16, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2628

No description provided.

Rows
Columns