# Critical Error After Site Name Change **URL:** \ **Category:** Application Support\ **Created:** [February 24, 2023, 5:42am UTC](https://community.kinsta.com/t/critical-error-after-site-name-change/2084 "2023-02-24T05:42:07Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Agus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/agus/32/1515_2.png) [@Agus](https://community.kinsta.com/u/Agus)\ **Post date:** [February 27, 2023, 7:20am UTC](https://community.kinsta.com/t/critical-error-after-site-name-change/2084/8 "2023-02-27T07:20:58Z")
You’re most welcome! That’s great to hear the above method worked fine for you Sarah! 👏 So most likely previously any of your plugin(s) might not fully compatible to run on PHP 8.0 (and had to switch to PHP 7.4 first, and you could then work on it/re-registered/updated plugin(s), and was then able to switch back to PHP 8.0). About the insecure warning, since you mentioned `Mac OSX Monterey` , I remember about similar issue with the SSL cert on Mac OS (on `Ventura` though) - and am wondering if this [solution here](https://community.kinsta.com/t/issue-with-ssl-net-err-cert-authority-invalid/2075/2) may also work to solve the case you’re experiencing perhaps. Cheers, Agus --- _[View the full topic](https://community.kinsta.com/t/critical-error-after-site-name-change/2084)._