Subdomain is cloud.josephsprivate.space
You got an internal server error there. Doesn't the apache domain logs say more about this?
I am originally from the Caribbean so there are some Caribbean dishes there.
Oh that's cool. About the only thing I know about that region is like most people know the Roti dish. But I was always interested in international dishes. So I will sure have another look and try it out. Unfortunately my wife is less international, wat meer van de stijl van wat de boer niet kent dat lust ie niet, alhoewel ze wel shoarma lust. I'm sure you get my drift, so I probably will have to cook something for my own then when testing this, but I don't mind.
It is weird though that this Solo license comes with so many problems.
Well in fact it doesn't. I'm also sure your not the only one, but there aren't a lot of issues to be found here purely from the personal licenses.
Most of them were from the beginning, that people did not understood that admin was a useraccount.
Normally it's reall install and have fun. I've installed a couple myself on VPS systems and had no issues at all. However I must say that I never used ipv6 yet, I just disabled that on the Centos servers.
Sending a ticket is indeed not for personal licenses, unless it's really a bug, then there is a way somehow, but I don't remember how exactly.
But if I understand correctly, the subdomain records were copied to the external DNS.
However, what amazes me the most, is that the .nl domain you added works all fine.
Ah wait... maybe I found something. It might be maybe LE and the DNS gets confused about the subdomain, because it's not setup like it should be if I'm correct.
I had a look in dnsdumpster.com on your main domain name. Then I found the cloud subdomain having 2 different ip addresses.
The record of cloud.josephsprivate.space is pointing to an 31.186.x.x ip at cloud.dynad.com with Serverius-AS here in NL.
But
www.cloud.josephsprivate.space is pointing to 92.63.x.x at pcExtreme.
And I can imagine that is causing a server error. Because
www.sub.domain.com and sub.domain.com are create both by DA when creating a subdomain. If DA is checking it will get confused.
I presume you're still working on this, because when I just visited the subdomain in Chrome, something very odd happend, suddenly I was routed to
https://www.cloud.josephsprivate.space/cloud
which is wrong anyway.
It's either (www.)cloud.josephsprivate.space or (www.)josephsprivate.space/cloud/ but what just happened is not possible.
So as far as I see and check at least this should be fixed for this subdomain and set to the same ip address or just remove the www version.
There are loads of other subdomains I see, but lots are not reachable at this moment on the amazone servers it seems.
Edit: seems you fixed that,
www.sub and sub. are both pointing to the 92.63.x.x ip now, however, now we have the wrong redirect again.
https://cloud.josephsprivate.space/cloud/
in Firefox. Maybe cache. In Edge and Chrome I got a forbidden now in the correct place.
I'll leave you working with it, it's not much use looking up things if you're working with it.