This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
computing:selfhostedwp [2023/12/16 20:33] – oemb1905 | computing:selfhostedwp [2025/06/01 19:39] (current) – oemb1905 | ||
---|---|---|---|
Line 192: | Line 192: | ||
</ | </ | ||
- | Personally, I don't think anyone should be using ftp. Sftp is fine, and if someone needs that, here's an example of a simple sftp server using proftp: | + | I was getting a stubborn TLS redirect error for images. To address this, I went into ''/ |
+ | |||
+ | /** added this to secure images **/ | ||
+ | <meta http-equiv=" | ||
+ | |||
+ | |||
+ | Personally, I don't think anyone should be using ftp. Sftp is fine, and if someone needs that, here's an example of a simple sftp server using proftp. Note: you can also just use ssh nowadays as openssh-server includes a ready made sftp server. I retain this for historical knowledge. | ||
sudo apt install proftpd ftp ftp-ssl | sudo apt install proftpd ftp ftp-ssl | ||
Line 220: | Line 226: | ||
Refresh WordPress and it should see the sftp server and allow you to make changes that way. Note: The sftp server is public and anyone can access this with proper credentials even if it not for WordPress so use a proper password and make sure your TLS configuration is working. Your instance should now be pretty solid. The only other thing you might want is more than one WordPress site subdomain, for example, site1.cooldomain.com, | Refresh WordPress and it should see the sftp server and allow you to make changes that way. Note: The sftp server is public and anyone can access this with proper credentials even if it not for WordPress so use a proper password and make sure your TLS configuration is working. Your instance should now be pretty solid. The only other thing you might want is more than one WordPress site subdomain, for example, site1.cooldomain.com, | ||
- | --- //[[jonathan@haacksnetworking.org|oemb1905]] | + | --- //[[alerts@haacksnetworking.org|oemb1905]] |