that was my thoughts as well, but thought I would leave it to experts, of which I aint one
Me neither. I copy and pasted it...
But reading the english, it looks as though the certificate is one used by Parallels Panel - if you google it, its a webhosting company, probably what this is hosted by. Self-signed implies that you can validate it yourself without it being on some kind of registered and approved database. The english of the code in the error looks as though it goes off to check the certificate against a database and it's throwing up an error because it can't find it on there.
Sounds like just the small details of web hosting to me, just a little tidying to do if Nick feels it's necessary.
Except that I've never heard of Parallels Panel, and they are certainly not the site's hosts, unless they're part of a sister company or something.
Well, if that's the case it will most certainly be sorted out. Anyway, thanks for alerting us to this :)Quote:
Sounds like just the small details of web hosting to me, just a little tidying to do if Nick feels it's necessary.
Marco.
Thanks for raising this - to be honest the forum was never configured for HTTPS access, and we've never tested it. Parallels Plesk is a system that runs on the server and allows people like me to configure various backend bits without having to worry about getting too handy with code etc. It handles certificate storage for secure sites running Plesk.
The certificate (self signed) needs to be regenerated at some point for my own benefit but it shouldn't affect the site itself - I need to make sure that the server isn't configured to announce itself as an allowing HTTPS so that 'HTTPS Anywhere' and the like doesn't try and establish a secure connection.
Not sure how long that'll take so bear with me...
Nice one, Nick. Thanks for looking into this. I look forward to seeing what the outcome is :)
Marco.
I have disabled SSL / HTTPS. Connections to The Art of Sound should always be via http://theartofsound.net - it would be useful if the original poster could confirm that their connections no longer default to trying for a secure connection. Attempting to connect directly to https://theartofsound.net will no longer be accepted. I'll have a look this evening and see if I can set up a redirect to send https:// connections back to our usual http:// site, for neatness's sake.
That would be interesting if I knew what it meant, or how it impacts upon/changes what Sam was getting at in his opening post... ;)
Marco.
Comes up refused to connect Nick as it should.