509.949.2162 jeremy@bondbyte.com

There’s a lot going on. I Changed VPS hosts. I upgraded Ubuntu from 14 to 18, of course PHP and a slough of other shit. Then of course upgraded from WordPress 4.6 to 5.2. Been dealing with various random issues. Here are a couple from today.

Installed LetsEncrypt and SSLd off my hosted sites.


1. LetsEncrypt WordPress Site

This is pretty straight forward. Console in to your server and run

certbot –apache -d sitename.com

8/19/19 Scratch That. Just run the command cerbot and then enter the number from the list of properly configured sites.

This will grind thru a few things, then prompt you to redirect requests to SSL. (option 2). Select 2, press enter. Certbot will add new .conf file and adjust the existing site.conf filelocated in /etc/apache2/sites-available.

What doesn’t happen. It doesn’t adjust the wp-config.php file in WordPress for good reason. WordPress isn’t Apache.

Throw this your wp-config.php file.

//Use HTTPS for WordPress
define('FORCE_SSL_ADMIN', true);

Read more about this here.

2. Disable Gutenburg Manually

Edit /wp-includes/functions.php in the your wordpress hive by adding the following line

add_filter(‘use_block_editor_for_post’, ‘__return_false’);

3. WordPress asking for FTP files.

Don’t install a Linux FTP client on a webserver. Bad Idea. Go to wp-config.php and the following lines near the bottom.

/** Sets up direct download */