[GH-ISSUE #1088] CertBot wildcard certificate #2611

New issue

Closed

opened 2026-03-14 04:49:49 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 04:49:49 +03:00

Owner

Originally created by @kmccmk9 on GitHub (Apr 24, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1088

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:

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

Expected behavior
The server would turn on and allow connections.

Screenshots
NA

Additional context
NA

Originally created by @kmccmk9 on GitHub (Apr 24, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1088 **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Firefox - RMM Version: latest **Installation Method:** - [ ] Standard - [X] 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. <domain swapped with example.com for privacy> [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

kerem closed this issue

2026-03-14 04:49:55 +03:00

kerem commented

2026-03-14 04:50:00 +03:00

Author

Owner

@dinger1986 commented on GitHub (Apr 24, 2022):

Can you share a screenshot?

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

@dinger1986 commented on GitHub (Apr 24, 2022): Can you share a screenshot? I did 4 or 5 test installs last week and they worked fine every time generating new certs.