| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Ubuntu Linux 20.04.6 |
| Webmin version | 2.021 |
| Virtualmin version | 7.7 Pro |
| Related packages | all packages are up to date |
hello everyine can some one please help me with this issue im having every time i login to my server i keep getting this in the url bar on my coogle chorme browser any ideas on how to fix this
when i go to webmin configureation then go to ssl encrypton then go to lets encrypt and request certificate this error shows up
I am assuming that you have checked with a different browser. Or that yesterday you could access https using Chrome. Then the most likely cause is that Chrome is pulling the page from cache - try Ctrl + R to reload the page.
OK forget that - I cross- posted with your 2nd post!
that looks to me like a request for a LE to localhost/router IP. (192.x.x.x)
You cannot request a Let’s Encrypt certificate for an IP address, and you should not use an IP address to communicate with your server (once you have names that resolve to your server’s IP).
Get a certificate for one of your Virtualmin managed domains, and use that to communicate with your server. Webmin will answer on all names managed by Virtualmin (assuming your DNS is right), and it will use the certificate for that name, assuming it has one.
ok so how do i fix this problem
my dns servers is with namecheap as that is where my domain name is brought from
You just said you’re hosting your DNS with Namecheap. If that’s so, the name server on your system is irrelevant, it isn’t doing anything, and you can/should turn off the DNS Feature in Virtualmin.
What problem are you trying to solve? I think I’m confused, because this seems to be changing the subject from what I thought we were talking about.
yes i have turned off the dns feature in virtualmin and my firist question was about the problem with the url bar showing this error and yes my dns is with namecheap too i have no problems with my dns
its saying that its not secure all the time even on a differant bowser
as you can see the dns feature is not ticked
As I said above:
You need to create a virtual server in Virtualmin (a domain), setup the necessary records for that domain at your registrar, and then request a certificate from Let’s Encrypt.
You’re trying to talk to your server on an IP address, which can’t have a Let’s Encrypt certificate. They do not issue certificates for IP addresses. So, don’t do that! Use a name to connect to your server. If you use a domain for a website that is managed by Virtualmin, and if you have setup the right A records, you can request a free certificate from Let’s Encrypt and the error will go away.
But I can still (just) see in that clipped image that you are requesting an IP (https://1) and unless your domain starts with a 1 you are using an IP (Joe made it perfectly clear you cannot request a LE cert for an IP.)
Sorry Joe, I seem to be cross posting (slow typer) - I’ll leave.
this is what shows up in the url bar when i login so how do i change that to the domain name
Don’t be impatient - it simply annoy people trying to help and makes them less inclined to do so.
I know I said that I would stay away but 
you have a domain registered I cannot see how we can make it any clearer.
Do not try to use https://[IP address] in your browser - you will never match https with an IP address LE certs are not provided for IP addresses
type the https://[yourdomain] in the browser address bar.
ok sorry for the impatient i dont mean to be and ok i will try that i have just the domain name and it just keeps going back to the ip address
Chrome and many other browser’s won’t reload the certificate not even on hard purging cache, i.e. Ctrl + Shift + R hotkey. However, closing the tab and then re-opening it with Ctrl + Shift + T will work, in case the certificate was really updated.
ok i will try that
i have just tried that and it didnt work and this is what it says
What exactly doesn’t work? Which URL is being accessed in the browser?
This website has a valid SSL Certificate. Just visit it with other browser (Firefox, Brave, Edge). Chrome has some issues, you need to clear the cache and open it again.
