# Widgets cert expired again

**URL:** <https://forum.spinitron.com/t/widgets-cert-expired-again/942>\
**Category:** 🐞 Bug-report\
**Tags:** service-status\
**Created:** [April 26, 2023, 12:48pm UTC](https://forum.spinitron.com/t/widgets-cert-expired-again/942 "2023-04-26T12:48:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ray\_Charbonneau](https://forum.spinitron.com/user_avatar/forum.spinitron.com/ray_charbonneau/32/110_2.png) [@Ray\_Charbonneau](https://forum.spinitron.com/u/Ray_Charbonneau)\
**Post date:** [April 26, 2023, 12:48pm UTC](https://forum.spinitron.com/t/widgets-cert-expired-again/942/1 "2023-04-26T12:48:08Z")

</div>

Widgets were inaccessible via “[widgets.spintron.com](http://widgets.spintron.com/)”, as you’ve let the certificate expire again.

---

<div class="post-metadata">

**Author:** ![tom](https://forum.spinitron.com/user_avatar/forum.spinitron.com/tom/32/343_2.png) [@tom](https://forum.spinitron.com/u/tom)\
**Post date:** [April 26, 2023, 1:11pm UTC](https://forum.spinitron.com/t/widgets-cert-expired-again/942/2 "2023-04-26T13:11:59Z")

</div>

Sorry about that.

The thing that seems to be missing from the automation is restarting the nginx servers across the cluster after the cert is renewed.

/me the worlds worst sysop

---

<div class="post-metadata">

**Author:** ![Ray\_Charbonneau](https://forum.spinitron.com/user_avatar/forum.spinitron.com/ray_charbonneau/32/110_2.png) [@Ray\_Charbonneau](https://forum.spinitron.com/u/Ray_Charbonneau)\
**Post date:** [April 26, 2023, 1:34pm UTC](https://forum.spinitron.com/t/widgets-cert-expired-again/942/3 "2023-04-26T13:34:04Z")

</div>

I’ve replaced the “[widget.spintron.com](http://widget.spintron.com)” URLs. As long as the alternative “[spintron.com](http://spintron.com)” URLs keep working, we’re all set.

---

<div class="post-metadata">

**Author:** ![tom](https://forum.spinitron.com/user_avatar/forum.spinitron.com/tom/32/343_2.png) [@tom](https://forum.spinitron.com/u/tom)\
**Post date:** [April 26, 2023, 2:38pm UTC](https://forum.spinitron.com/t/widgets-cert-expired-again/942/4 "2023-04-26T14:38:23Z")

</div>

that’s a good idea.

the reason we have `widgets.` at all is to provide both HTTP and HTTPS service for public URLs. when we introduced the widgets, some stations were not using HTTPS and browsers were throwing security errors with mixed content, so we had to make them work with whatever protocol the station’s server used. if you’re only on HTTPS then there’s no need to use the `widgets.` vhost.
