# Run commands after SSL cert renewal

**URL:** <https://forum.virtualmin.com/t/run-commands-after-ssl-cert-renewal/131430>\
**Category:** Virtualmin\
**Created:** [January 5, 2025, 2:36pm UTC](https://forum.virtualmin.com/t/run-commands-after-ssl-cert-renewal/131430 "2025-01-05T14:36:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [January 5, 2025, 6:57pm UTC](https://forum.virtualmin.com/t/run-commands-after-ssl-cert-renewal/131430/4 "2025-01-05T18:57:46Z")

</div>

I answered that question in that thread, too. [Custom actions with Virtualmin's Letsencypt renewals? - #4 by Joe](https://forum.virtualmin.com/t/custom-actions-with-virtualmins-letsencypt-renewals/131248/4)

It doesn’t matter where you put it, as long as Virtualmin has the full path to find it in the command to run field.

I usually put this kind of thing in `/usr/local/bin` or `/usr/local/sbin`, but it doesn’t matter as long as you tell Virtualmin where to find it.

---

_[View the full topic](https://forum.virtualmin.com/t/run-commands-after-ssl-cert-renewal/131430)._
