Appendix
Troubleshooting
Lost password
If you’ve lost access to BlueRange’s system administrator account and you’re unable to reset your password using the configured email address, it is also possible to reset the password through the database. This procedure requires write access to the database server and BlueRange’s database on the database server.
Please try to reset your password using the "Forgot your password?" link before attempting the steps below. You should treat these steps as an option of last resort.
To reset the password, you’ll first have to connect to the database using the command line or a management tool. Then execute the SQL script that is appropriate for your database server.
Log files
BlueRange’s log files can be found in the "log" directory located underneath its installation directory. Logs are rotated automatically once a day and old log files are compressed to save space.
Docker
Because Docker containers are expected to be ephemeral, BlueRange does not write log files when run inside a container. To get logs from a running container use the docker logs
command.
We recommend to set up a logging infrastructure to ensure logs are properly collected and archived to help with troubleshooting in case of issues.
Linux
If BlueRange was installed in the default directory "/opt/bluerange" logs can be found in "/opt/bluerange/log". The most recent log file is called bluerange.log
, while archived log files are named bluerange.log.<date>.gz
. If BlueRange was installed in a different location, the log
directory is found relative to its installation directory.
Windows
If BlueRange was installed in the default directory "C:\Program Files{productSmall}" logs can be found in "C:\Program Files{productSmall}\log". The most recent log file is called bluerange.log
, while archived log files are named bluerange.log.<date>.gz
. If BlueRange was installed in a different location, the log
directory is found relative to its installation directory.
Security considerations
-
Do install the latest OS and software updates and security patches
-
Do use strong passwords for administrator accounts
-
Do use long passwords for service-to-service communication, these passwords don’t need to be used or remembered by humans
-
Do make sure the enterprise account used to access your LDAP has read-only access
-
Don’t create accounts with weak passwords like “password” or “test”
-
Don’t store passwords in files that are world readable.