Nalin 10 Posted November 20, 2016 Mozilla, Google, and Apple are all blocking WoSign/StartCom SSL certificates. In January, Firefox 51 and Google Chrome 56 will release and, since the Project Argo site forces itself to use HTTPS, nobody will be able to access it anymore. For people on the beta channels for the browsers, this change is already in place: I am unable to go to the Project Argo website on Firefox Beta. You may want to consider switching your certificate to one that isn't blocked. https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-startcom-certificates/ https://security.googleblog.com/2016/10/distrusting-wosign-and-startcom.html https://support.apple.com/en-us/HT204132 Share this post Link to post Share on other sites
Brady_The_1 31 Posted January 28, 2017 I am curious if anything is happening on this front. Using Firefox Beta I haven't had access to https://www.projectargo.net/ for the longest time now, but four days ago Firefox 51 was released (not to mention all the other browsers following suit), which is going to increase the number of affected people tremendously. Share this post Link to post Share on other sites
Nalin 10 Posted January 31, 2017 On 1/28/2017 at 5:15 AM, Brady_The said: I am curious if anything is happening on this front. Using Firefox Beta I haven't had access to https://www.projectargo.net/ for the longest time now, but four days ago Firefox 51 was released (not to mention all the other browsers following suit), which is going to increase the number of affected people tremendously. Not only that, but Chrome 56 has now been released. I would say a significant amount of people are now affected. Chrome will let you bypass the warning by clicking the text that says "Advanced", and then clicking to "Proceed to www.projectargo.net (unsafe)" But it gives a big old "Not secure" warning right on the URL bar. Firefox is worse as it won't even let you visit the website. Share this post Link to post Share on other sites
Brady_The_1 31 Posted February 8, 2017 Thanks for fixing the problem. I appreciate it. :-) 1 Share this post Link to post Share on other sites