[GH-ISSUE #678] Easier way to renew cert ? #2376

New issue

Closed

opened 2026-03-14 03:45:29 +03:00 by kerem · 5 comments

kerem commented

2026-03-14 03:45:29 +03:00

Owner

Originally created by @vmasseron on GitHub (Aug 31, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/678

I'm always frustrated when I have to renew my certificate, it's time-consuming.

I've undertood that it is not easy to automate it, ok.

At the end of the renewing process, I got the message To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-onteractively renew *all* of your certificates, run "certbot renew"

This is my only certificate managed on this machine, will this work ?

Originally created by @vmasseron on GitHub (Aug 31, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/678 I'm always frustrated when I have to renew my certificate, it's time-consuming. I've undertood that it is not easy to automate it, ok. At the end of the renewing process, I got the message `To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-onteractively renew *all* of your certificates, run "certbot renew"` This is my only certificate managed on this machine, will this work ?

kerem closed this issue

2026-03-14 03:45:34 +03:00

kerem commented

2026-03-14 03:45:39 +03:00

Author

Owner

@dinger1986 commented on GitHub (Aug 31, 2021):

its not possible to automate renewing a wildcard cert and it needs TXT records added. It has been done using dns and 3 separate certificates but that is not supported.

If you require more assistance with this then please join the discord channel

@dinger1986 commented on GitHub (Aug 31, 2021): its not possible to automate renewing a wildcard cert and it needs TXT records added. It has been done using dns and 3 separate certificates but that is not supported. If you require more assistance with this then please join the discord channel

kerem commented

2026-03-14 03:45:44 +03:00

Author

Owner

@silversword411 commented on GitHub (Sep 1, 2021):

@dinger1986 Might be nice to add to the "Unsupported" docs a way to use purchased certs with TRMM. Do you know who may be doing this now?

@silversword411 commented on GitHub (Sep 1, 2021): @dinger1986 Might be nice to add to the "Unsupported" docs a way to use purchased certs with TRMM. Do you know who may be doing this now?

kerem commented

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

Author

Owner

@moose999 commented on GitHub (May 31, 2022):

If you are using CloudFlare for DNS you can automate the challenges https://www.bjornjohansen.com/wildcard-certificate-letsencrypt-cloudflare

@moose999 commented on GitHub (May 31, 2022): If you are using CloudFlare for DNS you can automate the challenges https://www.bjornjohansen.com/wildcard-certificate-letsencrypt-cloudflare

kerem commented

2026-03-14 03:45:55 +03:00

Author

Owner

@casaresjm commented on GitHub (Oct 4, 2022):

It would be nice to be able to use existing wildcard certificates we do not need to renew every 3 months with a really complex setup.

@casaresjm commented on GitHub (Oct 4, 2022): It would be nice to be able to use existing wildcard certificates we do not need to renew every 3 months with a really complex setup.

kerem commented

2026-03-14 03:46:00 +03:00

Author

Owner

@dinger1986 commented on GitHub (Oct 4, 2022):

its all on docs https://docs.tacticalrmm.com/functions/settings_override/#using-your-own-wildcard-ssl-cert and also how to use the http certbot

@dinger1986 commented on GitHub (Oct 4, 2022): its all on docs https://docs.tacticalrmm.com/functions/settings_override/#using-your-own-wildcard-ssl-cert and also how to use the http certbot