I’ve been running my old WordPress site on AWS’s LightSail for years now, but now that AWS is charging for IPv4 addresses the cost has doubled and I’m tired of paying for it. So this weeks project has been to transfer my diditalsos.com to digitalsos.net and get it running on a raspberry Pi.

More challenging than I though. First I’ve not updated the old WordPress site so exporting and importing to a new site didn’t work. The Graphene theme wouldn’t update and I resorted to manually transferring files with mysqldump and copying all of the /wordpress/wp-content/uploads files. This screwed up part of the site that listed all of the pages but that is to be figured out later.

Finally got the basics up locally on my Raspberry Pi but guess what NAT forwarding the ports 80 and 443 on my WiFi router didn’t work. Why? I was doubled NAT’ed with Quantum Fiber’s Modem running it’s own NAT. Finally found that I could navigate to the Advanced setup, select the 2nd WAN Setting to Transparent Bridge Mode and the external IP would go to my AE550 the same way with Dynamic IP. TaDa NAT forwarding to port 80 worked but not 443. The WiFi Router needed to have the remote administration port changed from 443 to anything else and then disabled.

Finally after getting everything setup was Apache even listening? Nope: I used sudo ss -ltnp to see and then a2enmod ssl to enable.

finally even though I got Let’s encrypt’s cipherbot to get my certificate it wasn’t used. Apparently you need to add the path’s to those files in the configuration file <VirtualHosts *:443> section:

SSLCertificateFile /etc/letsencrypt/live/digitalsos.net/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/digitalsos.net/privkey.pem