mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1633] OVH DNS Renewal fails -- was working before #1225
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#1225
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 @mora-phi on GitHub (Dec 4, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1633
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When auto-renewing a certificate, it fails with the following error :
The docs here https://certbot-dns-ovh.readthedocs.io/en/stable/ say:

If I log into the container and modify the command line to include :
It works.
Nginx Proxy Manager Version
v2.9.12
To Reproduce
Try to renew an OVH certificate
Expected behavior
The certificate is correctly renewed.
Screenshots

If trying to manually renew from the webpage :
Operating System
Docker
Additional context
Was working with a previous NPM version.
Certbot version is 1.21.0
@pifou25 commented on GitHub (Jun 6, 2022):
Hello, I also have a python error when trying to generate certificate using the OVH DNS challenge... seems related to ARM architecture. Here is the full log.
NPM version v2.9.18 (docker latest image) - certbot 1.25.0
I tried to install some (potentially) missing packages into the container, but could not fix this error...
@mjholub commented on GitHub (Oct 22, 2022):
I am facing a similar issue which boils down to certbot reporting my credentials as invalid, even though I double checked them.
Steps to reproduce:
error
Same happens with WebUI, the error message apart from irrelevant traceback output is exactly the same, just w/o the unsafe permissions warning.
@Ramalama2 commented on GitHub (Nov 29, 2022):
I have the exact same error as the one above:
Error determining zone identifier for auth.myhiddendomain.com: 403 Client Error: Forbidden for url: https://eu.api.ovh.com/1.0/domain/zone/. (Are your Application Key and Consumer Key values correct?)
@Ramalama2 commented on GitHub (Nov 30, 2022):
I resolved the issue, it is super stupid.
The solution is, that you have to create a application key for the whole account and all domains in it!

If you restrict access to one domain in your account, certbot wont work!
Here is the solution:
This issue happens only with certbot and is only certbot related.
You can use otherwise restricted application keys with acme.sh/dehydrated and whatever traefik uses works either!
Only certbot doesn't work! For the stupid certbot you have to open your whole account and have fun if someone gets access to your keys...
All your domains will be gone then 👍
That an huge security risk! and this method should be seen only as an solution to get nginx proxy manager working with certbot!
This is not an fix or something. Cheers
@github-actions[bot] commented on GitHub (Feb 29, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 14, 2025):
Issue was closed due to inactivity.