Securing HTTPS and my wordpress website
Hey Team,
So i am fairly new to this, and i noticed that once i installed a wordpress linode ( i love linode because its cheaper than shared hosting ), my website is unsecure and https wont work.
So the way i have things is like this.
Namecheap hosts my domain and points to linodes NS servers
installed a linode wordpress
I added the domain to Linode to manage the DNS Records as a master and i selected to add the records based off my wordpress linode
http://lbit.info works , but https wont work.
So i was wondering how id go about securing my website/server.
I was also thinking of using WHM because it would be nice if i had a central tool like WHM running everything and then i could give people cpanel etc, but i have no idea how to setup my own nameservers and how to setup that environment, so atm im just setting up hosting for my friends by hand, starting with my own website.
5 Replies
@lbit --
You need an SSL certificate and a web server configuration that properly supports it for https to work correctly.
See here:
It's free and pretty automatic. I've used it for years (for https AND ssmtp).
-- sw
@stevewi
Thanks for the info but I can't seem to find a guide for debian 10 which I used the automatic WordPress script for
Could you point me in the right direction
watrick
Linode Staff
We have a guide for using Certbot with Debian 10. Certbot is a tool that automates the process of getting a signed cert from Lets Encrypt.
Installing Certbot for TLS on Debian 10
This should be just what you need.
@lbit --
Just to complete the circle here, you can generally use instructions for recent versions of Ubuntu on Debian. This is because Debian is Ubuntu's upstream parent.
The key word here is generally… If the instructions use any Ubuntu-specific utilities or packages, then obviously they're not going to work on Debian. Obviously, any set of instructions involving the Ubuntu desktop are not going to work on Debian.
The package management utilities on Debian & Ubuntu are the same and, generally, packages are the same. When you install something on Ubuntu, things generally get put in the same places as they would if you were installing the same thing on Debian.
It's generally to Ubuntu's advantage to preserve upstream compatibility. Whether Shuttleworth agrees with that statement or not is a different discussion entirely.
I use Debian 10 too…after having sworn off Ubuntu after (too) many years.
-- sw