November 26th, 2020 at 9:52 PM
Hello all,
We have enabled HTTPS/SSL security for the entire MS community. We ended up using Certbot (as suggested by Thomas and S3_gunzel) - which massively simplified the process compared to the failed attemps for us to do so before. Everything worked without a hitch.
The site should be much more secure on public networks and will no longer display the "not secure" message on Chrome. It is also faster (HTTP/2.0) than before. That being said, we had to change a number of CSS/JS/Image URLs througout the theme, so there might have been a couple we missed. If anything looks incorrect or you get a "mixed content" error, let us know in this thread and we will address it promptly!
Regards,
-Makestation
We have enabled HTTPS/SSL security for the entire MS community. We ended up using Certbot (as suggested by Thomas and S3_gunzel) - which massively simplified the process compared to the failed attemps for us to do so before. Everything worked without a hitch.
The site should be much more secure on public networks and will no longer display the "not secure" message on Chrome. It is also faster (HTTP/2.0) than before. That being said, we had to change a number of CSS/JS/Image URLs througout the theme, so there might have been a couple we missed. If anything looks incorrect or you get a "mixed content" error, let us know in this thread and we will address it promptly!
Regards,
-Makestation
