[GH-ISSUE #4461] cdmon dns plugin certbot #2854

Closed
opened 2026-02-26 07:37:00 +03:00 by kerem · 1 comment
Owner

Originally created by @rascazzione on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4461

What provider would you like to see added to NPM?

cdmon.com, they are an Spanish domain and DNS provider and offer free DNS services. I've created the certbot plugin, tested, and deployed as a pip package, after some weecknds working on it ;D

Have you checked if a certbot plugin exists?

Yes, certbot exists as a pip package

https://pypi.org/project/certbot-dns-cdmon/

And here is the git directory

https://github.com/rascazzione/certbot-dns-cdmon

I've prepared the data for certbot-dns-plugins.json

	"cdmon": {
		"name": "cdmon",
		"package_name": "certbot-dns-cdmon",
		"version": "~=0.3.2",
		"dependencies": "",
		"credentials": "dns_cdmon_api_key=your-cdmon-api-token",
		"full_plugin_name": "dns-cdmon"
	},

I tried to compile the image, but I don't know why it doesn't appear in the compiled image after modifying and recompiling via docker compose (maybe it is necessary to rebuild frontend?).

Thank you very much!!!

Originally created by @rascazzione on GitHub (Mar 30, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4461 **What provider would you like to see added to NPM?** cdmon.com, they are an Spanish domain and DNS provider and offer free DNS services. I've created the certbot plugin, tested, and deployed as a pip package, after some weecknds working on it ;D **Have you checked if a certbot plugin exists?** Yes, certbot exists as a pip package https://pypi.org/project/certbot-dns-cdmon/ And here is the git directory https://github.com/rascazzione/certbot-dns-cdmon I've prepared the data for certbot-dns-plugins.json ``` "cdmon": { "name": "cdmon", "package_name": "certbot-dns-cdmon", "version": "~=0.3.2", "dependencies": "", "credentials": "dns_cdmon_api_key=your-cdmon-api-token", "full_plugin_name": "dns-cdmon" }, ``` I tried to compile the image, but I don't know why it doesn't appear in the compiled image after modifying and recompiling via docker compose (maybe it is necessary to rebuild frontend?). Thank you very much!!!
kerem 2026-02-26 07:37:00 +03:00
Author
Owner

@rascazzione commented on GitHub (Apr 5, 2025):

In the end I was able to test it when recompiling the frontend, I just had to execute the script that is already enabled (after some research I found it).

sudo ./scripts/ci/frontend-build

Then create a docker-compose.yml with

services:
  app:
    build:
      # Specifies the path to the directory containing the Dockerfile and source code
      context: ${REPO_PATH}/nginx-proxy-manager
      # Specifies the path to the Dockerfile RELATIVE to the context above
      dockerfile: docker/Dockerfile
    restart: unless-stopped
    ports:
      # These ports are exposed on your host machine.
      - '80:80'    # HTTP traffic
      - '81:81'    # Admin interface
      - '443:443'  # HTTPS traffic
    volumes:
      # These volumes persist data outside the container.
      # Ensure these paths (./data, ./letsencrypt) exist where you run docker-compose
      # or use absolute paths if preferred.
      - ${DATA_PATH}/data:/data                     # NPM data (configurations, users, etc.)
      - ${LETS_ENCRYPT_PATH}/letsencrypt:/etc/letsencrypt   # Let's Encrypt certificates

sudo docker compose up -d --build

When testing it, I saw that the plugin had a bug that I have corrected and I have updated to version 0.4.1

 "cdmon": {
                "name": "cdmon",
                "package_name": "certbot-dns-cdmon",
                "version": "~=0.4.1",
                "dependencies": "",
                "credentials": "dns_cdmon_api_key=your-cdmon-api-token\ndns_cdmon_domain=your_domain_is_optional",
                "full_plugin_name": "dns-cdmon"
        },

And here is my first certificate with cdmon and nginx proxy manager :D

Image

PD. Sorry for the multiples edits

<!-- gh-comment-id:2780915562 --> @rascazzione commented on GitHub (Apr 5, 2025): In the end I was able to test it when recompiling the frontend, I just had to execute the script that is already enabled (after some research I found it). `sudo ./scripts/ci/frontend-build` Then create a docker-compose.yml with ``` yaml services: app: build: # Specifies the path to the directory containing the Dockerfile and source code context: ${REPO_PATH}/nginx-proxy-manager # Specifies the path to the Dockerfile RELATIVE to the context above dockerfile: docker/Dockerfile restart: unless-stopped ports: # These ports are exposed on your host machine. - '80:80' # HTTP traffic - '81:81' # Admin interface - '443:443' # HTTPS traffic volumes: # These volumes persist data outside the container. # Ensure these paths (./data, ./letsencrypt) exist where you run docker-compose # or use absolute paths if preferred. - ${DATA_PATH}/data:/data # NPM data (configurations, users, etc.) - ${LETS_ENCRYPT_PATH}/letsencrypt:/etc/letsencrypt # Let's Encrypt certificates ``` `sudo docker compose up -d --build` When testing it, I saw that the plugin had a bug that I have corrected and I have updated to version 0.4.1 ``` "cdmon": { "name": "cdmon", "package_name": "certbot-dns-cdmon", "version": "~=0.4.1", "dependencies": "", "credentials": "dns_cdmon_api_key=your-cdmon-api-token\ndns_cdmon_domain=your_domain_is_optional", "full_plugin_name": "dns-cdmon" }, ``` And here is my first certificate with cdmon and nginx proxy manager :D ![Image](https://github.com/user-attachments/assets/7cbe43b7-ffe5-4573-8fbc-c09c97293b8a) PD. Sorry for the multiples edits
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#2854
No description provided.