This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
computing:selfhostedwp [2019/07/27 19:43] – oemb1905 | computing:selfhostedwp [2023/06/30 04:25] – oemb1905 | ||
---|---|---|---|
Line 7: | Line 7: | ||
------------------------------------------- | ------------------------------------------- | ||
- | // | + | // |
------------------------------------------- | ------------------------------------------- | ||
- | This tutorial is for users of 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 |
- | sudo apt install | + | sudo apt install |
- | <sudo apt install ftpd-ssl> (not sure if this is needed any longer) | + | |
- | cd / | + | |
- | sudo openssl req -new -x509 -days 7305 -nodes -out ftpd-rsa.pem | + | |
- | sudo nano / | + | |
| | ||
- | < | + | 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 as follows: |
- | | + | |
- | | + | |
- | | + | |
- | # Are clients required to use FTP over TLS when talking to this server? | + | |
- | | + | |
- | | + | |
- | | + | |
- | # Authenticate clients that want to use FTP over TLS? | + | |
- | | + | |
- | | + | |
- | </ | + | |
| | ||
- | You can technically put this snippet anywhere, but its proper location is under "# | + | sudo apt-get install php8.2-{common,cgi, |
| | ||
- | sudo systemctl restart proftpd.service | + | Apache2 will set up a 000-default.conf automatically and your host should now resolve. Be sure to set up TLS with certbot. Here's my preferred method: |
- | I do not change | + | 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 | ||
+ | |||
+ | sudo apt remove libapache2-mod-php* --purge | ||
+ | sudo a2enmod ssl | ||
+ | sudo a2enmod headers | ||
+ | sudo a2enmod cache | ||
+ | sudo a2enmod rewrite | ||
+ | sudo a2enmod setenvif | ||
+ | sudo a2dismod php8.2 | ||
+ | sudo a2dismod mpm_prefork | ||
+ | sudo a2enmod mpm_event | ||
+ | sudo a2enmod proxy | ||
+ | sudo a2enmod proxy_fcgi | ||
+ | sudo a2enconf php8.2-fpm | ||
+ | sudo a2enconf php8.2-cgi | ||
+ | sudo apache2ctl configtest | ||
+ | sudo systemctl restart apache2 | ||
+ | sudo systemctl restart php8.2-fpm | ||
- | sudo apt install mysql-server phpmyadmin apache2-utils php php-mcrypt php-xml php-curl php-gd php-cgi php-cli php-zip php-mysql php-mbstring php-intl php-fpm wget unzip | + | There are two standard ways to configure |
- | If this is the **first** time you installed mysql-server, | + | < |
+ | SetHandler " | ||
+ | </ | ||
- | sudo mysql_secure_installation | + | That takes care of configuring php-fpm and mpm_event. Before proceeding, navigate to your tld.domain in a web browser and make sure that your site resolves properly. If it does not, then you should debug your setup. To do that, there' |
- | + | ||
- | Once that is done, let's prioritize the web server' | + | |
- | + | ||
- | sudo nano / | + | |
- | + | ||
- | Now, you should | + | |
- | + | ||
- | < | + | |
- | DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm | + | |
- | </ | + | |
- | + | ||
- | Ok, let's restart the service for mysql-server: | + | |
- | sudo systemctl restart mysqld.service | + | sudo apachectl -M | grep ' |
- | + | | |
- | Secure phpmyadmin with user phpmyadmin and .htaccess file .phpmyadmin for security. | + | 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 / |
+ | < | ||
+ | < | ||
+ | < | ||
+ | <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: | ||
| | ||
- | | + | |
- | AuthName " | + | |
- | AuthUserFile | + | |
- | | + | Close and save the file. Let's now set up a database now for the WordPress instance as follows: |
- | + | ||
- | sudo systemctl restart apache2.service | + | |
- | + | ||
- | Now, the MySQL - more here than neeeded in case of trouble: | + | |
sudo mysql -u root -p | sudo mysql -u root -p | ||
- | | + | CREATE DATABASE databasename DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci; |
- | | + | GRANT ALL ON databasename.* TO ' |
- | | + | FLUSH PRIVILEGES; |
- | | + | EXIT; |
+ | |||
+ | 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. | ||
- | Trust me, do not use fancy database names and passwords. | ||
- | | ||
- | sudo apt update | ||
- | sudo apt-get install php-curl php-gd php-mbstring php-mcrypt php-xml php-xmlrpc | ||
sudo nano / | sudo nano / | ||
- | + | <AllowOverride All> | |
- | You need to search for "AllowOverride" and then change the ' | + | |
- | + | ||
- | < | + | |
- | other stuff | + | |
- | AllowOverride __All__ | + | |
- | other stuff | + | |
- | other stuff | + | |
- | </ | + | |
| | ||
- | Now, restart the webserver service, enable the rewrite mod, and check your config. | + | Let's now shell into our instance |
- | + | ||
- | sudo systemctl restart apache2 | + | |
- | sudo a2enmod rewrite | + | |
- | sudo a2enmod proxy_fcgi | + | |
- | sudo apache2ctl configtest | + | |
- | + | ||
- | If you have not set the fully qualified domain name, you may get an error - that can safely be ignored unless you desire it. | + | |
- | | + | |
- | mkdir wpdownload | + | |
- | cd wpdownload | + | |
curl -O https:// | curl -O https:// | ||
tar xzvf latest.tar.gz | tar xzvf latest.tar.gz | ||
- | | + | |
- | sudo chmod 660 ~/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 cp -ar ~/ | + | sudo mv ~/ |
- | sudo cp -ar ~/ | + | |
- | Now, let's set up permissions: | + | Now, create proper |
- | sudo chown -R username:www-data / | + | sudo chown -R www-data:www-data / |
sudo find / | sudo find / | ||
- | sudo chmod g+w / | + | sudo chmod 755 / |
- | sudo chmod -R g+w / | + | sudo chmod -R 755 / |
- | sudo chmod -R g+w / | + | sudo chmod -R 755 / |
- | Ok, time to grab 'secure values' | + | It's now time to configure your '' |
| | ||
curl -s https:// | curl -s https:// | ||
sudo nano / | sudo nano / | ||
- | <swap the defined values that were obtained from curl with the empty fields in the wp-config.php | + | <Replace |
+ | |||
+ | Sometimes, for reasons I am not sure about, WordPress does not allow users direct uploading. If/when that happens, add the entry to wp-config.php. If anyone knows why this is needed, please let me know! | ||
- | Enter user name and password for database in wp-config.php: | + | sudo nano / |
+ | < | ||
- | sudo nano /var/www/site1.com/ | + | Let's now visit site1.com |
- | + | ||
- | It looks something like this: | + | |
- | + | | |
- | /** The name of the database | + | |
- | define(' | + | |
- | + | | |
- | /** MySQL database username */ | + | |
- | | + | |
- | + | ||
- | | + | After isntalling memcached and enabling those modules, navigate to your web root and adjust your .htaccess as follows: |
- | | + | |
- | + | | |
- | Once that is done, restart the service: | + | |
- | + | | |
- | | + | ExpiresByType image/jpeg " |
- | + | ExpiresByType image/gif " | |
- | Plug-ins and other WP services can mess with the .htaccess file often, so use this default configuration below //when that happens//; more templates can be found here: [[https://codex.wordpress.org/htaccess|WP Codex]] | + | ExpiresByType image/png " |
+ | ExpiresByType text/css " | ||
+ | ExpiresByType text/html " | ||
+ | ExpiresByType text/x-javascript " | ||
+ | ExpiresDefault " | ||
+ | </ | ||
- | sudo nano / | ||
- | | ||
- | # BEGIN WordPress | ||
< | < | ||
- | | + | |
- | 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. | + | < |
+ | Header always set X-Content-Type-Options " | ||
+ | < | ||
+ | SetEnvIf Origin " | ||
+ | </ | ||
+ | Header set Access-Control-Allow-Origin %{CORS}e env=CORS | ||
+ | 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 " | ||
+ | </ | ||
+ | </ | ||
- | localhost | + | 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: |
- | Add Joomla, symlinks, directory permissions for low hanging fruit on WP, | + | sudo apt install proftpd ftp ftp-ssl |
+ | sudo a2enmod tls | ||
+ | cd / | ||
+ | sudo openssl req -new -x509 -days 7305 -nodes -out ftpd-rsa.pem -keyout ftpd-rsa-key.pem | ||
+ | sudo nano / | ||
+ | <enter parameters> | ||
| | ||
- | Addenda on web roots outside of /var/www/ | + | Next, enter the TLS module in tls.conf underneath ''# |
- | This tutorial | + | sudo nano / |
+ | < | ||
+ | | ||
+ | | ||
+ | | ||
+ | # Are clients required to use FTP over TLS when talking to this server? | ||
+ | | ||
+ | | ||
+ | | ||
+ | # Authenticate clients that want to use FTP over TLS? | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | sudo systemctl restart proftpd.service | ||
+ | |||
+ | Refresh WordPress and it should see the sftp server and allow you to make changes that way. Note: The sftp server | ||
- | --- //[[netcmnd@jonathanhaack.com|oemb1905]] | + | --- //[[jonathan@haacksnetworking.org|oemb1905]] |