I have two servers, one main with two aliases connected to it.
The other is a test server with it’s own .com domain.
I want to create a WordPress multisite using subdomains on the test server, but I am unable to either create a wildcard certificate from let’s encrypt or add it to the subdomain manually.
I manage all my domains outside of Virtualmin, because I’ve never gotten the nameservers to work. I point the domains, both top and subdomains to my IP.
When I’ve tried to add a ssl cert including the subdomains I get an error, either that it’s unauthorized from the main domain or that it’s missing a TXT on my dns setup, but I have no idea what I’m supposed to put into my TXT, because I have no token or anything like that.
It’s seems so weird that my main domain is somehow including the subdomains of my test server. I’ve looked around on the server and I can’t find any information that says the test server domain I’m using is included in the main domain and server’s SSL cert.
you cannot create a wildcard certificate unless Virtualmin completely manages your domains DNS (i.e. your child nameservers are at your virtualmin server, you set this at your registrar)
unless the domains site1.testdomain.com and site2.testdomain.com resolve to your Virtualmin server the lets encrypt process will fail.
I am not sure if the sub-domains need to be sub-servers when using a wildcard certificate.
What I would try
correct any issues outlined above.
enable lets encrypt error display
Virtualmin → System Settings → Virtualmin Configuration → Configuration category: SSL settings → Show Let’s Encrypt error at domain creation time?
run the lets encrypt certificate creation manually and see what the errors are
UPDATE! I noticed that I shared my IP. Changed it to something else so I don’t end up in trouble here…
The subdomains resolve to my IP and have for days now. I am completely lost. I do not want to start over, like reinstalling virtualmin and re-install my servers. I do have backups, but I don’t want to deal with that again.
I’m just following the instructions using Let’s Encrypt. I don’t understand either where stuff went wrong. I’ve done all that you’ve shown me with that picture as well, but it does not help.
I’ve finally got access to certbot and I managed to create an SSL certificate there and add a token to my DNS TXT field for the domain I’m using, but the certificate does not show up on that page.
Yeah, I figured since I saw HTML stuff or something like it.
I know I don’t have to do anything manually, but I had to try since I don’t know wtf is wrong here.
notice the missing 217.76.60.120
if these domain names have been changed for this thread, he shouldn’t because there is no way the problem can be diagnosed without the real domain name
Ok, here’s the error from when I added the test domain + 2 subdomains in lets encrypt:
Update! Removed the photo due to me forgetting to hide my domain in one place.
I know I’m a little inconsistent with blurring the domains out, but you hopefully get the gist. I could only fit one photo here, but it’s the same for the second domain site2, and it tells me at the end that the domains need to resolve to the IP - which they do according to dns checking sites!
Well, thanks a lot for showing my domains and IP that I’m trying to hide!
Yes. Those domains listed there are the ones I own. The domains I’m using in this forum are hidden. site1.testdomain.com does not exist! Please remove my stuff from your post.
If I do have to post my real domains, why? That makes no sense. I don’t want people finding out a reason to hack me etc.
I understand enough with virtualmin, so this is not needed. thank you. Disappointed.
it’s all in the public domain any one can search for this and get the results from the information you gave so therefore you should remove the information that allows anyone to display the information I showed
Well I thought I did. I totally missed that I shared my IP by mistake. I don’t know how do hide it otherwise. I don’t think my host can do that for free and I refuse to pay for it.
Whatever. I’m screwed anyway. This is not going well. I guess I’m gonna have to use my test site without subdomains then. That’s probably the best case.
I’ve tried changing the name servers to cloudflare, but I don’t think that will help. It could be that my registrar are just so effing slow in resolving domains. It took multiple days before I could use my test domain properly.
Thank you. I shall try that tomorrow. As far as I know I don’t have a .well-known folder in my public_html directory, but I shall try doing that when my nameserver is working.
I’ll get back to you unless this thread is deleted for safety reasons.