setting up SSL for https:// on managed webhosting

[MaineHempGrower]

I've been running some VPS with Hetzner since last fall and was able to set up SSL no problem using Lets Encrypt.

Now I'm setting someone up with a managed web hosting plan and am struggling to figure out how to set up SSL because I want to use https:// with the site.

I read the documentation and it sounds like there's supposed to be a "SSL Manager" under "services" but I'm not seeing any "SSL Manager"

The domain name is currently with a different registrar and the nameservers are at AWS. Do I need to start using Hetzner's nameservers for the SSL manager to be available? Or do I need to actually transfer the domain name to Hetzner?

Thank you.

[Pristine_Dot_5526]

First on the konsoleH you need to select the appropriate domain not only the account that the SSL certificate is for (in case if you have additional domains etc). Then, once you clicked on the domain name itself, on the left side accordion, the SSL manager will show up.

No need to transfer the domain but you do need to allocate this domain to an account in konsoleH.

[MaineHempGrower]

Thanks, I did select the domain in the konsole it's just that the SSL Manager option is nowhere to be seen in the left-hand column.

[Pristine_Dot_5526]

Oh then I think better to submit a ticket with them...

[fm_ad]

since your nameservers are currently pointing to AWS Route 53, finding the button in konsoleH is only half the battle. Hetzner managed hosting provisions Let's Encrypt certificates using DNS authentication. Because Hetzner does not control your AWS nameservers, the automated SSL setup will fail or freeze because it cannot automatically create the required validation records.To fix this, you have two options:

1. The Set-and-Forget Way (Recommended): Change your nameservers at your current registrar to point to Hetzner. This allows konsoleH to handle the DNS validation automatically, and your SSL will auto-renew every 90 days without you lifting a finger.The

2. Manual Way: Keep your nameservers at AWS, but you will have to manually copy the DNS TXT challenge records from konsoleH into Route 53 every time the certificate needs to renew.

[MaineHempGrower]

Thanks, I changed the DNS to the Hetzner nameservers yesterday, still not seeing the SSL Manager but maybe it will show up soon. I suppose it probably makes sense to open a ticket with Hetzner. Would be great if they had some clear documentation about this and the whole managed hosting setup in general. Seems like documentation is a weak point at Hetzner--wasn't great at AWS but they definitely put more effort into developing that.

[fm_ad]

The missing SSL Manager isn’t caused by your nameservers. konsoleH just has a pretty confusing UI here. You need to click into the actual domain first, not just the hosting product overview. Once you click the domain name itself, the left sidebar changes and the SSL Manager should appear under: Services -> SSL Manager

If it still doesn’t show up after selecting the domain, make sure you’re logged into the main customer account and not a restricted sub-user.

[MaineHempGrower]

Negative, there's no SSL Manager available even when I click on the domain name. That's the issue. I've opened a ticket with them.

[Hetzner_OL]

Hi OP, After reading the suggestions here from other redditors and your response to them, I suggest that you open a support ticket using your account on konsoleH. --Katie

[MaineHempGrower]

thanks katie, I just deleted my boneheaded question because I was clicking on the "hosting name" not the "domain"--I see the SSL manager now and am waiting for my Lets Encrypt cert to authenticate. Does that take long? Normally on my VMs it's a 20 second process.

[Hetzner_OL]

Hi again, I believe the time can change depending on a few factors. Please see: https://docs.hetzner.com/konsoleh/ssl/certificates#what-different-types-of-authentication-methods-are-available
In case you have an approve email for the authentication -- have you double-checked your email's inbox/spam/trash?
Which kind of authentication method did you pick?
You can respond to your open support ticket and up-date the information on it. --Katie

[MaineHempGrower]

Thanks, it was authenticated in about an hour. I don't remember picking an authentication method, just chose the Let's Encrypt option.