Hi everyone,
I'm happy to announce that the https issue for the docs is now resolved. The issue was slightly more complex and less complex than I thought. The issue affected "https://skunity.com" and "https://www.skunity.com", but no other sub-domains were affected (forums.skunity.com is hosted on a different server, but still unaffected at domain level). The issue was also only present in Google Chrome. Other browsers and SSL/HTTP(S) checking sites worked fine.
Originally I thought it was due to CloudFlares SSL certificate issued to the domain and as Chrome is very fussy with HTTPS, it just refused connection with a generic reason. After investigation with @xXAndrew28Xx, we tried restarting Apache, going through every configuration file and running commands to fix the issue, nothing worked. We then figured out that specifying the pages worked (testing page that still exists https://skunity.com/hiandrew), but any page that was the docs didn't. The way the docs are built means that different pages call upon some of the same files, regardless of the actual page. I did some digging (basically just commented and uncommented lines until stuff worked), and found that a header was being sent by PHP and was either conflicting with a meta tag or confusing the browser because it was sent before any HTML but was a HTML related header. The line was removed and the docs load fine.
There is a warning for unsecure content, which I plan to fix, but don't have the time to roll out right now. Docs 2 will be released soon and don't have any unsecure content notices. Just ignore it for now, your browsing experience shouldn't be affected.
