This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing:selfhostedwp [2022/02/02 19:49] – oemb1905 | computing:selfhostedwp [2023/12/16 20:33] (current) – oemb1905 | ||
---|---|---|---|
Line 11: | Line 11: | ||
------------------------------------------- | ------------------------------------------- | ||
- | This tutorial is for setting up a self-hosted WordPress instance on Debian GNU/ | + | This tutorial is for setting up a self-hosted WordPress instance on Debian GNU/Linux. This tutorial assumes you have some familiarity setting up a LAMP stack. If you need help with that, check out [[https:// |
- | sudo apt install php-cgi php-cli php-zip php-mysql php-mbstring php-intl php-fpm php-curl php-gd | + | sudo apt install |
| | ||
- | Or ... | + | Sometimes dpkg can choose which version of php you want and it's not always the version you want. In those cases, you can explicitly specify the version you need. Some packages are only available as '' |
| | ||
- | sudo apt-get install | + | sudo apt-get install |
| | ||
- | Okay, let's now enable fast cgi and rewrite php modules and then check your config. | + | Apache2 will set up a 000-default.conf automatically |
+ | |||
+ | sudo apt install certbot letsencrypt python3-certbot-apache | ||
+ | sudo certbot --authenticator standalone --installer apache -d site1.com --pre-hook " | ||
+ | crontab -e | ||
+ | <30 2 * * 1 / | ||
| | ||
+ | Once you have the LAMP stack setup and TLS properly configured, it's time to make some decisions on your php handler and your apache2 multi-processing module (mpm). There' | ||
+ | | ||
+ | sudo apt remove libapache2-mod-php* --purge | ||
+ | sudo apt install php8.3-fpm php8.3-cgi | ||
+ | sudo a2enmod ssl | ||
+ | sudo a2enmod headers | ||
+ | sudo a2enmod cache | ||
sudo a2enmod rewrite | sudo a2enmod rewrite | ||
+ | sudo a2enmod setenvif | ||
+ | sudo a2dismod php8.1 | ||
+ | sudo a2dismod php8.2 | ||
+ | sudo a2dismod php8.3 | ||
+ | sudo a2dismod mpm_prefork | ||
+ | sudo a2enmod mpm_event | ||
+ | sudo a2enmod proxy | ||
sudo a2enmod proxy_fcgi | sudo a2enmod proxy_fcgi | ||
- | sudo a2enconf | + | sudo a2enconf |
+ | sudo a2enconf php8.3-cgi | ||
sudo apache2ctl configtest | sudo apache2ctl configtest | ||
- | + | | |
- | Move index.php to the top priority | + | sudo systemctl restart php8.3-fpm |
- | + | ||
- | | + | There are two standard ways to configure |
- | <DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm> | + | |
- | + | | |
- | Optionally, we can install phpmyadmin, and if you do, you should secure as follows: | + | SetHandler " |
+ | </ | ||
+ | |||
+ | That takes care of configuring | ||
+ | |||
+ | | ||
+ | sudo apachectl -M | grep ' | ||
+ | sudo apache2ctl configtest | ||
+ | |||
+ | The output of mpm should show mpm_event and the output of proxy grep should show proxy_module and proxy_fcgi_module in use. If not, trace back over the steps above and see what went wrong. As for configtest, it should either tell you what's wrong or return " | ||
+ | sudo apt install phpmyadmin | ||
sudo htpasswd -c / | sudo htpasswd -c / | ||
- | sudo nano / | + | sudo nano / |
- | + | ||
- | Enter the following in the file that opens: | + | |
- | + | ||
< | < | ||
< | < | ||
< | < | ||
<Require valid-user> | <Require valid-user> | ||
+ | |||
+ | If you don't need something as heavy as phpmyadmin, you can optionally create a phpinfo page instead: | ||
+ | |||
+ | sudo nano / | ||
+ | sudo htpasswd -c / | ||
+ | sudo nano / | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <Require valid-user> | ||
+ | |||
+ | Use these tools to make sure your handler and multi-processing module are configured to your preference and functional. After that's all working, let's make sure that your WordPress index.php is set to top priority as follows: | ||
| | ||
- | Close and save the file. Let's set up a database now for the WordPress instance: | + | sudo nano / |
+ | < | ||
+ | |||
+ | Close and save the file. Let' | ||
sudo mysql -u root -p | sudo mysql -u root -p | ||
Line 51: | Line 93: | ||
EXIT; | EXIT; | ||
- | Next up, it is time to allow overrides in your primary apache configuration: | + | Next up, it is time to allow overrides in your primary apache configuration. This is optional but/and it allows WordPress extensions to make configuration changes to .htaccess and/or other changes to the web server. It's often helpful, but you can leave it off if you prefer and configure everything manually. |
sudo nano / | sudo nano / | ||
- | < | ||
< | < | ||
| | ||
- | If you have not set the fully qualified domain name, you may get an error - that can safely be ignored unless you desire it. If you want to get rid of that, navigate to ''/ | + | Let's now shell into our instance |
- | | + | |
- | mkdir wpdownload | + | |
- | cd wpdownload | + | |
curl -O https:// | curl -O https:// | ||
tar xzvf latest.tar.gz | tar xzvf latest.tar.gz | ||
- | | + | |
- | sudo chmod 640 ~/Downloads/ | + | |
- | cp ~/Downloads/ | + | |
- | | + | |
Okay, we will need the files and directories I created once we get it running. | Okay, we will need the files and directories I created once we get it running. | ||
sudo mv ~/ | sudo mv ~/ | ||
- | Now, let's set up permissions and ownership: | + | Now, create proper |
sudo chown -R www-data: | sudo chown -R www-data: | ||
Line 81: | Line 117: | ||
sudo chmod -R 755 / | sudo chmod -R 755 / | ||
- | Ok, time to grab ' | + | It's now time to configure your '' |
| | ||
curl -s https:// | curl -s https:// | ||
sudo nano / | sudo nano / | ||
+ | <Replace the example salts with those you just downloaded using copy/ | ||
| | ||
- | Let's also add the following line to the '' | + | Sometimes, for reasons I am not sure about, WordPress does not allow users direct uploading. If/when that happens, |
sudo nano / | sudo nano / | ||
< | < | ||
- | | ||
- | Plug-ins and other WP services can mess with the '' | ||
- | sudo nano /var/www/site1.com/public_html/ | + | Let's now visit site1.com |
- | + | ||
- | | + | apt install memcached |
+ | nano /etc/ | ||
+ | < | ||
+ | a2enmod cache | ||
+ | a2enmod expires | ||
+ | a2enmod headers | ||
+ | a2enmod rewrite | ||
+ | |||
+ | After isntalling memcached and enabling those modules, navigate to your web root and adjust your .htaccess | ||
+ | |||
+ | | ||
+ | ExpiresActive On | ||
+ | ExpiresByType image/jpg " | ||
+ | ExpiresByType image/jpeg " | ||
+ | ExpiresByType image/gif " | ||
+ | ExpiresByType image/png " | ||
+ | ExpiresByType text/css " | ||
+ | ExpiresByType text/html " | ||
+ | ExpiresByType text/ | ||
+ | ExpiresDefault " | ||
+ | | ||
< | < | ||
- | | + | |
- | RewriteBase / | + | |
- | RewriteRule ^index\.php$ - [L] | + | |
- | RewriteCond %{REQUEST_FILENAME} !-f | + | RewriteRule ^index\.php$ - [L] |
- | RewriteCond %{REQUEST_FILENAME} !-d | + | RewriteCond %{REQUEST_FILENAME} !-f |
- | RewriteRule . /index.php [L] | + | RewriteCond %{REQUEST_FILENAME} !-d |
+ | RewriteRule . /index.php [L] | ||
+ | < | ||
+ | Header set Timing-Allow-Origin " | ||
+ | </ | ||
</ | </ | ||
- | # END WordPress | ||
- | Visit wordpress site and configure by opening a web browser of your choice and entering site1.com. If you need more than one site, but do not want to set up a separate virtual host, for example using '' | + | < |
+ | Header always set X-Content-Type-Options " | ||
+ | < | ||
+ | SetEnvIf Origin " | ||
+ | </ | ||
+ | Header | ||
+ | Header set Access-Control-Allow-Credentials " | ||
+ | < | ||
+ | Header set X-Frame-Options " | ||
+ | Header set X-XSS-Protection " | ||
+ | Header set X-Download-Options " | ||
+ | Header set X-Permitted-Cross-Domain-Policies " | ||
+ | Header set X-DNS-Prefetch-Control " | ||
+ | Header set Pragma " | ||
+ | Header set Age " | ||
+ | Header set Cache-Control "" | ||
+ | Header set Strict-Transport-Security " | ||
+ | Header set Referrer-Policy "" | ||
+ | Header set Cross-Origin-Embedder-Policy " | ||
+ | Header set Cross-Origin-Opener-Policy " | ||
+ | Header set Report-To ' | ||
+ | Header set Content-Security-Policy " | ||
+ | Header set Referrer-Policy " | ||
+ | Header set Feature-Policy " | ||
+ | </ | ||
+ | </ | ||
- | You can optionally require an sftp server instead of using the default installer. Here's an example using proftp, which is still maintained: | + | Personally, I don't think anyone should be using ftp. Sftp is fine, and if someone needs that, here's an example |
sudo apt install proftpd ftp ftp-ssl | sudo apt install proftpd ftp ftp-ssl | ||
+ | sudo a2enmod tls | ||
cd / | cd / | ||
sudo openssl req -new -x509 -days 7305 -nodes -out ftpd-rsa.pem -keyout ftpd-rsa-key.pem | sudo openssl req -new -x509 -days 7305 -nodes -out ftpd-rsa.pem -keyout ftpd-rsa-key.pem | ||
sudo nano / | sudo nano / | ||
+ | <enter parameters> | ||
| | ||
+ | Next, enter the TLS module in tls.conf underneath ''# | ||
+ | |||
+ | sudo nano / | ||
< | < | ||
| | ||
Line 127: | Line 216: | ||
| | ||
</ | </ | ||
+ | sudo systemctl restart proftpd.service | ||
| | ||
- | Put this snippet under ''# | + | 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 |
- | + | ||
- | sudo systemctl restart proftpd.service | + | |
- | + | ||
- | Happy hacking! | + | |
- | --- //[[oemb1905@jonathanhaack.com|oemb1905]] | + | --- //[[jonathan@haacksnetworking.org|oemb1905]] |