mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #624] api domain certificate x509 error! #2345
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2345
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
A clear and concise description of what the bug is.
@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...
@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):
paste nginx configs also
@magicshow1 commented on GitHub (Jul 7, 2021):
nats wildcard, all are default
@magicshow1 commented on GitHub (Jul 7, 2021):
how can I solve this problem....
@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?
@wh1te909 commented on GitHub (Jul 7, 2021):
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