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 #2633] "Error determining zone_id: 9109" upon attempted renewal #1826

New issue

Open

opened 2026-02-26 07:32:37 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:32:37 +03:00

Owner

Originally created by @glassman81 on GitHub (Feb 26, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2633

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Nginx Proxy Manager Version
v2.3.19

Describe the bug

When attempting to renew a letsencrypt cert using cloudflare, an error message is received ragarding the zone id:

[2/26/2023] [3:54:06 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-5 with error: Error determining zone_id: 9109 Invalid access token. Please confirm that you have supplied valid Cloudflare API credentials. (Did you enter a valid Cloudflare Token?)
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
QueryBuilder#allowEager method is deprecated. You should use allowGraph instead. allowEager method will be removed in 3.0
QueryBuilder#eager method is deprecated. You should use the withGraphFetched method instead. eager method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
[2/26/2023] [3:57:14 AM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates via Cloudflare for Cert #5: *.mydomain.com
[2/26/2023] [3:57:14 AM] [SSL ] › ℹ info Command: certbot renew --config "/etc/letsencrypt.ini" --cert-name "npm-5" --disable-hook-validation --no-random-sleep-on-renew
[2/26/2023] [3:57:15 AM] [Express ] › ⚠ warning Command failed: certbot renew --config "/etc/letsencrypt.ini" --cert-name "npm-5" --disable-hook-validation --no-random-sleep-on-renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Failed to renew certificate npm-5 with error: Error determining zone_id: 9109 Invalid access token. Please confirm that you have supplied valid Cloudflare API credentials. (Did you enter a valid Cloudflare Token?)
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
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.

The following is the content from the letsencrypt.log file:

File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main
return internal_main.main(cli_args)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1862, in main
return config.func(config, plugins)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1634, in renew
renewal.handle_renewal_request(config)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/renewal.py", line 552, in handle_renewal_request
f"{len(renew_failures)} renew failure(s), {len(parse_failures)} parse failure(s)")
certbot.errors.Error: 1 renew failure(s), 0 parse failure(s)
2023-02-26 03:57:15,822:ERROR:certbot._internal.log:1 renew failure(s), 0 parse failure(s)

Originally created by @glassman81 on GitHub (Feb 26, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2633 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Nginx Proxy Manager Version** v2.3.19 **Describe the bug** When attempting to renew a letsencrypt cert using cloudflare, an error message is received ragarding the zone id: [2/26/2023] [3:54:06 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Failed to renew certificate npm-5 with error: Error determining zone_id: 9109 Invalid access token. Please confirm that you have supplied valid Cloudflare API credentials. (Did you enter a valid Cloudflare Token?) All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/npm-5/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0. [2/26/2023] [3:57:14 AM] [SSL ] › ℹ info Renewing Let'sEncrypt certificates via Cloudflare for Cert #5: *.mydomain.com [2/26/2023] [3:57:14 AM] [SSL ] › ℹ info Command: certbot renew --config "/etc/letsencrypt.ini" --cert-name "npm-5" --disable-hook-validation --no-random-sleep-on-renew [2/26/2023] [3:57:15 AM] [Express ] › ⚠ warning Command failed: certbot renew --config "/etc/letsencrypt.ini" --cert-name "npm-5" --disable-hook-validation --no-random-sleep-on-renew Saving debug log to /var/log/letsencrypt/letsencrypt.log Failed to renew certificate npm-5 with error: Error determining zone_id: 9109 Invalid access token. Please confirm that you have supplied valid Cloudflare API credentials. (Did you enter a valid Cloudflare Token?) All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/npm-5/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) 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. The following is the content from the letsencrypt.log file: File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main return internal_main.main(cli_args) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1862, in main return config.func(config, plugins) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1634, in renew renewal.handle_renewal_request(config) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/renewal.py", line 552, in handle_renewal_request f"{len(renew_failures)} renew failure(s), {len(parse_failures)} parse failure(s)") certbot.errors.Error: 1 renew failure(s), 0 parse failure(s) 2023-02-26 03:57:15,822:ERROR:certbot._internal.log:1 renew failure(s), 0 parse failure(s)

kerem added the

stale

bug

labels

2026-02-26 07:32:37 +03:00

kerem commented

2026-02-26 07:32:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 27, 2024):

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

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

kerem commented

2026-02-26 07:32:37 +03:00

Author

Owner

@PexalDev commented on GitHub (Apr 8, 2024):

i have same error, how to solve it?

@PexalDev commented on GitHub (Apr 8, 2024): i have same error, how to solve it?

kerem commented

2026-02-26 07:32:37 +03:00

Author

Owner

@chminsc commented on GitHub (Aug 3, 2024):

same here

@chminsc commented on GitHub (Aug 3, 2024): same here

kerem commented

2026-02-26 07:32:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 13, 2025):

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

@github-actions[bot] commented on GitHub (Mar 13, 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#1826

No description provided.

Rows
Columns