The Amass engine did not respond: the Amass engine did not respond within the timeout period

[QiWan777]

An error is reported every time it is used: The Amass engine did not respond: the Amass engine did not respond within the timeout period

[gioFasta]

@QiWan777 what type of build you using? if you use amass-docker-compose, with compose.yaml change branch enum from develop to master and it works

[PurpleLinux]

@gioFasta I've tried compiling from scratch, the regular go install, and using the latest (v5.0.1) docker image and I keep getting The Amass engine did not respond: the Amass engine did not respond within the timeout period. It happens when I run enum, and once it happens once it seems to shut the whole thing down. So enum -h runs. Then I try to do enum -d domain.domainface, get The Amass engine did not respond: the Amass engine did not respond within the timeout period, and now enum -h won't run at all.

The only clue that might be a false lead is in the engine logs in .config/amass, it seems that the last thing that gets run before it chokes is "plugin started ... Aviato" and in the enumeration run that killed it "plugin started ... Verified Email". I have no idea if this is related or not.

Whats even weirder is that if I wipe the docker image, download a new one, then run enum -h, it's still broken.

[PurpleLinux]

Something interesting with this issue, I think it's a networking problem. When I first ran this i was having problems on a NAT'd VM. Then on a linux box connected to a VPN. Disconnected the VPN and then it worked again.

[s7x]

Can confirm that amass is behaving really strangely with VPN connections. Can also confirm the amass enum -h command is timing out when connected to a VPN.

Tested on amass Version 5.1.1.