-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Description
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 wanted to include support for a letsencrypt dns-challenge for domainoffensive.de for myself until the corresponding plugin has been integrated into NPM (see #2055).
I did the following:
-
modified docker-compose.yml by adding the following line unter the "volumes:" section:
- ./app/global/certbot-dns-plugins.js:/app/global/certbot-dns-plugins.js
-
created a folder app/global
-
created a file certbot-dns-plugins.js
-
took the original file from https://raw.githubusercontent.com/NginxProxyManager/nginx-proxy-manager/develop/global/certbot-dns-plugins.js and added the following lines:
//####################################################//
domainoffensive: {
display_name: 'DomainOffensive',
package_name: 'certbot-dns-do',
version_requirement: '~=0.3.0',
dependencies: '',
credentials: 'dns_do_api_token = YOUR_TOKEN',
full_plugin_name: 'dns-do',
}, -
restarted via docker-compose down && docker-compose up -d
-
checked the certbot-dns-plugins.js file via docker exec -it bash - the added content was visible here
Nginx Proxy Manager Version
2.9.18
Expected behavior
I expected to find a new "DomainOffensive" selection when trying to get a Let's Encrypt SSL certificate via dns challenge.
This didn't happen.
Operating System
Debian 11 with latest docker and docker-compose
What am I doing wrong? Any help is appreciated! :-)
Thanks in advance,
David