2.3 KiB
Troubleshooting
Logs
When troubleshooting, the logs are your best friends. We try our best to provide user-friendly logs to help you understand what happened. Please note that we don't store the logs inside the container, they are all displayed on stdout/stderr so Docker can capture them. They can be displayed using the docker logs command.
You can edit the LOG_LEVEL
environment variable to increase or decrease the verbosity of logs with the following values : debug
, info
, notice
, warn
, error
, crit
, alert
or emerg
(with debug
being the most verbose level).
Permissions
Don't forget that bunkerized-nginx runs as an unprivileged user with UID/GID 101. Double check the permissions of files and folders for each volumes (see the volumes list).
ModSecurity
The OWASP Core Rule Set can sometimes leads to false positives. Here is what you can do :
- Check if your application has exclusions rules (e.g : wordpress, nextcloud, drupal, ...)
- Edit the matched rules to exclude some parameters, URIs, ...
- Remove the matched rules if editing it is too much a hassle
Some additional resources :
Bad behavior
The bad behavior feature comes with a set of status codes considered as "suspicious". You may need to tweak the corresponding list to avoid false positives within your application.
Whitelisting
It's a common case that a bot gets flagged as suspicious and can't access your website. Instead of disabling the corresponding security feature(s) we recommend a whitelisting approach. Here is a list of environment variables you can use :
WHITELIST_IP_LIST
WHITELIST_REVERSE_LIST
WHITELIST_URI
WHITELIST_USER_AGENT
More information here.