tag:support.arachni-scanner.com,2012-07-01:/discussions/problems/5032-arachniArachni: Discussion 2018-05-04T09:15:50Ztag:support.arachni-scanner.com,2012-07-01:Comment/444772812018-01-10T06:30:38Z2018-01-10T06:32:46ZUnable to access Arachni GUI on browser<div><p>Hello Support,</p>
<p>I have setup arachni scanner on one of the AWS EC2 instance.<br>
After downloading and extracting of arachni tried to ran ./arachni_web with host IP but seems it is not working.</p>
<p>Please suggest what will be the fix on below.</p>
<p>[root@arachni bin]# ./arachni_web --host 52.65.3.246 Puma 2.14.0 starting...<br>
* Min threads: 0, max threads: 16 * Environment: development * Listening on tcp://52.65.3.246:9292 /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/puma-2.14.0/lib/puma/binder.rb:233:in <code>initialize': Cannot assign requested address - bind(2) for "52.65.3.246" port 9292 (Errno::EADDRNOTAVAIL) from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/puma-2.14.0/lib/puma/binder.rb:233:in</code>new' from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/puma-2.14.0/lib/puma/binder.rb:233:in <code>add_tcp_listener' from (eval):2:in</code>add_tcp_listener' from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/puma-2.14.0/lib/rack/handler/puma.rb:33:in <code>run' from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/rack-1.6.4/lib/rack/server.rb:286:in</code>start' from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/rack-1.6.4/lib/rack/server.rb:147:in <code>start' from /root/arachni/arachni-1.5.1-0.5.12/system/gems/gems/rack-1.6.4/bin/rackup:4:in</code>' from /root/arachni/arachni-1.5.1-0.5.12/bin/../system/gems/bin/rackup:22:in <code>load' from /root/arachni/arachni-1.5.1-0.5.12/bin/../system/gems/bin/rackup:22:in</code>' [root@arachni bin]#</p>
<p>Let me know if more information or any log on server is needed.</p>
<p>Regards,<br>
Smit Mehta</p></div>smit.mehtatag:support.arachni-scanner.com,2012-07-01:Comment/444772812018-05-04T09:15:47Z2018-05-04T09:15:47ZUnable to access Arachni GUI on browser<div><p>This is purely an env issue, you'll nee to talk with AWS support on how to configure the server for their env I think.</p></div>Tasos Laskos