| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Rocky 10.1 |
| Webmin version | |
| Virtualmin version | 8 |
Silly Firefox won’t let me accept self signed certificates any more.
The Virtualmin 8 install went without error, but I can’t access it.
Have been trying to get FFox to behave to no avail.
Can anyone give me detailed steps to get FFox to behave, or it there something that can be done differently during the VMin 8 install to avoid this issue?
Any reason you can’t use Let’s Encrypt? I know this doesn’t answer your question but if searching hasn’t answered it then maybe it is an easier/better option.
What is your domain’s TLD? It is .com or something else?
Look for Settings like “Verify the current validity of certificates by querying the OCSP server”, under Settings → Securty and Data Protection turn it off!
Domain TLD is .com.au
Can’t get into VMin to select anything.
Opps. 
Have you simply tried another browser? I use 4 to 5 regularly so I kinda forget that isn’t the norm.
I only use FFox, but may have to look at something else. I really don’t want to use any chrome based or Edge.
You could install just long enough to get around this problem and then can it.
Hmm.. I just literally had over a hundred packages show up on my Debian 13 machine so I did them and rebooted. At least the Linux version has the advanced option pop up and my Firefox is the most locked down browser I use.
Can anyone please try and duplicate this?
Rocky 10.1, Virtualmin 8, Firefox 147.0 on Win10
Install VMin 8 from here - supplied by Ilia.
sudo sh -c "$(curl -fsSL https://download.virtualmin.com/install-script)" -- --bundle LAMP
Try to access the site with Firefox.
The only way I have been able to get in is by disabling ssl (miniserve.conf ssl=0).
Even then I can’t get an LE certificate as No virtual host matching domain.tld was found.
Probably due to the host being hidden etc. I know it’s in an obvious place to unhide it, but I can never find it when I want it. It’s a bit like Microsoft making decisions for me because they think I don’t know what I am doing, but at least VMin does have an option to unhide it - somewhere.
Perhaps it’s not accessible because I haven;t yet run the wizard?
Which I really don’t want to do until I can get https working.
I created a new remote VPS to test outside of my firewalls etc, Alma 10. Virtualmin worked right out of the box.
Restored snapshot on my local VM then installed VMin again - that now also works right away!
Ilia, if you had a fiddle I thank you very much!
If Firefox doesn’t show the “Accept the Risk and Continue” button, it’s almost always because HSTS is enforced through caching or preloading.
Since .com.au is not on the global HSTS preload list, HSTS will only be enforced by the browser if you’ve opened the same domain before with a valid SSL certificate.
The only way around it is to clear all browser settings related to this domain, or use a private tab.
Or, use the IP address instead of the domain name. The simplest way to bypass the warning is to connect using IP:10000. This is why we show this link in the installer in case the SSL certificate request for the hostname fails during installation.
What is the expected behavious for installing VMin 8 on Rocky 10?
2 x installs have instantly had LE certs, but the 3rd one has self signed.
If your hostname resolves, Virtualmin is able to get a cert for it. OS is probably irrelevant.
If you reinstall with the same hostname multiple times and request Let’s Encrypt certificates too often in a short time, after a few successful tries, Let’s Encrypt will stop and won’t issue another SSL certificate due to rate limits.
After updating my working VMin to 8, I tried a fresh install on a fresh Rocky 10.1 using the link on your download page :
"Installing Virtualmin 7 and all related packages "
Will that be updated soon?