I have a self hosted site using PC at home, been using it for a couple of years this way, use NO-IP dynamic (w2aiq.ddns.net) use it just to host podcast files (which works fine with just HTTP) but I would now like to add https for people to occasionally visit and not feel like they are going to get hacked with all the ridiculous warnings issued by their browsers!
I dont know why this has to be so difficult
My domain is:w2aiq.ddns.net (actual podcast address: http://w2aiq.ddns.net/wordpress)
I ran this command:
It produced this output:
My web server is (include version):apache with wordpress
The operating system my web server runs on is (include version):windows 10 home
My hosting provider, if applicable, is:self
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):no/ use wordpress, have direct access to the actual physical machine
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): do I really need certbot to get a certificate since I have direct physical machine access
