SSL and definition of server

Hi Everybody!

When I think of “sever,” I think of the server as I built it. So I get confused when Virtualmin tells me I have to add a server - I mean what did I install Virtualmin /to/ if not a server?

Here’s what’s going on.

I created a new server in Digital Ocean. The hosting account is held elsewere so I had them enter an A record to point web traffic to my Digital Ocean server. And that’s all I need, no mail or anything else. For now. This server had Apache, PHP and mySQL installed before I installed Virtualmin. Virtualmin hiccuped once about the pre-existing mySQL installation but I think I corrected that issue. In any event, Virtualmin is installed and seems to be happy.

So I saw that https is “crossed out” when accessing Virtualmin. Seems I need an certificate. There wasn’t any tutorial but I did find this page
https://www.virtualmin.com/documentation/tutorial/how-to-add-an-ssl-certificate .

My problem is that nowhere in my interface can I find /anything/ that says “Server Configuration.” There is an option somewhere to “Change IP Address,” but I can’t imagine why I would want to do that. The server’s IP address is the one I’ve been assigned. “It’s mine,” as Cartman would say. If I change it I’ll be pointing to someone else’s domain.

I do see a feature to “Create Virtual Server,” but not sure why I have to do that as the actual server is already created and running Virtualmin. But it sounds like that’s what I have to do.

Can someone clear me up here?

Thanks.

I took a plunge and “created” the virtual server with nothing by www and ssl. Based on the tutorial (yes, there was a tutorial) I now have a self-signed certificate. Yet my browser (Chrome) disagrees and still shows the https as crossed out. Have I missed a step?

Howdy,

If you’re accessing a site via https, and it works, with the exception that you see a line through the “https” part in the location bar – that actually sound normal.

Self signed certificates generate a warning, and browsers show they’re not fully secure/trusted by adding a line through the https part.

If you had a commercial SSL certificate, it would stop doing that – but that’s often not necessary, as self signed certificates can work great when there’s not a lot of people accessing the site, and when you trust that you’re going to the correct site.

-Eric