Enabling the Web Application Firewall

mod_security is a Web Application Firewall (WAF) that filters and blocks known malicious HTTP requests. Blocked HTTP requests include many, but not all forms of Brute Force, Cross-Site Scripting (XSS), Remote File Inclusion (RFI) , Remote Execution, and SQL injection (SQLi) attacks.

DreamHost enables mod_security for free by default, but you can enable/disable this feature in the panel if necessary.

1. Navigate to the Manage Websites page.
2. Click the Manage button to open the Domain Settings page, which allows you to adjust various settings for your site.
   • If in Grid view, click the Manage button at the bottom of the website box.
   • If in List view, click the Manage button at the far right of your domain name.
3. Scroll down to the Additional Settings section.
4. To the right of Web Options, click the Modify button.
5. To the right of Web Application Firewall, click the toggle to enable or disable.
6. Click the Save Changes button.

The Web Application Firewall option enables the use of a special security module for your website. Many common attacks that can compromise your website are blocked by this option, but there are no guarantees that all attacks will be prevented. With this enabled, DreamHost proactively ensures that the most commonly known attacks are prevented.

DreamHost uses the HTTP response code 418. If you see 418 response codes in your access.log files, it means that the request was blocked by mod_security. However, this may not mean a specific visitor was blocked, but rather a request to your website. You need to read your log entries to determine what caused the 418 error.

Further details related to the block are often in the corresponding date stamped error.log entry. If you are having trouble deciphering why you are getting a 418 error in your log files, please don’t hesitate to contact support at Contact Support.

While a majority of DreamHost’s mod_security rule set is custom created as threats emerge, the base of DreamHost’s mod_security rule set comes from the OWASP mod_security Core Rules Set.

When a 418 error response is triggered by a user visiting your site, the following error message appears:

Unused. The server encountered an internal error or misconfiguration and was unable to complete your request.

The 418 error indicates that there is a temporary ban by mod_security on the server. Most often, this is triggered by multiple failed login attempts to a WordPress site. Once triggered, the message appears after any subsequent attempts to access the login page.

If you are seeing the 418 error outside of the context of a WordPress site login, please review your error and access logs for 418 response codes or Contact Support.

Disabling and modifying mod_security rules via an .htaccess file is not supported at this time.