| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Ubuntu 24.04 |
| Webmin version | REQUIRED |
| Virtualmin version | 8.1.0 Pro |
I have an IP with the port 10000 which I can access Virtualmin. However, it is not secured. Where is the documentation to show me how to secure it? I thought the wizard would have done this normally, but apparently I am not doing something right.
What do you mean by “not secured”?
I’m guessing no ssl certificate as the OP is connecting to webmin via an IP address rather than a domain name
If that’s what you mean (no TLS certificate), it means your system hostname does not resolve.
If your system hostname resolves, the install process will try to get a certificate from Let’s Encrypt.
But, if it does not resolve, or if for some reason validation fails, you’ll need to set that up yourself once you have a name that resolves correctly.
I didn’t say anything about an IP address.
The OP did as you can see from this quote from post 1
The certificate is not validated. It does not mean HTTPS is not working.
What does the certificate list as domains etc… It probably is a self-signed cert anyway.
Without knowing the domain etc… if the user is connecting to the hostname, I think there is an option specifically to get a SSL for it and this might not be on.
Ah, then, yeah. Virtualmin never requests a cert for an IP. That used to not be supported by Let’s Encrypt.
OP, use hostnames.
I apologize for not being more clear in my explanation. I do have a hostname. I have the DNS records pointing to the IP of Virtualmin. When I use the hostame with the default port it says it does not recognize the hostname. I have given the time for it to propagate for 4 days. So it not being enough time is not the issue.I will copy the exact error and post here. Thank you all for being patient.
For that length of time I suspect your hostname doesn’t resolve. Why not create a domain using virtualmin obtain the ssl certificate for it and then log in that way. My guess is your hostname doesn’t resolve the the ip address, qhich in turn could be an error in your dns records. This is impossible to debug without your real hostname and ip address
Thank you for that suggestion. I will try that route.
Propagation is not a thing with regard to merely updating records. It can never be longer than the TTL of your zones records, usually about five minutes, by default, on most DNS servers. If you’re waiting on propagation, you’re probably wasting your time. (Glue records might have a propagation time of up to about 24 hours, though more realistically only a few hours, tops.)
You can also know whether records are right pretty much immediately, by explicitly querying your DNS servers (but make sure you know what your DNS servers are).
If you browse to https://your.system.hostname:10000 and it doesn’t give you the same Webmin login as browsing to the IP, then your DNS is wrong. So, you need to track down the problem with DNS (and don’t waste days waiting on “propagation”).
