Nginx部署ModSecurity遇modsecurity.conf-recommended源文件404问题

Hey there, that 404 error pops up because the raw file URL you're using has likely been deprecated or the repository structure shifted. No sweat—here are two solid ways to grab the recommended ModSecurity config file:

Method 1: Clone the ModSecurity Repository (Most Reliable) #

Cloning the full repo guarantees you get the latest version of the config file plus all associated resources:

# Clone the repository to your local machine
git clone https://github.com/SpiderLabs/ModSecurity.git

# Navigate into the cloned repo directory
cd ModSecurity

# Copy the recommended config file to your Nginx ModSec directory
cp modsecurity.conf-recommended /etc/nginx/modsec/

If you already have the repo cloned, run git pull first to fetch the latest updates before copying the file.

Method 2: Directly Fetch the File (Shorter) #

Use an updated raw file path to grab just the config file without cloning the whole repo:

wget -P /etc/nginx/modsec/ https://raw.githubusercontent.com/SpiderLabs/ModSecurity/main/modsecurity.conf-recommended

Post-Fetch Step #

Once you have the file, it's standard practice to rename it to the default config filename and enable active rule enforcement (if you want real protection instead of just detection):

# Rename the recommended config to the default config name
mv /etc/nginx/modsec/modsecurity.conf-recommended /etc/nginx/modsec/modsecurity.conf

# Edit the file to switch from detection-only to active enforcement
sed -i 's/SecRuleEngine DetectionOnly/SecRuleEngine On/' /etc/nginx/modsec/modsecurity.conf

You can also open the file in a text editor (like nano or vim) to tweak settings based on your specific use case.

内容的提问来源于stack exchange，提问作者Yearmaz