Category: WordPress

WordPress Update & Plugin Install Problems

Recently has a server that would not run WordPress updates or plugin installs no matter what I did. After extensive troubleshooting, it turned out the server had SELinux enabled which disallows outbound connections from Apache. One useful tool in troubleshooting update problems is the Background Update Tester plugin: http://wordpress.org/plugins/background-update-tester/ It gives some extra detail on why updates can’t run.    

Read More »

Block wp-login.php On Single Site In WordPress Multi-Site

In the recent rash of wp-login.php brute force attacks, I needed a way to block access to wp-login.php on a single domain in a WordPress multi-site with many domains. The impact on customers of blocking all domains was too great so I needed a more targeted solution. Here’s what I came up with for the .htaccess file:

Read More »

Redirect Loop on Plesk 11.5

If you get a rewrite loop in Plesk 11.5 then make sure you’ve set the Preferred Domain field correctly in the hosting settings. See this article for details: http://blogs.reliablepenguin.com/2013/08/09/canonical-rewrite-built-in-to-plesk-11-5 This can be especially tricky with WordPress. Make sure the site url in WordPress matches the preferred domain setting.

Read More »

WordPress Multi-site On Plesk

It’s easy to setup WordPress in multi-site mode on Plesk. Let’s assume you want to map:

to your multi-site installed on “acme.com”. From an SSH login on the server, just edit the file:

If the file does not exist then create a new empty file. Add the following line to the top of the file:

Save the file and tell plesk to reconfigure:

Now restart Apache:

Now you’re ready to go with multi-site. There’s an article here that addresses subdomain and webmail issues: https://codex.wordpress.org/Configuring_Wildcard_Subdomains_for_multi_site_under_Plesk_Control_Panel

Read More »

WordPress xmlrpc.php (pingback) Vulnerability

We’ve seen many WordPress sites being abused recently via the Pingback function in xmlrpc.php. Here are some good articles on the topic: http://www.incapsula.com/the-incapsula-blog/item/715-wordpress-security-alert-pingback-ddos http://perishablepress.com/wordpress-xmlrpc-pingback-vulnerability/ If you don’t need xmlrpc.php or Pinkbacks then we recommend that you block xmlrpc.php in your .htaccess file by adding code like this:

Or you could rename or remove the xmlrpc.php file. Here’s the config to block xmlrpc.php from Nginx:

Read More »

Categories

Get a free consultation from Reliable Penguin

Submit the form—or for immediate service call 866-649-7984.