-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File Screenshot Errors #199
Comments
Potentially a bug?Errors 1 & 3As mentioned in the OP, running
If I run the following one liner, GoWitness will complete successfully without an issue. cat "../subd.txt" | while read line; do gowitness single -X 2560 -Y 1440 -F "http://$line"; done Given this, I believe there is some sort of bug. Of course I can just use this in general, but that defeats the purpose of the If there is anything else I can provide to hopefully get this resolved, I am more than happy to do so. Error 2I only get this on one subdomain out of the list of 13. When going to the same URL in my browser, I am given the following error: This tells me that the second error is server-side, and therefore not legitimate to this issue any more. |
Thanks, the extra information is useful. As a hypothesis on what's going on, I have two things in mind to test (without knowing your targets):
|
Thanks for the reply. It seems that those two suggestions together work. I did attempt Based on your hypothesis I thought I would change the order and see if that could be the case using the original command and they still spat out errors. Is there anything I can look for with the issue subdomains when loading it in my browser or maybe curl to see why? If preferable, I can provide you with the target if it makes it less tedious to figure it out. Thank you! |
Think the bigger thing here is that an error is not necessarily a bad thing. It's really just telling you it couldn't screenshot (or preflight) the remote end and will move on to the next target. Specifying the full URL is preferred to prevent gowitness from trying to find something that might not exist to begin with. On the fallback idea, this is something I have planned for the v3 release. |
Understood. Because I had the time, I was able to set everything up on my PC and it seems Considering that fact and that |
Command
gowitness file -X 2560 -Y 1440 -F -f "subd.txt"
Errors
ERR failed to witness url error="context deadline exceeded" url=http://api.DOMAIN.com
ERR failed to witness url error="Get \"https://draft.usecollect.com\": remote error: tls: handshake failure" url=https://draft.DOMAIN.com
ERR failed to witness url error="could not retrieve attribute \"outerHTML\": No node with given id found (-32000)" url=https://app.DOMAIN.com
More Info
I have a file of 13 subdomains. The format is just
sub.domain.com
. Only 8 of the subdomains worked. Theapi.DOMAIN.com
subdomain has a prefetch status code of 200, however I am given the first error above. The problem is if I run a single run on the same subdomain, it has zero issues and it is able to get the image.Errors 1 and 3, I am able to get screenshots using the following:
gowitness single -X 2560 -Y 1440 -F http://SUB.DOMAIN.com
. I am unsure as to how I can get Error 2 to work.Expectations
When running the original command above, it is expected that all subdomains are checked. If prefetch is successful, a screenshot should be taken assuming the Response Code is 2XX/3XX/4XX.
The text was updated successfully, but these errors were encountered: