Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
A little DNS modification and another run at certbot can get that going.
OR can it?
Won't be able to CNAME the apex [that'll wreak havoc upon the interwebs - LOL].
Thanks for replying! As you can probably tell I'm a little out of my depth here. Could you elaborate a little bit? Its just that you could be talking in a foreign language right now
Let me step back a couple of paces ...
There are basically four common ways to reach any web site:
http://example.com
https://example.com
http://www.example.com
https://www.example.com
Generally speaking, only one of the four is considered the "active" / "main site".
The other three are expected to direct the browsing client onward in that direction.
The HTTP sites forward to the HTTPS sites
And the base domain forwards to "www" [or in the other direction]
In your case, the base domain is being hosted by a parking page site, so it can't be set to forward and it doesn't support HTTPS.
So that covers two of the four.
The other two, the insecure should forward to the secure [but it doesn't (yet)].
Cover all four cases (as best you can).
They may involve separate providers.
OR
May require you to update the HTML or add an .htaccess file.
[YMMV - speak with the providers about what you want and they may be able to help or point you in the right direction]
But technically you already do have a validated site. https://www.davidaste.com/