Nginx 504 gateway timeout

[markland556]

Have been trying to troubleshoot to the best of my abilities with no luck. Fresh docker container built and always get 504 bad gateway. Seems like it can not connect to gunicorn web service. Not sure what to try next.

2022-11-07 02:00:33,036 CRIT Supervisor running as root (no user in config file)
2022-11-07 02:00:33,036 INFO Included extra file "/etc/supervisor/conf.d/hashcat_wpa.conf" during parsing
2022-11-07 02:00:33,063 INFO RPC interface 'supervisor' initialized
2022-11-07 02:00:33,063 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-11-07 02:00:33,064 INFO supervisord started with pid 7
2022-11-07 02:00:34,071 INFO spawned: 'nginx' with pid 10
2022-11-07 02:00:34,076 INFO spawned: 'gunicorn' with pid 11
2022-11-07 02:00:34,081 INFO spawned: 'hashcat-brain' with pid 12
2022-11-07 02:00:34,106 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-11-07 02:00:35,630 INFO success: hashcat-brain entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-11-07 02:00:36,632 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)

[dizcza]

Please share the content of the following files:

• /root/hashcat-wpa-server/logs/supervisor/nginx_stdout.log
• /root/hashcat-wpa-server/logs/supervisor/nginx_stderr.log
• /root/hashcat-wpa-server/logs/supervisor/gunicorn_stdout.log
• /root/hashcat-wpa-server/logs/supervisor/gunicorn_stderr.log

[markland556]

nginx_stdout.log -Empty
nginx_stderr.log - Empty
gunicorn_stdout.log - Empty
gunicorn_stderr.log :

[2022-11-07 14:29:54 +0000] [11] [CRITICAL] WORKER TIMEOUT (pid:2953)
[2022-11-07 14:29:54 +0000] [2953] [INFO] Worker exiting (pid: 2953)
[2022-11-07 14:29:55 +0000] [2957] [INFO] Booting worker with pid: 2957
[2022-11-07 14:30:25 +0000] [11] [CRITICAL] WORKER TIMEOUT (pid:2957)
[2022-11-07 14:30:25 +0000] [2957] [INFO] Worker exiting (pid: 2957)
[2022-11-07 14:30:25 +0000] [2961] [INFO] Booting worker with pid: 2961
[2022-11-07 14:30:55 +0000] [11] [CRITICAL] WORKER TIMEOUT (pid:2961)
[2022-11-07 14:30:55 +0000] [2961] [INFO] Worker exiting (pid: 2961)
[2022-11-07 14:30:55 +0000] [2965] [INFO] Booting worker with pid: 2965
[2022-11-07 14:31:26 +0000] [11] [CRITICAL] WORKER TIMEOUT (pid:2965)
[2022-11-07 14:31:26 +0000] [2965] [INFO] Worker exiting (pid: 2965)
[2022-11-07 14:31:26 +0000] [2968] [INFO] Booting worker with

[dizcza]

All right, so the workers are killed as soon as they are spawned by gunicorn. It doesn't tell us why though.

I noticed that the Dockerfile is outdated (in 3 months, gosh) and yet another apt package has been removed/changed/etc. So I need to invest time into the issue.

In the meanwhile, consider creating a separate Python env locally (on host), running pip install -r requirements.txt and then launching gunicorn from the project root directory:

gunicorn app:app --bind localhost:8000

Navigate to localhost:8000.

Consider also a command line interface described in Readme.

[dizcza]

Sorry for taking this so long. I've been occupied by survival tasks.

I've made a fix, available on master (a few hours and will be available on the Dockerhub as well).

Please check if this works for you. I've tested the docker images locally.

Feel free to reopen the issue if the problem still persists.

[markland556]

The same issue remains.

[dizcza]

@markland556 please tell me the branch (tag) you're using. Is it the latest or pocl?

[markland556]

EDIT: Sorry, Using latest

[dizcza]

Malformed response.

Write again.

[markland556]

Using Latest

[dizcza]

Are you sure you've updated the dizcza/hashcat-wpa-server:latest from the Dockerhub repository? You can simply check the python version:

• if it's 3.9, you're using the old image
• if it's 3.8, you've updated the image to the most recent one (I've downgraded the python version)

[dizcza]

And also I assume you have a GPU on the machine from which you start the dizcza/hashcat-wpa-server:latest image. It won't work for machines without GPUs.

[dizcza]

Please check if other branches (tags) work for you:

• dizcza/hashcat-wpa-server:intel-cpu will work on your PC or laptop but will probably not work on cloud services
• dizcza/hashcat-wpa-server:pocl should work on any machine

[markland556]

Verified Python version is 3.8 for gpu version. Tried both cpu and pocl version with same 504 gateway issue.

[dizcza]

Are you launching the docker image on your host machine or on web services like AWS?

[markland556]

This is docker running on a Ubuntu VM on a Proxmox hypervisor. It worked at one point in the past, But i think everything was redone at some point and havent had it working since.
Even in the Ubuntu VM if i go to localhost:9111 is still gives the same error.