Troubleshooting
This page contains troubleshooting information for all parts of FiercePhish. This should be your first stop if you are having issues. All known bugs will be put in this wiki page and solutions for them (if they exist).
If you make changes to ".env", make sure you run php artisan config:cache afterwards. This will solve a lot of problems you may have related to configurations.
If you look at ./storage/logs/laravel.log, you'll probably see "TokenMismatchException". Apparently there can be an issue if you are accessing the FiercePhish instance via an internal network. I recommend you try clearing your cookies and try again. If that doesn't work, try opening up the web port to the external Internet and try logging in like that (you can set the URL Prefix to hide the FiercePhish instance). If that works but the internal version does not, contact me so I can debug it further because I haven't been able to reproduce this issue
Lots of cheap VPSes have extremely limited RAM. While FiercePhish doesn't actively use a lot of memory, running a lot of the services it requires on one server can cause the server to constantly use roughly 500MB of RAM. Therefore, a VPS with 512MB of RAM is pretty close on the server requirements. However, you can use a swap file to solve this issue!
Create and enable a swapfile
A copy/pastable version of this is show below:
fallocate -l 2G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfileThis will enable the swapfile and you can see it in usage by running free -m. However, this will not stick after a server reboot.
To make the swapfile permanent
- Add
/swapfile none swap sw 0 0to "/etc/fstab"
Note: The installer can be rerun multiple times with no problems or configuration issues
CTRL+C (or CTRL+Z) the install to kill it. Rerun the installer in verbose mode to see all the output. Sometimes MySQL has issues installing and hangs on "Renaming removed key_buffer and myisam-recover options". This generally means you used an odd password for MySQL. If its a different problem, submit a Github issue with the log.
This generally means bower failed to install the front-end dependencies for some reason. This could mean you don't have enough RAM, but it could also just randomly fail. You can run the install again by running:
cd /var/www/fiercephish
bower install --force-root
If this still errors for you, you might try running bower cache clean and maybe even rm -r ~/.cache/bower.
If you forgot what the prefix that you set was, you will have to manually look at the configuration file on the server. Find the ".env" file (by default at "/var/www/fiercephish/.env") and look at the "URI_PREFIX" variable.
For example, if the .env file says: URI_PREFIX=this/is/it, browse to FiercePhish by going to http://domain.com/this/is/it/.
Sometimes this happens if the config files don't re-cache fast enough or if your APP_URL variable is not properly set. First, try to manually browse to what you set the prefix to. For example, if you set the prefix to: this/is/it, browse to http://domain.com/this/is/it/.
If that doesn't work, investigate the .env file (by default at "/var/www/fiercephish/.env"). Look at "URI_PREFIX" variable and use that as the prefix in your web browser. Lastly, change "URI_PREFIX" to "null" (URI_PREFIX=null) to get rid of the prefix and try again (if you update the ".env" file, make sure you then read this).
To prevent this from happening in the future, make sure "APP_URL" (or "Application URL" under "Settings"-->"Configuration") is set properly (either the publicly facing IP address or the domain name).
(This should be fixed as of Issue #11 being resolved. If it still persists, open a new Issue)
The easiest way to recover your instance if you forgot your username and/or password is just by making a new account. You can do this via commandline:
php artisan fp:createuser
After you create a new account, either modify your old one with a new password or delete it (or ignore it).
You can disable the 2FA authentication of a user with the following command:
php artisan fp:disable2fa