Nginx 1.18.0. ModSecurity WAF installation ./configure error

3 min read 25-10-2024

the ifix

Nginx 1.18.0. ModSecurity WAF installation ./configure error

When attempting to install the ModSecurity Web Application Firewall (WAF) with Nginx 1.18.0, many users encounter a common hurdle: an error during the ./configure step. Understanding this issue and how to resolve it can help streamline your installation process, ensuring that your web server is secure and robust.

The Problem Scenario

While trying to install ModSecurity on Nginx 1.18.0, you may see an error message similar to this during the ./configure phase:

./configure: error: <specific error message>

This error often stems from missing dependencies, incorrect paths, or incompatible versions of libraries.

Analyzing the Issue

The installation process for ModSecurity requires certain libraries and dependencies to be present on your system. If these are not correctly installed or configured, the ./configure script will fail, and you’ll see an error message indicating the nature of the problem. Here are common errors and their resolutions:

Common Errors and Solutions

Missing Dependency Packages:
- Error Message: configure: error: required dependency XYZ not found
- Solution: Ensure that all the necessary libraries are installed. You can usually find these listed in the ModSecurity documentation. For most Linux distributions, you can install missing packages using package managers such as apt or yum.
```
sudo apt-get install -y build-essential libcurl4-openssl-dev libxml2-dev libyajl-dev
```
Incorrect Library Versions:
- Error Message: configure: error: Your version of XYZ is too old
- Solution: Update the libraries to the required version. Check the ModSecurity documentation to find the specific version needed.
Paths Issues:
- Error Message: configure: error: could not find XYZ
- Solution: Specify the correct paths during configuration. You can do this by using the --with-xyz option. For instance:
```
./configure --with-xyz=/path/to/library
```
Using the Wrong Nginx Source:
- Error Message: configure: error: Nginx version required is not found
- Solution: Make sure you are using the correct Nginx source files that are compatible with ModSecurity.

Steps to Install ModSecurity with Nginx 1.18.0

Here’s a practical guide to successfully install ModSecurity on Nginx:

Install Dependencies: Ensure that all required packages are installed. You might want to run:

sudo apt-get update
sudo apt-get install -y build-essential libcurl4-openssl-dev libxml2-dev libyajl-dev

Download Nginx and ModSecurity: Download the Nginx source code and ModSecurity. It’s important to download the appropriate versions.

wget http://nginx.org/download/nginx-1.18.0.tar.gz
tar -xzvf nginx-1.18.0.tar.gz
wget https://github.com/SpiderLabs/ModSecurity/releases/download/v3.0.4/modsecurity-3.0.4.tar.gz
tar -xzvf modsecurity-3.0.4.tar.gz

Compile ModSecurity: Change to the ModSecurity directory and run:
```
cd modsecurity-3.0.4
./build.sh
```

Configure Nginx with ModSecurity: Go to the Nginx directory and configure it with the ModSecurity module:

cd ../nginx-1.18.0
./configure --with-compat --add-dynamic-module=../modsecurity-3.0.4/nginx/modsecurity
make
sudo make install

Testing: After installation, test the Nginx configuration and start the server:
```
sudo nginx -t
sudo systemctl start nginx
```

Conclusion

Installing ModSecurity with Nginx 1.18.0 can present some challenges, especially during the ./configure step. However, by understanding the common issues and their solutions, you can navigate these problems effectively. Keeping your software and dependencies up to date is key to a successful installation and an enhanced security posture for your web applications.

Additional Resources

By following this guide, you can ensure that your Nginx installation is fortified with the ModSecurity WAF, providing enhanced security against various web threats. Happy configuring!