Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
In os-OPNWAF (OPNsense Business Version 25.10.2), custom error documents cannot be accessed due to a permission denied error. The error log shows that access to custom error documents is denied because search permissions are missing on the path.
The issue occurs because the uploaded custom error document directory (/usr/local/opnsense/data/OPNWAF/errors/[UUID]/) has incorrect permissions (drwxr-x---) compared to the default directory (drwxr-xr-x), preventing Apache from accessing the files.
To Reproduce
Steps to reproduce the behavior:
- Go to os-OPNWAF → Error Documents
- Download the default error documents
- Edit the files and save them as a ZIP archive
- Upload the modified ZIP file through the web interface
- Test web protection "/?id=100 or 'x'='y'"
Relevant log files
[core\:error] (13)Permission denied: [client x.x.x.x:49609] AH00035: access to /__waf_errors__/403.html denied (filesystem path '/usr/local/opnsense/data/OPNWAF/errors/[UUID]/403.html') because search permissions are missing on a component of the path.
Workaround:
The issue can be resolved by manually setting the correct permissions:
chmod 755 /usr/local/opnsense/data/OPNWAF/errors/[UUID]/
chmod 644 /usr/local/opnsense/data/OPNWAF/errors/[UUID]/*
Environment
- OPNsense 25.10.2 (Business Edition)
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
In os-OPNWAF (OPNsense Business Version 25.10.2), custom error documents cannot be accessed due to a permission denied error. The error log shows that access to custom error documents is denied because search permissions are missing on the path.
The issue occurs because the uploaded custom error document directory (
/usr/local/opnsense/data/OPNWAF/errors/[UUID]/) has incorrect permissions (drwxr-x---) compared to the default directory (drwxr-xr-x), preventing Apache from accessing the files.To Reproduce
Steps to reproduce the behavior:
Relevant log files
Workaround:
The issue can be resolved by manually setting the correct permissions:
chmod 755 /usr/local/opnsense/data/OPNWAF/errors/[UUID]/ chmod 644 /usr/local/opnsense/data/OPNWAF/errors/[UUID]/*Environment