- Check that the
crackerjack
service is running using:sudo systemctl status crackerjack
orps -aux | grep crackerjack
(you should see 4 workers).
- Check that apache/nginx are running, and have a look at their log files in
/var/log
- Check that the whole
/crackerjack
directory is owned by thewww-data
user (or whichever user is running your web server). - If it's still not working, create a new issue in the repo.
- Login to your server via SSH
- Switch to the www-data user (or whichever user is running your web server)
- Run
screen -ls
- Screen names have the following format:
USERID_USERNAME_RANDOMSEED_SESSIONID
- Which means if your session URL is
/sessions/4/view
and your username isadmin
, the screen name will be:SOMEID_admin_XXXX_4
- Which means if your session URL is
- Attach to the screen using
screen -r SCREEN_NAME
- Click the
start
button via the GUI and check if that screen instance is receiving the command and check its output. - Make sure that the user that's running the web server has a
.hashcat
directory in their home directory, for example/var/www/.hashcat
- Check that the crontab has been installed.
- Login as the
www-data
(or equivalent) user, and runcrontab -l
.
- Login as the
- Make sure you are not using self-signed certificates, use LetsEncrypt.
- Check the
syslog
.
- Check that the crontab has been installed.
- Login as the
www-data
(or equivalent) user, and runcrontab -l
.
- Login as the
- Check the
syslog
.