After upgrading the server from 0.12 to the latest master agent dies on start:
Successfully registered!
Collecting agent data...
Login successful!
Hashtopolis Server version: 0.14.2 (commit f4fc2b1)
Client is up-to-date!
File download header reported wrong status code: 404
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/root/hashtopolis.zip/__main__.py", line 377, in <module>
File "/root/hashtopolis.zip/__main__.py", line 167, in init
File "/root/hashtopolis.zip/htpclient/binarydownload.py", line 23, in run
File "/root/hashtopolis.zip/htpclient/binarydownload.py", line 81, in __check_utils
FileNotFoundError: [Errno 2] No such file or directory: '7zr'
7zr is available:
$ which 7zr
/usr/bin/7zr
But for some reason the agent tries to download it from the server, and the server responds 404:
I noticed that it looks for /hashtopolis/static/7zr.bin, and its the old path. The upgraded version has been deployed to the root and is being accessed as http://server:8081
Don't know how to proceed. Is it an issue in the migration because of changed path, or is it an agent's code's issue. And why does it need to download that binary if 7zr is available on the system?
Version Information
0.7.2
Hashcat
No response
Description
After upgrading the server from 0.12 to the latest master agent dies on start:
7zr
is available:But for some reason the agent tries to download it from the server, and the server responds 404:
I noticed that it looks for
/hashtopolis/static/7zr.bin
, and its the old path. The upgraded version has been deployed to the root and is being accessed ashttp://server:8081
Don't know how to proceed. Is it an issue in the migration because of changed path, or is it an agent's code's issue. And why does it need to download that binary if 7zr is available on the system?