starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #624] api domain certificate x509 error! #400

New issue

Closed

opened 2026-03-02 02:16:04 +03:00 by kerem · 7 comments

kerem commented

2026-03-02 02:16:04 +03:00

Owner

Originally created by @magicshow1 on GitHub (Jul 7, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/624

Server Info (please complete the following information):

OS: [Ubuntu 20.04]
Browser: [chrome]
RMM Version (as shown in top left of web UI):

Installation Method:

[ x] Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI):
Agent OS: [e.g. Win 10 v2004, Server 2012 R2]

Describe the bug
A clear and concise description of what the bug is.

Originally created by @magicshow1 on GitHub (Jul 7, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/624 **Server Info (please complete the following information):** - OS: [Ubuntu 20.04] - Browser: [chrome] - RMM Version (as shown in top left of web UI): **Installation Method:** - [ x] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): - Agent OS: [e.g. Win 10 v2004, Server 2012 R2] **Describe the bug** A clear and concise description of what the bug is. ![Capture](https://user-images.githubusercontent.com/76628802/124721424-f70de400-debd-11eb-9edb-a351c6d17122.JPG)

kerem closed this issue

2026-03-02 02:16:05 +03:00

kerem commented

2026-03-02 02:16:05 +03:00

Author

Owner

@magicshow1 commented on GitHub (Jul 7, 2021):

/rmm/api/tacticalrmm/tacticalrmm/local_settings.py

CERT_FILE = "/path/to/your/fullchain.pem"
KEY_FILE = "/path/to/your/privkey.pem"

It still fails after configuration and restart...

@magicshow1 commented on GitHub (Jul 7, 2021): /rmm/api/tacticalrmm/tacticalrmm/local_settings.py CERT_FILE = "/path/to/your/fullchain.pem" KEY_FILE = "/path/to/your/privkey.pem" It still fails after configuration and restart...

kerem commented

2026-03-02 02:16:05 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jul 7, 2021):

where did you purchase the cert from and is it wildcard?

@wh1te909 commented on GitHub (Jul 7, 2021): where did you purchase the cert from and is it wildcard?

kerem commented

2026-03-02 02:16:05 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jul 7, 2021):

paste nginx configs also

@wh1te909 commented on GitHub (Jul 7, 2021): paste nginx configs also

kerem commented

2026-03-02 02:16:06 +03:00

Author

Owner

@magicshow1 commented on GitHub (Jul 7, 2021):

nats wildcard, all are default

@magicshow1 commented on GitHub (Jul 7, 2021): nats wildcard, all are default

kerem commented

2026-03-02 02:16:06 +03:00

Author

Owner

@magicshow1 commented on GitHub (Jul 7, 2021):

how can I solve this problem....

@magicshow1 commented on GitHub (Jul 7, 2021): how can I solve this problem....

kerem commented

2026-03-02 02:16:06 +03:00

Author

Owner

@silversword411 commented on GitHub (Jul 7, 2021):

Your screenshot shows that the DNS names aren't matching (1st doesn't match 2nd), am I missing something?

If the dns names actually match, is the cert chain unbroken when you view it?

@silversword411 commented on GitHub (Jul 7, 2021): Your screenshot shows that the DNS names aren't matching (1st doesn't match 2nd), am I missing something? If the dns names actually match, is the cert chain unbroken when you view it?

kerem commented

2026-03-02 02:16:06 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jul 7, 2021):

nats wildcard, all are default

nats doesn't sell SSL certs lol. if you are using self signed cert then that definitely is not supported and will fail.

and if you are using a purchased ssl cert (not self signed) you'll need to update the nginx configs as well to point to the certs. the default nginx config generated by the install script uses the letsencrypt path. as @silversword411 said, read the error message it should give you a hint.

anyway at this time we don't really support using custom certs. you're welcome to do so if you know what you're doing but there is no official support until we get docs up for it so i'm closing this

@wh1te909 commented on GitHub (Jul 7, 2021): > nats wildcard, all are default nats doesn't sell SSL certs lol. if you are using self signed cert then that definitely is not supported and will fail. and if you are using a purchased ssl cert (not self signed) you'll need to update the nginx configs as well to point to the certs. the default nginx config generated by the install script uses the letsencrypt path. as @silversword411 said, read the error message it should give you a hint. anyway at this time we don't really support using custom certs. you're welcome to do so if you know what you're doing but there is no official support until we get docs up for it so i'm closing this

kerem referenced this issue

2026-03-14 02:56:06 +03:00

[GH-ISSUE #400] Feature request: Rights management by groups (users or customers) #2188