The issue is that Firefox is caching security certificates rather than loading them fresh. This doesn't become an issue until the cached security certificate expires, then the user faces the "this website is not secure" warning page. The user tries to reload the page multiple times and continues to get the same warning page, then they call me in a panic and say "my website is not loading because it is not secure!" The solution is Ctrl+F5 and voila the website loads without issue. However, this is definitely an "issue" and the issue isn't with the website or the lack of knowledge of the end user. End users should not need to know how to refresh their local cache of a website to resolve a security certificate expiring when it has already been renewed. Firefox should by default check for a new security certificate when the cached version has expired or at least that is what would appear to be the logical progression of local caching. Unfortunately, I have been unable to find a way to report this issue to Firefox developers...so I am reporting it here in hopes that someone in the community has the ear of the development team and can point out this issue. Thanks, Dr. Pat