starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2048] SSL Certs are not auto-renewing -> log error: "Another instance of Certbot is already running" #1482

New issue

Open

opened 2026-02-26 07:31:14 +03:00 by kerem · 14 comments

kerem commented

2026-02-26 07:31:14 +03:00

Owner

Originally created by @maltokyo on GitHub (May 12, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2048

SSL Certs are not auto-renewing (for all of my domains).

So I went into the WebGUI and tried to manually renew the SSL Certificates

Manual renewal worked for one domain, and then from the second domain that had expired, when I choose "renew now" I got the error in a red banner in the webGUI just saying "Internal Error".

So, I checked logs and it contains the following error for all the domains that are not renewed:

"Another instance of Certbot is already running"

Could anyone help, who might have a permanent fix for this?

Full log below:

nginx_proxy_manager    | [5/12/2022] [8:35:50 AM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #17: my.domain.com
nginx_proxy_manager    | [5/12/2022] [8:35:50 AM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-17" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
nginx_proxy_manager    | [5/12/2022] [8:35:51 AM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-17" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
nginx_proxy_manager    | Another instance of Certbot is already running.
nginx_proxy_manager    | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/tmp0k76co9u/log or re-run Certbot with -v for more details.
nginx_proxy_manager    |

Originally created by @maltokyo on GitHub (May 12, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2048 SSL Certs are not auto-renewing (for all of my domains). So I went into the WebGUI and tried to manually renew the SSL Certificates Manual renewal worked for one domain, and then from the second domain that had expired, when I choose "renew now" I got the error in a red banner in the webGUI just saying "Internal Error". So, I checked logs and it contains the following error for all the domains that are not renewed: **"Another instance of Certbot is already running"** Could anyone help, who might have a permanent fix for this? Full log below: ``` nginx_proxy_manager | [5/12/2022] [8:35:50 AM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates for Cert #17: my.domain.com nginx_proxy_manager | [5/12/2022] [8:35:50 AM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-17" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation nginx_proxy_manager | [5/12/2022] [8:35:51 AM] [Express ] › ⚠ warning Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-17" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation nginx_proxy_manager | Another instance of Certbot is already running. nginx_proxy_manager | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/tmp0k76co9u/log or re-run Certbot with -v for more details. nginx_proxy_manager | ```

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@source011 commented on GitHub (May 14, 2022):

@source011 commented on GitHub (May 14, 2022): +1

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@maltokyo commented on GitHub (May 19, 2022):

Would anyone have any insights?

@maltokyo commented on GitHub (May 19, 2022): Would anyone have any insights?

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@source011 commented on GitHub (May 19, 2022):

Would anyone have any insights?

I ended up doing the DNS challenge as a work around for now.

@source011 commented on GitHub (May 19, 2022): > Would anyone have any insights? I ended up doing the DNS challenge as a work around for now.

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@maltokyo commented on GitHub (May 20, 2022):

Thank you, will try that. Not sure how to go about it though, will dig around.

@maltokyo commented on GitHub (May 20, 2022): Thank you, will try that. Not sure how to go about it though, will dig around.

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@mat-m commented on GitHub (Jun 4, 2022):

Rolling back from 2.9.18 to 2.9.15 fixes it for me.

@mat-m commented on GitHub (Jun 4, 2022): Rolling back from 2.9.18 to 2.9.15 fixes it for me.

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@flufftronix commented on GitHub (Jun 10, 2022):

I had the same issue, running these inside the app container in 2.9.18 fixed it for me:

pip uninstall certbot
pip install certbot

@flufftronix commented on GitHub (Jun 10, 2022): I had the same issue, running these inside the app container in 2.9.18 fixed it for me: ``` pip uninstall certbot pip install certbot ```

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@daominhsangvn commented on GitHub (Aug 4, 2022):

I resolved the problem by this post
https://community.letsencrypt.org/t/solved-another-instance-of-certbot-is-already-running/44690

Basically just find and remove all lockfile which lock the certbot

@daominhsangvn commented on GitHub (Aug 4, 2022): I resolved the problem by this post https://community.letsencrypt.org/t/solved-another-instance-of-certbot-is-already-running/44690 Basically just find and remove all lockfile which lock the certbot

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@EDIflyer commented on GitHub (Oct 7, 2022):

Thanks @daominhsangvn - that did the trick for me! For those having issues with it not renewing when Force SSL is enabled then this PR fixes that too - https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2038

@EDIflyer commented on GitHub (Oct 7, 2022): Thanks @daominhsangvn - that did the trick for me! For those having issues with it not renewing when Force SSL is enabled then this PR fixes that too - https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2038

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 17, 2024):

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

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

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@maltokyo commented on GitHub (Feb 19, 2024):

Not stale

@maltokyo commented on GitHub (Feb 19, 2024): Not stale

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 26, 2024):

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

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

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@maltokyo commented on GitHub (Nov 26, 2024):

Crazy this is not fixed

On Tue, Nov 26, 2024, 3:07 AM github-actions[bot] @.***>
wrote:

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

—
Reply to this email directly, view it on GitHub
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2048#issuecomment-2499459889,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKS7WZVGB4T4EBNFQXDWTT2CPJWLAVCNFSM6AAAAABSPKDHOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGQ2TSOBYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@maltokyo commented on GitHub (Nov 26, 2024): Crazy this is not fixed On Tue, Nov 26, 2024, 3:07 AM github-actions[bot] ***@***.***> wrote: > Issue is now considered stale. If you want to keep it open, please comment > 👍 > > — > Reply to this email directly, view it on GitHub > <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2048#issuecomment-2499459889>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKS7WZVGB4T4EBNFQXDWTT2CPJWLAVCNFSM6AAAAABSPKDHOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGQ2TSOBYHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

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

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

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

kerem commented

2026-02-26 07:31:15 +03:00

Author

Owner

@EDIflyer commented on GitHub (Aug 17, 2025):

In my experience https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3121 fixes this

@EDIflyer commented on GitHub (Aug 17, 2025): In my experience https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3121 fixes this

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#1482

No description provided.

Rows
Columns