Let's Encrypt not working

[DNAScanner]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • No
• 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 For a few days now I'm trying to get my let's encrypt SSL to work, but it doesn't, and I don't know why

Nginx Proxy Manager Version v2.9.15

To Reproduce Steps to reproduce the behavior:

1. Go to 'Dashboard'
2. Click 'Proxy Hosts'
3. Click 'Add Proxy Host' so it opens the menu
4. Fill in the form: Domain Names: 'dnascanner.dynv6.net' Scheme: http Forward Hostname/IP: raspberrypi Forward Port: 8080 Every switch off (cache assets, block common exploits, websockets support)
5. Go to the 'SSL'-Tab
6. Switch to 'Request a new SSL Certificate' and enable 'Force SSL', 'HSTS', 'HTTP/2 Support' and 'HSTS subdomains' and agree on the bottom
7. Click the 'OK' button and wait. After a few secs it should say 'Internal Error'

Expected behavior I expected, that I get the SSL on my webserver working

Screenshots https://cdn.discordapp.com/attachments/910203843625766922/941733175552524388/unknown.png

Operating System Running on RaspberryPi 4b 'raspberrypi os'

Additional context Docker Version: 20.10.12, build e91ed57 Browser Version: OperaGX LVL3 (core 83.0.4254.46) Let's Encrypt Report: https://cdn.discordapp.com/attachments/910203843625766922/941735452891832432/log.log

[blockiindahood]

Same here 👋🏼

[blockiindahood]

I just found out, if you create it over the "certificate" tab it works, but only if your website does not respond with a 500

[DNAScanner]

I just found out, if you create it over the "certificate" tab it works, but only if your website does not respond with a 500

For me it still doesn't work..

[Skizz83]

Same here too, exactly the same error message in the logs

[anthonyb800]

Same issue & same error here when trying to get a wildcard cert w/Cloudflare API.

[blockiindahood]

Now it is working fine for me, I installed it on Proxmox with the Third-Party script, without docker on an Alpine container. It only throws an exception when the website throws an 500 html code.

[DNAScanner]

Now it is working fine for me, I installed it on Proxmox with the Third-Party script, without docker on an Alpine container. It only throws an exception when the website throws an 500 html code.

How tf did u do that? Could u send me a link or some intructions or smt?

[blockiindahood]

https://github.com/ej52/proxmox-scripts/tree/main/lxc/nginx-proxy-manager linked under https://nginxproxymanager.com/third-party/ @DNAScanner

[anthonyb800]

Looks like it worked for me this morning. Not sure what changed, but I obtained the cert with no issues

[HerrFrutti]

same. reverting back to version 2.9.10 does it for me.

running on a pi 4 4gb ram Raspbian GNU/Linux 11 (bullseye)

[rrreid]

I was getting the same 'Internal Error' issue, but once I restarted npm, it loaded back up with the updated cert. All seems to be working as expected now.

[github-actions[bot]]

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

[github-actions[bot]]

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