This article is about blocking IPs in Pantheon for sites using the WordPress CMS. Prevent unwanted traffic incidents that might result in site outages and billing overages.
Review the nginx-access.log.
Download the nginx-access.log on the LIVE environment. The logs can be accessed using SFTP or by using the provided script from Pantheon’s documentation. Be sure to combine all the logs for a day if the site plan has multiple application containers. Identify the IP that has the highest number of visits and verify it with https://www.abuseipdb.com/
Be sure to install the plugin WP Traffic Jammer that can be downloaded at WordPress.org https://wordpress.org/plugins/traffic-jammer. The plugin has a wp-cli command that can be used on a remote wp-cli call using Terminus. It also has a settings page to add a single IP or an IP range.
Block the IP using Terminus.
Use remote wp-cli via terminus to block the IP.
$ terminus wp <sitename>.<env> -- jam block <ip>
To unblock the IP.
$ terminus wp <sitename>.<env> -- jam unblock <ip>
Block the IP on the WordPress Admin Dashboard.
On the Admin Dashboard, you would see the left side menu, click “Traffic Jammer” and add a single IP or IPs, CIDR format can be also used for IP ranges.
Block the IP using a PHP Snippet
Use a PHP snippet that can be added to wp-config.php file. This offers an advantage since it would be triggered before loading all the plugins and themes.
What a great way to start a new year with releases, as this is the same for the company offering the best WebOps SAAS (Software as a Service) Platform which is Pantheon. During the last week of December, a new version tag of Terminus has been released, comes version 3.
What is Terminus?
The Terminus command-line interface provides advanced interaction with Pantheon. Terminus enables you to do almost everything in a terminal that you can do in the Pantheon Dashboard, and much more. In practice, some of the features missing on the Dashboard are included in Terminus. Developers can also include in development workflow or as part of a script for deployment using continuous integration.
Operating System Compatibility
As of this writing tested to work on the following platforms
Windows 10 – WSL 2 Ubuntu 20.0
Ubuntu 20.0 – this would include Ubuntu under Docker or VirtualBox
Before getting frustrated, included also are the list of platforms that Terminus would not work:
Windows 10 – Command Line
Windows 10 – Git Bash (MingW)
Ubuntu 18.0 and later versions
Linux system with coreutils equal to or less than 8.28
PHP 7.4 or above
PHP Extensions (mbstring, xml, curl, cli)
git (if you need to include plugins)
As for the prior version of Terminus, it can be installed in many ways, the new version is limited to work only on the standalone PHAR package. Assuming all the requirements are met. Start the installation on the home folder
mkdir ~/terminus && cd ~/terminus
curl -L https://github.com/pantheon-systems/terminus/releases/download/`curl --silent "https://api.github.com/repos/pantheon-systems/terminus/releases/latest" | perl -nle'print $& while m#"tag_name": "\K[^"]*#g'`/terminus.phar --output terminus
chmod +x terminus
sudo ln -s ~/terminus/terminus /usr/local/bin/terminus
The new version of Terminus comes with a plugin manager, installation now can be done using the terminus command
The security team from Cloudflare did continue to investigate and found additional flaws in the 2.15.0 version of Apache Log4j, which allows adversaries to initiate denial-of-service (DoS) attacks (CVE-2021-45046). The issue has been addressed on the newly available version which is 2.16.0. All companies which include Log4j on their infrastructure stack are suggested to patch to the updated version.
Cloudflare is known for its DDOS protection and is used by more than seven million websites, they have advised their customers to modify the WAF configuration to mitigate the exploit.
100514 (legacy WAF) 6b1cc72dff9746469d4695a474430f12 (new WAF)
100515 (legacy WAF) 0c054d4e4dd5455c9ff8f01efe5abb10 (new WAF)
100516 (legacy WAF) 5f6744fa026a4638bda5b3d7d5e015dd (new WAF)
The mitigation is divided into three rules that look at HTTP headers, body, and URL, in that order.
They have also introduced a fourth rule that will guard against a far broader variety of assaults at the cost of a greater false-positive rate. As a result, they have made it available, but it’s not set to BLOCK by default:
100517 (legacy WAF) 2c5413e155db4365befe0df160ba67d7 (new WAF)
Cloudflare was the preferred choice of Kinsta, to make client websites faster and more secure. The reason they are not affected by log4j vulnerability. Kinsta is a managed WordPress hosting company that offers feature-rich, cost-effective services. They received the highest rating this year from the G2 review.
WordPress plugin to block IP and bots categorized as harmful, resulting in heavy server loads from frequently crawled pages, or utilized in vulnerability/security breach scans. The plugiin can block: