mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1681] GOOGLE DNS #1255
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#1255
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 @jeffryjdelarosa on GitHub (Dec 24, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1681
What provider would you like to see added to NPM?
Google
Have you checked if a certbot plugin exists?
I have problem with PRIVATE KEY, it has problem wiht Invalid control character at: line 5 column 46 (char 182).
@mcowger commented on GitHub (Dec 26, 2021):
I'm seeing the same behavior. The same credential file works fine on certbot 1.22.0 on my laptop, which is the same version as in the image.
If I manually copy the .json file into the volume and run certbot on the CLI the request is successful, so I suspect this is something in how the file is saved to disk.
@chaptergy commented on GitHub (Dec 29, 2021):
I have just checked, the json string should be saved to file exactly as provided. What character is in line 5 column 46 (char 182)? So what character is causing this? Maybe this could have something to do with https://github.com/jc21/nginx-proxy-manager/pull/1697, but since you said your image runs with certbot 1.22.0, which is the newest version, this shouldn't be the case.
@jeffryjdelarosa commented on GitHub (Dec 29, 2021):
The character is /n then I replaced it for //n, then it jumped to the next /n, so what I did was replaced them all. After It takes some time and I got an error when I look at the logs it said the _acme txt is not correct.
@jeffryjdelarosa commented on GitHub (Jan 2, 2022):
Nice !