# Nginx proxy manager SSL **URL:** \ **Category:** Aide (en français)\ **Created:** [August 25, 2023, 1:22pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078 "2023-08-25T13:22:23Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 1:22pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/1 "2023-08-25T13:22:23Z")
Je peux lire des réponses en Anglais : yes Mon nom de domaine est : [hocishome.duckdns.org](http://hocishome.duckdns.org) Bonjour ! Ravi de faire parti de la communauté ! Je cherche depuis des heures parmi plein de sujets et rien ne fonctionne... Je suis neophyte. J’ai exécuté cette commande : Bonjour, J'essaie de rendre possible l'accès à Homeassistant depuis l'extérieur pour faire remonter mes appareils sur alexa ensuite, avec duckdns en docker portainer. Je n'arrive pas à donner les certificats et rendre le [https://hocishome.duckdns.org](https://hocishome.duckdns.org) fonctionnel. Elle a produit cette sortie : > ❯ Starting backend ... > [8/25/2023] [1:12:45 PM] [Global] › ℹ info Using MySQL configuration > [8/25/2023] [1:12:47 PM] [Migrate] › ℹ info Current database version: 20211108145214 > [8/25/2023] [1:12:47 PM] [Setup] › ℹ info Logrotate Timer initialized > [8/25/2023] [1:12:47 PM] [Setup] › ℹ info Logrotate completed. > [8/25/2023] [1:12:47 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... > [8/25/2023] [1:12:47 PM] [IP Ranges] › ℹ info Fetching [https://ip-ranges.amazonaws.com/ip-ranges.json](https://ip-ranges.amazonaws.com/ip-ranges.json) > [8/25/2023] [1:12:48 PM] [IP Ranges] › ℹ info Fetching [https://www.cloudflare.com/ips-v4](https://www.cloudflare.com/ips-v4) > [8/25/2023] [1:12:48 PM] [IP Ranges] › ℹ info Fetching [https://www.cloudflare.com/ips-v6](https://www.cloudflare.com/ips-v6) > [8/25/2023] [1:12:48 PM] [SSL] › ℹ info Let's Encrypt Renewal Timer initialized > [8/25/2023] [1:12:48 PM] [SSL] › ℹ info Renewing SSL certs close to expiry... > [8/25/2023] [1:12:48 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized > [8/25/2023] [1:12:48 PM] [Global] › ℹ info Backend PID 277 listening on port 3000 ... > [8/25/2023] [1:12:49 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:12:50 PM] [SSL] › ℹ info Renew Complete > [8/25/2023] [1:13:09 PM] [Nginx] › ⬤ debug Deleting file: /data/nginx/proxy\_host/1.conf > [8/25/2023] [1:13:09 PM] [Nginx] › ⬤ debug Deleting file: /data/nginx/proxy\_host/1.conf.err > [8/25/2023] [1:13:09 PM] [Nginx] › ⬤ debug Could not delete file: { > "errno": -2, > "syscall": "unlink", > "code": "ENOENT", > "path": "/data/nginx/proxy\_host/1.conf.err" > } > [8/25/2023] [1:13:09 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:13:09 PM] [SSL] › ℹ info Requesting Let'sEncrypt certificates via Cloudflare for Cert #21: [hocishome.duckdns.org](http://hocishome.duckdns.org) > [8/25/2023] [1:13:09 PM] [SSL] › ℹ info Command: mkdir -p /etc/letsencrypt/credentials 2\> /dev/null; echo '# Cloudflare API token > dns\_cloudflare\_api\_token = g7DvNms0R54ygj05Xrs1xcPFsMSTy\_BwLzFdiTIb' \> '/etc/letsencrypt/credentials/credentials-21' && chmod 600 '/etc/letsencrypt/credentials/credentials-21' && . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-cloudflare==$(certbot --version | grep -Eo '0-9+') cloudflare && deactivate && certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-21" --agree-tos --email "[admin@hocishome.duckdns.org](mailto:admin@hocishome.duckdns.org)" --domains "[hocishome.duckdns.org](http://hocishome.duckdns.org)" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-21" > [8/25/2023] [1:13:17 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:13:17 PM] [Express] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-21" --agree-tos --email "[admin@hocishome.duckdns.org](mailto:admin@hocishome.duckdns.org)" --domains "[hocishome.duckdns.org](http://hocishome.duckdns.org)" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-21" > Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) : debian raspberry pi 4B Mon hébergeur, le cas échéant, est : duckdns Je peux me connecter à un shell root sur ma machine (oui ou non, ou je ne sais pas) : yes J’utilise un panneau de configuration pour gérer mon site (non, ou fournit le nom et la version du panneau de configuration) : nginx proxy manager front works fine ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/2/c/2ceedf0cc4236465388b1c3dd41a068fcc2c67f7.png) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 25, 2023, 1:26pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/2 "2023-08-25T13:26:02Z")
It seems your Nginx Proxy Manager (NPM) is trying to do the `dns-01` challenge (and thus not the `http-01` challenge you're testing using Let's Debug) using the Cloudflare DNS plugin while your DNS provider is DuckDNS. That doesn't make much sense. That said: I don't have any experience with NPM and I do not want to have any experience with that software (I don't like it at all), so I cannot help you with changing the findings I mentioned above. ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 1:28pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/3 "2023-08-25T13:28:22Z")
Ok, j'ai désactivé l'option DNS challenge pour ne pas faire un non-sens entre DNS et HTTP de mes requêtes, mais fonctionne toujours pas ^^. ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/2/e/2e592d1ef60b74227b732591d0b04ebfa89ab0d9.png) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 25, 2023, 1:29pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/4 "2023-08-25T13:29:45Z")
> [@Hocis](#): > > mais fonctionne toujours pas If you disabled the DNS challenge, you should have gotten a different error message. Please provide that new error message, as my crystal ball unfortunately is broken and still needs to be repaired. ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 1:32pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/5 "2023-08-25T13:32:15Z")
> [@Osiris](#): > > If you disabled the DNS challenge, you should have gotten a different error message. Please provide that error message, as my crystal ball unfortunately is broken and still needs to be repaired. This happened 🙂 > Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-23" --agree-tos --authenticator webroot --email "[admin@hocishome.duckdns.org](mailto:admin@hocishome.duckdns.org)" --preferred-challenges "dns,http" --domains "[hocishome.duckdns.org](http://hocishome.duckdns.org)" > Saving debug log to /tmp/letsencrypt-log/letsencrypt.log > Some challenges have failed. > Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details. > > ``` > at ChildProcess.exithandler (node:child_process:402:12) > at ChildProcess.emit (node:events:513:28) > at maybeClose (node:internal/child_process:1100:16) > at Socket. (node:internal/child_process:458:11) > at Socket.emit (node:events:513:28) > at Pipe. (node:net:301:12) > > ``` ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/0/a/0ab716d73798b04edd1b156490281f7349507af8.png) in portainer log of [nginxproxymanager\_app\_1] : > Starting backend ... > [8/25/2023] [1:30:39 PM] [Global] › ℹ info Using MySQL configuration > [8/25/2023] [1:30:42 PM] [Migrate] › ℹ info Current database version: 20211108145214 > [8/25/2023] [1:30:42 PM] [Setup] › ℹ info Logrotate Timer initialized > [8/25/2023] [1:30:42 PM] [Setup] › ℹ info Logrotate completed. > [8/25/2023] [1:30:42 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... > [8/25/2023] [1:30:42 PM] [IP Ranges] › ℹ info Fetching [https://ip-ranges.amazonaws.com/ip-ranges.json](https://ip-ranges.amazonaws.com/ip-ranges.json) > [8/25/2023] [1:30:42 PM] [IP Ranges] › ℹ info Fetching [https://www.cloudflare.com/ips-v4](https://www.cloudflare.com/ips-v4) > [8/25/2023] [1:30:42 PM] [IP Ranges] › ℹ info Fetching [https://www.cloudflare.com/ips-v6](https://www.cloudflare.com/ips-v6) > [8/25/2023] [1:30:42 PM] [SSL] › ℹ info Let's Encrypt Renewal Timer initialized > [8/25/2023] [1:30:42 PM] [SSL] › ℹ info Renewing SSL certs close to expiry... > [8/25/2023] [1:30:42 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized > [8/25/2023] [1:30:42 PM] [Global] › ℹ info Backend PID 200 listening on port 3000 ... > [8/25/2023] [1:30:43 PM] [Nginx] › ⬤ debug Deleting file: /data/nginx/proxy\_host/1.conf > [8/25/2023] [1:30:43 PM] [Nginx] › ⬤ debug Deleting file: /data/nginx/proxy\_host/1.conf.err > [8/25/2023] [1:30:43 PM] [Nginx] › ⬤ debug Could not delete file: { > "errno": -2, > "syscall": "unlink", > "code": "ENOENT", > "path": "/data/nginx/proxy\_host/1.conf.err" > } > [8/25/2023] [1:30:43 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:30:44 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:30:44 PM] [SSL] › ℹ info Renew Complete > [8/25/2023] [1:30:44 PM] [SSL] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-23/fullchain.pem -subject -noout > Can't open /etc/letsencrypt/live/npm-23/fullchain.pem for reading, No such file or directory > 547769563008:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss\_file.c:69:fopen('/etc/letsencrypt/live/npm-23/fullchain.pem','r') > 547769563008:error:2006D080:BIO routines:BIO\_new\_file:no such file:../crypto/bio/bss\_file.c:76: > unable to load certificate > ) > [8/25/2023] [1:30:48 PM] [SSL] › ℹ info Requesting Let'sEncrypt certificates for Cert #23: [hocishome.duckdns.org](http://hocishome.duckdns.org) > [8/25/2023] [1:30:48 PM] [SSL] › ℹ info Command: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-23" --agree-tos --authenticator webroot --email "[admin@hocishome.duckdns.org](mailto:admin@hocishome.duckdns.org)" --preferred-challenges "dns,http" --domains "[hocishome.duckdns.org](http://hocishome.duckdns.org)" > [8/25/2023] [1:31:11 PM] [Nginx] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt\_23.conf > [8/25/2023] [1:31:12 PM] [Nginx] › ℹ info Reloading Nginx > [8/25/2023] [1:31:12 PM] [Express] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-23" --agree-tos --authenticator webroot --email "[admin@hocishome.duckdns.org](mailto:admin@hocishome.duckdns.org)" --preferred-challenges "dns,http" --domains "[hocishome.duckdns.org](http://hocishome.duckdns.org)" > Saving debug log to /tmp/letsencrypt-log/letsencrypt.log > Some challenges have failed. > Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 25, 2023, 2:28pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/6 "2023-08-25T14:28:43Z")
I have no clue what Certbot returned as error message, as for some reason NPM decided it would be a good idea to NOT inform the user what went wrong. (You might find more info in the Certbot log file.) That said, it seems your website is not available on HTTP port 80, not using IPv4 nor using IPv6, which is a requirement for the `http-01` challenge. ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 3:04pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/7 "2023-08-25T15:04:25Z")
Je ne sais pas trop comment faire pour m'en assurer ... J'ai mis dans le docker duckdns mon token duckdns associé, après je ne sais pas comment lier les deux. Je ne sais meme pas où est le certbot log file ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 25, 2023, 3:05pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/8 "2023-08-25T15:05:49Z")
> [@Hocis](#): > > Je ne sais pas trop comment faire pour m'en assurer ... J'ai mis dans le docker duckdns mon token duckdns associé, après je ne sais pas comment lier les deux. The DuckDNS token is only required for the `dns-01` challenge, not for the `http-01` challenge. For the `http-01` challenge you "only" need a working website using HTTP. > [@Hocis](#): > > Je ne sais meme pas où est le certbot log file The location of the log is mentioned in the NPM output. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 25, 2023, 3:05pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/9 "2023-08-25T15:05:53Z")
> [@Hocis](#): > > Je ne sais meme pas où est le certbot log file > [@Hocis](#): > > Saving debug log to /tmp/letsencrypt-log/letsencrypt.log You may need to visit an NPM forum for help setting this up ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 3:10pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/10 "2023-08-25T15:10:58Z")
Don't have any folder letsencrypt-log in tpm. Letsencrypt is in opt folder but no letsencrypt-log folder in. ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/8/f/8f203bdaeb2043661bcc561365f84f0eb35cbaab.jpeg) ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 3:11pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/11 "2023-08-25T15:11:33Z")
![image](https://global.discourse-cdn.com/letsencrypt/original/3X/2/c/2c68bf4e23107e79cc2cd752417022c2c075b1be.png) ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 25, 2023, 3:28pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/12 "2023-08-25T15:28:06Z")
The log is probably in one of the systemd private folders. That's something that NPM is configuring ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 4:32pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/13 "2023-08-25T16:32:56Z")
in all 3 systemprivate there is only a tmp folder where there is nothing ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/e/5/e5f0b633ece304dead43b466cb2b7dbd4eda2f89.jpeg) I am not able to fix my problem 😕 I can go to HA with : ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/5/4/54e7efd1a226495f842f879d5442bfce1b4e1628.png) So a link has been set, but not able to generate SSL to have it outside with https... I only have log ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 25, 2023, 4:40pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/14 "2023-08-25T16:40:28Z")
> [@Hocis](#): > > I am not able to fix my problem 😕 Your website isn't reachable from my location _at all_. That's an issue separate from getting a certificate if you actually would like visitors from the public internet. And also a requirement for getting a cert using the `http-01` challenge. If you don't want your website accessible from the public internet, you can't use the `http-01` challenge and you should continu your efforts with NPM to make it actually use the DuckDNS DNS plugin. How? I don't know. ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 4:41pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/15 "2023-08-25T16:41:46Z")
I'd like to access to the site outside with [https://domain.duckdns.org](https://domain.duckdns.org) ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 25, 2023, 4:42pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/16 "2023-08-25T16:42:15Z")
> [@Hocis](#): > > I can go to HA with : > > ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/5/4/54e7efd1a226495f842f879d5442bfce1b4e1628.png) The HTTP Challenge requires something listening on port 80. You can redirect that once it arrives to a different port. But, it starts there and your server is not available on that port. ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 4:43pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/17 "2023-08-25T16:43:09Z")
> [@MikeMcQ](#): > > The HTTP Challenge requires something listening on port 80. You can redirect that once it arrives to a different port. But, it starts there and your server is not available on that port. How I do it ? ^^' the port is listening by nginx in docker : ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/6/c/6cdfc90d9758a59ceda601600569280c86b6f168.png) ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 4:52pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/18 "2023-08-25T16:52:10Z")
![Capture d’écran 2023-08-25 à 18.51.12](https://global.discourse-cdn.com/letsencrypt/original/3X/f/0/f01dcc65df7b8f6b315b95ce908ea3d7beef305a.png) I have this on my box internet ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [August 25, 2023, 5:02pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/19 "2023-08-25T17:02:43Z")
> [@MikeMcQ](#): > > You can redirect that once it arrives to a different port. 80 or 443 only, if it's for http-01. (it follows redirects to other fqdns) > [@Hocis](#): > > I have this on my box internet You need to enable that funcion for port (externe) 80 and 443, each to the appropriate internal port (this depends on how you configured your nginx proxy manager -- you should look at its docker-compose.yml). ---
**Author:** ![Hocis](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@Hocis](https://community.letsencrypt.org/u/Hocis)\ **Post date:** [August 25, 2023, 5:09pm UTC](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078/20 "2023-08-25T17:09:42Z")
here my docker compose ![Capture d’écran 2023-08-25 à 19.09.22](https://global.discourse-cdn.com/letsencrypt/original/3X/5/5/550eb38d2fc6de4efb09d4aeae14d32ef58408bd.jpeg) [Next page](https://community.letsencrypt.org/t/nginx-proxy-manager-ssl/204078.md?page=2)