...
The correct configuration of ModSecurity or suPHP with Revive Adserver will depend very much on your requirements. If you're finding that Revive Adserver is "broken", first try turning off ModSecurity/suPHP completely, and see if that fixes the issue. If so, you know what the issue is, and can look to update your configuration to meet your needs, while still allowing Revive Adserver to work.
Step 4: Check ACLs
If Revive Adserver is reporting that it cannot read/write to directories, but the permissions appear to be correct, please check to ensure that there are no additional security systems in place beyond simple file permissions that are preventing access. There are a number of different security systems which could be causing the issue, however, some examples that have been noted in the past to cause issues include:
- On Linux: SELinux.
Step 5: Disable Varnish Caching
There have been numerous reports of various things "not working" in Revive Adserver when Varnish is used as a delivery cache. Try disabling Varnish, and see if that fixes the issue.
Step
...
6: Check your Plugins
See:
Step
...
7: Check your Database
If you are using MySQL, use mysqlcheck to ensure that you do not have any corrupt database tables in your Revive Adserver database.
...
| Code Block |
|---|
[database] type=mysqli |
Step
...
8: Check your Log Files
Check both your Revive Aserver var/log/debug.log file and your web server's log file for error messages which may indicate issues with connecting to the database, or with an inability to access files.
...