Scan via TOR stuck on Starting

[alphaDev23]

I pulled the master branch yesterday and rebuilt Dockerfile.full. Version is 4.0.0. I changed the settings to TOR, 127.0.0.1, and 9050 for SOCKS Server Type, SOCKS Server IP Address, and SOCKS Server TCP Port, respectively. From within the container (network_mode set to "host"), TOR is listening on 127.0.0.1:9050. However, the scan is stuck on "starting." The last logs are below. Please advise.

2023-01-23 03:47:01	sflib	STATUS	Downloading configuration data from: https://publicsuffix.org/list/effective_tld_names.dat
2023-01-23 03:47:01	sflib	DEBUG	Using proxy: socks5h://127.0.0.1:9050

[alphaDev23]

Any thoughts on the above?

[bcoles]

I wasn't able to reproduce this issue outside of Docker.

2023-01-31 22:57:30,900 [INFO] sfwebui : Waiting for the scan to initialize...
2023-01-31 22:57:31,024 [DEBUG] sflib : Using proxy: socks5h://127.0.0.1:9050
2023-01-31 22:57:31,025 [INFO] sflib : Downloading configuration data from: https://publicsuffix.org/list/effective_tld_names.dat
2023-01-31 22:57:35,009 [INFO] sflib : Scan [7E4E0853] for 'example.com' initiated.

[alphaDev23]

It is working now. I believe that if you change the SOCKS proxy after a scan is created/ran and then re-run the scan, it will remain stuck in "Starting." I created the same scan with the SOCKS proxy set prior to its creation and it now runs without issue.