Ssl internal error in nginx proxy manager

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: kingsofvirginia.org with google domain. cloudflare handles dns.

I ran this command: request ssl certificate in nginx proxy manager. The proxy option is turned off for the domain in cloud flare

It produced this output: internal error when requesting new ssl certificate

My web server is (include version): running docker, container name is ngnix proxy manager.

The operating system my web server runs on is (include version): ubuntu 22.04

My hosting provider, if applicable, is: google domains

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

Welcome to the Let's Encrypt Community, Sidney! :slightly_smiling_face:

What I believe the error message is referencing is the "gray cloud" status of kingsofvirginia.org in your Cloudflare CDN configuration. Without being "orange cloud", you would need the nginx proxy manager to serve a publicly trusted certificate.

https://community.cloudflare.com/t/how-to-turn-off-cdn/20763

Update: That said, I believe that @MikeMcQ is onto something below. I surmise that nginx proxy manager "thinks" that you're using Cloudflare in "gray mode" for kingsofvirginia.org because you are using Cloudflare as your DNS provider but the response from your website is coming from nginx proxy manager and not the Cloudflare CDN. This is just an educated guess. If correct, it is IMO a bug in nginx proxy manager.

3

Welcome to this community @kingsofvirginia

I don't see that there is anything specific to Let's Encrypt in that error. I think you are better off asking about that on the nginx proxy manager github.