HTTPS site access broken
Hi
There's a very high possibilty I broke my website access yesterday. I was fiddling with sub-domains and accidentally removed the link between my domain name and the website www.darkwolves.eu / darkwolves.guildlaunch.com .
I sent an email yesterday, but then today I've managed, I think, to get the link back up. However, it's now telling me that the site is unsecure - obviously I can get round it by telling the browser to go there anyway, but of course others won't do that.
I've selected the HTTPS option in the admin bit of my page (actually, deselected and reselected, as it was already showing .. and everything else seems fine there), but I'm wondering if, when the link broke, it didn't automatically re-establish? Or if I need to do something extra on my domain host page?
For info, this is the page I'm getting:
Your connection is not private
Attackers might be trying to steal your information from www.darkwolves.eu (for example, passwords, messages or credit cards). Learn more
Looking through the settings on our end, I think we're still good here. It's hard to assume what part of your settings need to be updated. Here's our instructions for settings on your domain host end.
Can you try to figure out the difference of your settings now to this article? We should be able to get it back on, it's just a matter of figuring out which setting is missing now.
You know how sometimes you really wish you'd taken a screenshot before you changed anything? /sigh
Okay I kinda struggled with this a little bit. I'd come across something earlier on GL saying about the A record .. which worked up to a point (at least it actually found our site again, but then came up with that security warning).
I've added the CNAME (I'm assuming it was actually to customdomain1.guildlaunch.com and not darkwolves.guildlaunch.com?) .. but that then removed the A record. Is that right?
Oh and I've broken your forum now .. just got the following error:
Failed to load plugin: anchor from url https://www.gameskinny.com/js/tinymce/0406xx/plugins/anchor/plugin.min.js
Adding the CNAME should have been the trick.
The tinymce plugin error you got would have been a side effect of https not working properly and should have started working again once you got https sorted.
Looks like you're good to go though, I hope it wasn't too brain frying! Don't worry, I also struggle on this stuff more than I'd like to haha.