Reporting Bugs
Occasionally something breaks that I can't foresee. That's why you're here! Follow the instructions below to gather as much information as you can for a bug report.
FiercePhish v1.2.0 and later provides you with a log export feature under "Settings" --> "Logs". Click "Download Logs" and attach them to your GitHub Issue.
Otherwise, these are the most important logs:
- Laravel.log, by default stored in
/var/www/fiercephish/storage/logs/laravel.log - Apache log, by default stored in
/var/log/apache2/error.log - Postfix log, by default stored in
/var/log/mail.log
If you are having problems with the automated install, you can either set "VERBOSE=true" for method #1 or run ./install.sh -v for method #2.
Once you have verbose enabled, redirect the output to a file (and give me the log file):
-
For method #1:
curl https://github.com/Raikia/FiercePhish/blob/master/install.sh | bash | tee log_file.txt -
For method #2:
./install.sh -v | tee log_file.txt
Screenshots of the bug are hugely helpful, as are reproduction steps. You can even set "DEBUG" mode on, both via the web interface ("Settings" --> "Configurations" --> "Application Debugging"), or via the configuration file (by default located in "/var/www/fiercephish/.env") (set "DEBUG=true", then run "php artisan config:cache").
Bug reports are only as useful as the amount of information provided. The more you provide, the faster I can fix the bug to get a fix out to you!
Once you have all the information above, go to Github Issues, click "New Issue", and put all the information together in there.