Doing it all again, this time asking for server to be created with the self-signed cert re-generates the cert, and then going to ask for an LE cert after is trying for all the alias again. This didn’t happen a couple of days ago and is possibly a step backwards.
This might be my fault, I usually select to Edit Virt Server, untick DNS domain enabled - I missed doing that before requesting the LE cert.
@Randomz Jamie just fixed a bug requesting LE certificate for aliases on default domain creation in wizard. The only issue that is still present though (with all checked in code), is that self-signed certificate is applied, making connection error popup appear.
I just did a fresh install, then ran the Wizard. First go I selected to create the domain with self-signed and it created a new certificate along with the error message.
The I restored snapshot and ran the Wizard but this time I selected for an LE certificate. Again it created a self-signed with the error message.
So what is supposed to have changed, or am I not getting the up to date installer?
I tried 7.1 a couple of times today, it works well and fixed the MySql root password bug - thanks guys.
I am still curious about the option to create the default domain which defaults to using a LetsEncrypt certificate, but still fails to do that. Looking at the files, .etc/letsencrypt directory created but with nothing entered apart from the one line cli.ini file.
What is supposed to happen?
Thanks guys for also stopping it from regenerating the self certificate.
Perhaps, what could work in your case is to first deleting the default domain created earlier and then, going to, System Settings ⇾ Virtualmin Virtual Servers ⇾ Configuration: Defaults for new domains and set Address format for Apache virtual hosts option to Always use *, and then re-run the wizard and create default domain anew – does it fix the problem for you?
Another thing, doing this on 7.1 doesn’t apply the LE cert to port 10000 for Web/Virtualmin. It used to which was the only real reason I used it as the default domain for me is just to run Virtualmin.
EDIT! It appears to not be applying it at all to the default domain if I go back to Server Config, SSL Cert and have a look.
Looking via command line it appears to be in place in /etc/letsencrypt/live etc
It would work if DNS pre-configured correctly (cloud DNS or glue records on registrar side).
It will apply Let’s Encrypt certificate if request is successful. Self-signed certificate will not be applied, as there is no point in doing it, because miniserv already has a self-signed certificate.
Try going to virtual-server.name - Server Configuration ⇾ SSL Certificate / Let’s Encrypt page, disabling validation with choosing Skip tests and requesting a certificate.
Spammer. I have deleted the user, blocked them, and removed their links. I didn’t see this earlier.
Edit: Also, don’t repeat the spam links when a spammer posts! You very well could have gotten yourself reported as a spammer, either automatically or by a user.
I would just like to add that with headless servers I decided to create one cert for ALL domain names, and a wildcard (*.domain.tld) cert for all those names. Yes, using LE. This made it so much easier.
Assuming one machine has no more than 100 domain-names this works fine.
Would be nice if VM would offer this as an option.
That is dangerous, and I don’t recommend it. Wildcards already have security implications (and I don’t recommend them!), but one cert for all domains is even worse. Anyone on the server can impersonate anyone else, and can copy the cert off and re-use it elsewhere.