Latest stable Arachni Web UI does not work on Linux 64 bit
Hi, I tried to run latest stable Arachni 1.4 on my Arch Linux.
When I run
./arachni_web the server starts, but I can not connect on
localhost:9292. It simply sits and does nothing.
When I try
./arachni_web -s webrick I can connect, but it fails when I try to
log in. I am attaching a output of Webrick server when it fails.
Thin and Mongrel even don't start, they simply crash. I can provide
more output if you wish.
I am running 64 bit version of Arachni for Linux on my 64 bit Arch
Linux. I tried it with latest stable version and also with nightly
version. If you need more information, just ask me and I will try
to send it to you.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Tasos Laskos on 22 Feb, 2016 09:03 AM
Hello,
I'm pretty sure it does work, although I don't know what the problem might be in your case.
Also, I'm not seeing anything attached to this discussion.
Cheers
2 Posted by Vojta on 22 Feb, 2016 09:30 AM
Okay, I am sending it here. This is output of running web UI with Thin, Webrick and Mongrel. Puma simply sits and does nothing. The Webrick error occurs after I try to log in with a valid user account.
Support Staff 3 Posted by Tasos Laskos on 22 Feb, 2016 09:36 AM
Unfortunately these don't help much, Puma is the bundled server so is there anything interesting (or anything at all) printed when just running
arachni_web?4 Posted by Vojta on 22 Feb, 2016 11:41 AM
Here is the ebugging output when just starting it. If I try to visit http://localhost:9292, it does nothing.
Support Staff 5 Posted by Tasos Laskos on 22 Feb, 2016 11:45 AM
Everything looks normal, can you please show me the output of:
6 Posted by Vojta on 22 Feb, 2016 11:48 AM
It just sits and does nothing. Here is the output in a file, I hope it helps.
Support Staff 7 Posted by Tasos Laskos on 22 Feb, 2016 11:51 AM
I meant the out of the
curlcommand after you've startedarachni_web.8 Posted by Vojta on 22 Feb, 2016 11:55 AM
There is no output. It simply waits and waits for several minutes. And when I do a Nmap scan of localhost, the port is shown as closed.
Support Staff 9 Posted by Tasos Laskos on 22 Feb, 2016 12:04 PM
I don't think that's actually possible, that curl command would have printed something even before it tried to connect.
Another thing you can try is:
And try to connect to http://127.0.0.1/ .
10 Posted by Vojta on 22 Feb, 2016 12:18 PM
Thanks, now it works.
Support Staff 11 Posted by Tasos Laskos on 22 Feb, 2016 01:04 PM
Glad to hear that. :)
Tasos Laskos closed this discussion on 22 Feb, 2016 01:04 PM.