All files and folders should be owned by www-data user and group if not then WordPress can’t change files hence fails to update from dashboard. wp-cli says to use sudo -u www-data -i — wp <command> but that gives This account is currently not available. Why? See this answer: https://askubuntu.com/a/486661/695240 You’re getting the This account … Read more
Your .htaccess and wp-config.php look fine. Error 101 is usually caused by a network, router or proxy issue. It could also be related to your browser cache and or cookies Have you tried connecting with a different browser or computer or clearing your browsers cookies? It can also be caused by your computers antivirus or … Read more
… and as per usual, I figure it out as soon as I post the question -.- Using this answer, I changed apache2.conf under /etc/apache2/. There is a section towards the bottom talking about the security model. The section Directory /var/www/ needs to be changed from AllowOverride None to AllowOverride All. I restarted apache and … Read more
The most efficient way to accomplish this would be to change the structure to /%postname%/ and add a 301 redirect to your .htaccess file for the old structure: RedirectMatch 301 ^/([0-9]{4})/([0-9]{2})/(?!page/)(.+)$ http://example.com/$3 Change example.com to your domain and add the redirect above the # BEGIN WordPress directive so it won’t be removed if WordPress updates … Read more
It looks like “Easy Apache” handles both Apache and PHP. Only a guess, but you have recompiled Apache/PHP without the needed image libraries– either GD or ImageMagick. Without those, the server cannot physically resize images. You can use a phpinfo() script to see if the libraries are present. If not, you will need to recompile– … Read more
I worked through this problem myself with the help of a forum mod on wordpress.org. You can see the full forum post here.
Why don’t you use WordPress core settings for doing this? This is the recommended way and doesn’t need editing .htaccess or Apache config directly. You can find the details here in WP docs. I’m posting the steps here: After installing WP in the root dir, Go to the Settings->General and change these values: WordPress Address … Read more
This is an issue with your server configuration, not with WordPress. Generally, it means that the server is not configured to use suPHP. (More, via Otto, here and here.) The (usually simple) solution is to add your FTP information to wp-config.php: define(‘FTP_USER’, ‘username’); define(‘FTP_PASS’, ‘password’); define(‘FTP_HOST’, ‘ftp.example.org’); Put these in wp-config.php (with your specific information, … Read more
Easiest way: Use mod_suphp instead of mod_php. This should just be a matter of using whatever ubuntu’s package manager is to remove mod_php and install mod_suphp instead. mod_suphp is a slightly modified version of mod_php. It does the same thing, but it sets the user of the apache process to be the same as the … Read more
Try changing your permalinks structure. Within the dashboard go to Settings > Permalinks and select the Post Name structure. When this is done click Save Changes. If Post Name is already selected, it might be worth clicking save changes again to reset the permalinks. Update: Per the comments below, WordPress does not, out of the … Read more