i used to be able to access https://my_guild_site_here.guildlaunch.com/ and it would just work, now it's redirecting me to the front page and i have to use plain http instead of https.
Same thing happens with https://community.guildlaunch.com, it redirects ALL SSL access to the front page and it also affects the user profile page, i'm getting the above "File not found" errors when i try to access my user profile via HTTPS because of the redirect.
From the page http://www.guildlaunch.com/about-us/security/
Secure Logins - SSL Logins - As of July 2010 all logins on Guild Launch sites, on the GuildLaunch.com domain, are submitted via Secure connections with a 2048bit key. This means the data can not be eavesdropped on in transit. Click the image below to view information on our Secure Server certificate.
This is not happening right now. All logins (even if I am visiting my site via HTTPS when I click the login link) are being done via HTTP and not via HTTPS. This happens when logging in from the link on my own guild page as well as using the Login link on www.guildlaunch.com. Please fix this asap.
Honestly I'm not sure. According to this post, logins are secure on sites that use the GL domain names, like yours.
I'm assuming the sites that have their own domain names are not (like mine).
For info this is the post I'm referring to:
Hi, Sorry for the delay. Unfortunately, we aren't able to offer HTTPS protection for custom domains at this time. We might in the future at an additional cost. All logins on Gamer Launch sites, on the GamerLaunch.com or other subdomains, are submitted via Secure connections with a 2048bit key.
This has had a knock on affect as far as switching between our website and the main support forums was concerned, and I was hoping some resolution would be forthcoming, but nothing has materialised.
Plus, of course, there is the security issue. But there's nothing much I can do about that.
I can actually access your site, which in theory should qualify for the GL security, using the https in the url .. but Firefox still tells me it is insecure *shrugs*. Perhaps literally it is only the log-in page that is secured?
Hopefully GL can shed some light ;-)