[GH-ISSUE #1681] GOOGLE DNS #1255

Closed
opened 2026-02-26 06:36:26 +03:00 by kerem · 4 comments
Owner

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).

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?** <!-- What is this provider called? --> Google **Have you checked if a certbot plugin exists?** <!-- Currently NPM only supports DNS challenge providers for which a certbot plugin exists. You can visit pypi.org, and search for a package with the name `certbot-dns-<privider>`. --> I have problem with PRIVATE KEY, it has problem wiht Invalid control character at: line 5 column 46 (char 182).
kerem 2026-02-26 06:36:26 +03:00
Author
Owner

@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.

<!-- gh-comment-id:1001101589 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:1002473515 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:1002559106 --> @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.
Author
Owner

@jeffryjdelarosa commented on GitHub (Jan 2, 2022):

Nice !

<!-- gh-comment-id:1003722187 --> @jeffryjdelarosa commented on GitHub (Jan 2, 2022): Nice !
Sign in to join this conversation.
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#1255
No description provided.