Unable to export logged vectors from Proxy plugin
I'm in the process of testing out the proxy plugin, and have run into an issue exporting the logged vectors.
The error message is:
Service Unavailable
invalid byte sequence in US-ASCII
I noticed in the Discovered Elements several instances of:
"We're sorry, but something went wrong (500)..."
All are links to PNG and JPG files in the application.
Please assist.
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 20 Feb, 2016 09:34 AM
Hello,
Is there a backtrace printed somewhere?
Either in the browser or the console?
Cheers
2 Posted by Frank on 20 Feb, 2016 06:05 PM
Hello Tasos,
There was no backtrace in the browser. Just the HTML response I indicated:
Service Unavailable
invalid byte sequence in US-ASCII
If I run the curl command
I get the same HTML response in thevectors.yml
file.In the console for the proxy plugin, the only message indicated that it was exporting the vectors. No message of an error.
I was running the proxy with the default debug level of 1.
Support Staff 3 Posted by Tasos Laskos on 20 Feb, 2016 06:31 PM
It just dawned on me, you're not using the latest version right?
I don't think that error message would appear in 1.4.
4 Posted by Frank on 22 Feb, 2016 04:25 PM
Yes. This issue was with version 1.3.
When attempting to startup Arachni 1.4 with the proxy plugin, the scanner spawns 6 browsers and never connects to port 8282. I checked the ports via
ss -ant
and tried to POST a request through the proxy. I received a messagecurl: (7) Failed to connect to localhost port 8282: Connection refused
.Below is what is shown when executing the following command
Update: The proxy finally started connecting to port 8282 in version 1.4, and I was able to export the vectors.
Any insight on why the proxy couldn't connect?
Support Staff 5 Posted by Tasos Laskos on 22 Feb, 2016 04:50 PM
No idea, maybe it was an one time thing, I guess a random bind failure could happen.
Glad you got it working though.
Cheers
Tasos Laskos closed this discussion on 22 Feb, 2016 04:50 PM.