Nginx Proxy Manager Wildcard SSL Cert

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:teamgroth.me

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:GlassDoor

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

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):

I am trying to setup a wildcard cert for my nginx proxy manager. Everytime I type in my domain which is teamgroth.me, and I hit tab, the interface will change it to teamgroth.com and when it goes out to validate the API key it fails, because it is looking for the wrong domain. Is there a way that I can make it recognize that I have a .me domain instead of a .com?

That is definitely a question for the NPM support team.

5 Likes

Thanks for replying @MikeMcQ. I did figure out what I was doing wrong. I finally got a cert for my NPM, but it is showing up inactive for some reason. I thought that I might have made the API token incorrect, so I deleted it three times with three different tokens with the same result. I don't understand how I can have an SSL cert, but it not be active.

Imgur

That is another great question for the NPM support group :slight_smile:

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.