HTTPS / SSL
I am a paying customer (NOT using a free plan) and followed the instructions to configure my custom domain. I also email Gamer Launch (per the instructions) two weeks ago to configure the SSL for the domain.
While the domain points correctly to GamerLaunch and to my site, the SSL configuration isn’t complete for the custom domain.
Since no one responded to the email request which is the stated process, how do I get the SSL properly configured for the custom domain?
Apologies for the delay Kalela. I have configured the SSL cert for your custom domain in our system now. It should start working for you shortly. It usually takes less than an hour for it to fully update everywhere. I am going to check in on it until I see it working!
Do you think the delay will take a few more hours or into tomorrow? I'm still getting an error.
Thanks for your support! :)
Just to double check, had you already found and followed these instructions?
https://guildlaunch.uservoice.com/knowledgebase/articles/1917004-how-to-request-and-set-up-ssl-certified-custom-dom
It's possible that the provisioning is getting hung up because it's not hooking up with your domain host properly.
Let me know if you have done this CNAME step. Sorry if this has been confusing for you, it's not the easiest thing we do haha.
Yes... I've done all of those steps. When I go to the custom domain, it navigates properly to my gamerlaunch domain. I get that it's not secure. The lock is showing and working for the GamerLaunch URL but not for my custom URL.
The forums keep giving me an error when trying to upload screenshots to show the difference. You can try the links to see if you are getting differences.
https://www.eq-aed.org/ - Says Not Secure though is pointing properly to https://aed.gamerlaunch.com/
There's one last thing for me to check on, but I will not have access to that tool until tomorrow. I'll let this cert continue to try to provision tonight and check in on this first thing in the morning when I have access to the tool I need. We will get this to work!
I see you came by the site this morning and we still have Not Secure on our Custom Domain.
How's it looking for getting it working?
Sorry about that, I abruptly got an invite to something.
What I wanted to check this morning did not yield what I was hoping.
The only thing left to do that I can think of is to double check your domain host settings.
Can you double check that you have CNAME set to Host: www and Points to customdomain1.guildlaunch.com
And then double check your Forwarding setting. It should have Forward To http:// and enter your URL www.eq-aed.org, make sure Forward Type is Permanent (301), Settings set to Forward Only and "Update my nameservers and DNS settings to support this change" is checked off.
The screenshots of what those settings look like in GoDaddy are in here
https://guildlaunch.uservoice.com/knowledgebase/articles/1917004-how-to-request-and-set-up-ssl-certified-custom-dom
These instructions are separate from the basic default settings you find linked too from the Site URLs admin page.
If you can confirm that those settings are in your domain host, I will try the next steps I can find to try. I apologize for the issues!
I've used a lookup tool and found that you definitely need to get the CNAME and forwarding steps from above fixed. Are you using GoDaddy or another host? GoDaddy is easiest because we have screenshots of the settings for it. If you're on another host, I can try to find instructions or anything to help you through those settings.
The steps had noted to use an IP address for the CNAME settings. You are now saying to point to the URL? I'm not using GoDaddy as they are a rip-off. I am a professional web designer and own numerous domains through another company that has all of my hosting for my businesses.
The link on the dashboard states to use an IP address. Here's the link I used per my dashboard.
I'm making some additional settings to see if that resolves the issue. As I stated in my previous post, the original instructions only noted the need to set the A record using the IP address. I've added the additional CNAME record to see how that resolves. I'm waiting for the processing to complete.
I know this process is confusing, we could do better. I need to update that page to show both instructions and explain why you do one or the other better. The link to instructions I gave above is the instructions you need to follow for getting the SSL cert working. The A record instructions you linked is the old instructions to get regular custom domains working without an SSL cert.
You can use a DNS lookup tool to test if the CNAME is configured. I've run a test again and it still shows that there is not a CNAME configured. You also need to make sure the forwarding settings are updated as well. I could try to help look up how to set this in your domain host if you'd like. Again, I'm sorry for the inconvenience of this, I want to make this system better.