CertBot wildcard certificate

[kmccmk9]

Server Info (please complete the following information):

• OS: Ubuntu 20.04
• Browser: Firefox
• RMM Version: latest

Installation Method:

• Standard
• Docker

Agent Info (please complete the following information):

• Agent version: NA
• Agent OS: NA

Describe the bug
Following the documentation for creating certbot certificates, starting the services results in the following error messages.

[842] 2022/04/24 06:35:58.303859 [ERR] 172.16.0.3:49314 - cid:135 - TLS handshake error: remote error: tls: bad certificate
time="2022-04-24T06:38:06Z" level=fatal msg="x509: certificate is valid for *.example.com, not api..example.com". I've also tried this using the setup script in the non-docker instructions with the same result.

To Reproduce
Steps to reproduce the behavior:

1. Follow the installation instructions and generate certificates either through setup script or independently
2. Start the server and see the error.

Expected behavior
The server would turn on and allow connections.

Screenshots
NA

Additional context
NA

[dinger1986]

Can you share a screenshot?

I did 4 or 5 test installs last week and they worked fine every time generating new certs.

[kmccmk9]

I used certs from the setup.sh in the standalone server guide.

[wh1te909]

please paste the commands you're running to generate the certs and how you're putting them in the .env file, you're not doing something right

[kmccmk9]

I used certs from the setup.sh in the standalone server guide.

[ninjamonkey198206]

I run this via Docker with no issues, and have a walkthrough and example files if you need them. If you can hop on the discord and dm me, I can help you get this straightened out.

[BelleNottelling]

It looks like you added a period as a suffix to your domian name
Like this: .api.example.com
When you actually want is api.example.com

[kmccmk9]

I'm sorry where do you see that?

[BelleNottelling]

From your error message:
certificate is valid for *.example.com, not api..example.com"

That is however, assuming you didn't introduce the typo when replacing your domain with example.com

[kmccmk9]

I'm sorry that was indeed a typo when I wrote the issue.