aquatone icon indicating copy to clipboard operation
aquatone copied to clipboard

Aquatone V1.7.0 not creating screenshots

Open ginsa-todoroki opened this issue 5 years ago • 7 comments

Hello,

I am trying to get screenshots from an Amass list of subdomains but the result is nothing. It ends with

Requests:

  • Successful : 0

  • Failed : 0

  • 2xx : 0

  • 3xx : 0

  • 4xx : 0

  • 5xx : 0

I have aquatone the pre-compiled version installed in /usr/bin so no problems with the PATH I also have chromium installed but something not quite right.

Targets : 524 Threads : 1 Ports : 80, 443, 8000, 8080, 8443 Output dir : /root/Desktop/aquaton-res

Calculating page structures... done Clustering similar pages... done Generating HTML report... done

Writing session file...Time:

  • Started at : 2019-10-18T13:23:41-07:00
  • Finished at : 2019-10-18T13:28:15-07:00
  • Duration : 4m34s

Requests:

  • Successful : 0

  • Failed : 0

  • 2xx : 0

  • 3xx : 0

  • 4xx : 0

  • 5xx : 0

Screenshots:

  • Successful : 0
  • Failed : 0

ginsa-todoroki avatar Oct 18 '19 20:10 ginsa-todoroki

the same issue .. can you add the -debug flag and post the output ..i may help you !!

breaker01 avatar Oct 21 '19 22:10 breaker01

I have the same problem. i did using the -debug flag it is showing the following

   [agent:tcp_port_scanner] Port 443 is closed on site.com
   [agent:tcp_port_scanner] Port 8080 is closed on site.com
   [agent:tcp_port_scanner] Port 8443 is closed on site.com

please suggest a fix

Anugrahsr avatar May 02 '20 07:05 Anugrahsr

Just stop use proxy and all will fine.

brother0k avatar Jun 03 '20 22:06 brother0k

I have the same problem. i did using the -debug flag it is showing the following

   [agent:tcp_port_scanner] Port 443 is closed on site.com
   [agent:tcp_port_scanner] Port 8080 is closed on site.com
   [agent:tcp_port_scanner] Port 8443 is closed on site.com

please suggest a fix

same issue

raisulreyad avatar Aug 08 '20 09:08 raisulreyad

check the -scan-timeout option

sudoaza avatar Aug 28 '20 01:08 sudoaza

I have had the same issue. Change the -scan-timeout option from the default. The port scan times out and move on before it receives data back. I would also suggest to adjust according to your network speed, slower network speed, longer timeout period

epicpewpew avatar Feb 21 '21 19:02 epicpewpew

Same issue. Same debug info. Setting a longer -scan-timeout appears to fix it.

tperich avatar Oct 29 '21 08:10 tperich