# Renew HTTPS certificate without web GUI

**URL:** <https://discuss.rapid7.com/t/renew-https-certificate-without-web-gui/57099>\
**Category:** InsightVM\
**Tags:** InsightVM\
**Created:** [March 6, 2026, 11:04am UTC](https://discuss.rapid7.com/t/renew-https-certificate-without-web-gui/57099 "2026-03-06T11:04:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddrewe004](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@ddrewe004](https://discuss.rapid7.com/u/ddrewe004)\
**Post date:** [March 6, 2026, 11:04am UTC](https://discuss.rapid7.com/t/renew-https-certificate-without-web-gui/57099/1 "2026-03-06T11:04:16Z")

</div>

Hiya,

With the upcoming reduction in HTTPS certificate lifespans, we are trying to automate certificate renewal wherever we can, including the InsightVM Security Console. The docs currently only describes [how to renew the certificate with the web GUI](https://docs.rapid7.com/insightvm/managing-the-security-console/). Does anyone know a way how to renew the certificate without the web GUI, with something like an API call for example?

---

<div class="post-metadata">

**Author:** ![C.W](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/c/bbe5ce/32.png) [@C.W](https://discuss.rapid7.com/u/C.W)\
**Post date:** [March 9, 2026, 1:25pm UTC](https://discuss.rapid7.com/t/renew-https-certificate-without-web-gui/57099/2 "2026-03-09T13:25:58Z")

</div>

We were also looking into doing this last year, and my previous TAM told us “there is no built-in way to automate the certificate rotation as that step needs to be performed on the console itself.” Hopefully Rapid7 will change this in the future

---

<div class="post-metadata">

**Author:** ![ddrewe004](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@ddrewe004](https://discuss.rapid7.com/u/ddrewe004)\
**Post date:** [March 9, 2026, 3:10pm UTC](https://discuss.rapid7.com/t/renew-https-certificate-without-web-gui/57099/3 "2026-03-09T15:10:49Z")

</div>

Well, that’s unfortunate. Thank you!
