Steve Micallef

This issue appears to be caused by something else occupying the port you've chosen to use for SpiderFoot. Check `netstat` to see what else might be listening on port 5001....

Just curious, when you run that, is another `sf.py` already running on the machine?

Are you able to check and share the logs in `$HOME/.spiderfoot/logs/spiderfoot.debug.log` to see what was happening before the freeze?

Could you check that SpiderFoot is not running already? The database might be locked by that process.

Interesting idea - what would be the seed event in such a module to trigger its search?

Since a discord URL cannot be provided as a scan target in SpiderFoot, this discord server URL would come from the target website (for example), so that would work. What...

I can't reproduce this. Are you definitely using the latest version? Could you share the contents of both files and the version of docker you're using?

Are you using the latest version of SpiderFoot from the master branch? Please also ensure you kill any running `spiderfoot` container, build, and then run the `docker-compose`: 1. `docker ps`...

I'm wondering if this issue is specific to Windows. Have you been able to try this on a non-Windows system?

Thanks for the submission! One question: how does this provide value over the `outlier_webserver` rule? I think this might be prone to be quite noisy since it's looking at the...