[GH-ISSUE #3780] Request: Allow us to pass dns_transip_global_key option to certbot #2487

Closed
opened 2026-02-26 07:35:44 +03:00 by kerem · 2 comments
Owner

Originally created by @ghost on GitHub (May 28, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3780

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
      Describe the bug

I've create a TransIP API keypair without whitelist IP requirement.
However cerbot's TransIP plugin creates access tokens with a whitelist ip requirement.
This is annoying because I'm on a dynamic IP.
Certbot can be told to NOT create whitelist protected tokens by setting: dns_transip_global_key = yes
Please add an option for us to pass this flag to certbot.
See: https://github.com/hsmade/certbot-dns-transip/pull/36

Nginx Proxy Manager Version

v2.11.2

To Reproduce
Steps to reproduce the behavior:

  1. Add a certificate using the TransIP DNS provider.
  2. Add your global keypair tp "/etc/letsencrypt/transip-rsa.key"
  3. Set your username: dns_transip_username = xxx
  4. Request a cert:
Encountered exception during recovery: certbot.errors.PluginError: Error finding domain using the Transip API: 401: Remote IP is not authorized for this request; called from IP X

Error finding domain using the Transip API: 401: Remote IP is not authorized for this request; called from IP X

Expected behavior

A shiny new certificate

Screenshots

Operating System

Docker running on Synology DSM 7

Additional context

Originally created by @ghost on GitHub (May 28, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3780 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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 **Describe the bug** <!-- A clear and concise description of what the bug is. --> I've create a TransIP API keypair without whitelist IP requirement. However cerbot's TransIP plugin creates access tokens with a whitelist ip requirement. This is annoying because I'm on a dynamic IP. Certbot can be told to NOT create whitelist protected tokens by setting: ```dns_transip_global_key = yes``` Please add an option for us to pass this flag to certbot. See: https://github.com/hsmade/certbot-dns-transip/pull/36 **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.11.2 **To Reproduce** Steps to reproduce the behavior: 1. Add a certificate using the TransIP DNS provider. 2. Add your global keypair tp "/etc/letsencrypt/transip-rsa.key" 3. Set your username: dns_transip_username = xxx 4. Request a cert: ``` Encountered exception during recovery: certbot.errors.PluginError: Error finding domain using the Transip API: 401: Remote IP is not authorized for this request; called from IP X Error finding domain using the Transip API: 401: Remote IP is not authorized for this request; called from IP X ``` **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> A shiny new certificate **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Docker running on Synology DSM 7 **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 07:35:44 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

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

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

<!-- gh-comment-id:2562075093 --> @github-actions[bot] commented on GitHub (Dec 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Jan 17, 2026):

Issue was closed due to inactivity.

<!-- gh-comment-id:3762514839 --> @github-actions[bot] commented on GitHub (Jan 17, 2026): Issue was closed due to inactivity.
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#2487
No description provided.