[error]ENOENT: no such file or directory, open '/home/vsts/work/r1/a/owaspzap/report.json' #11
Comments
|
Looks like the real error is the one before it and that it can't access the target URL. Is this an intranet site? is this running a non-microsoft hosted agent? Is it accessible from the agent? I/O error(5): ZAP failed to access: http://172.17.0.1:8080 The file doesn't exist because the scan never ran. |
|
okay, that was fixed and now bumped into| 2020-08-28T09:02:01.0726910Z ##[warning]Failed to read /home/vsts/work/r1/a/owaspzap/test-results.xml. Error : There are multiple root elements. Line 49, position 2.. |
|
I started getting this yesterday when I changed the target website. Looking at the file, it includes both the HTTP and HTTPS runs. I looked at the settings and the site requires HTTPS so it is redirecting the call from HTTP to HTTPS and OWASP thinks it is two different websites. In the report parser that I wrote, I passed in the target site so it would only report on that one site. I think we need to do this here or just use HTTPS when doing the testing. The weird thing is if I change it to HTTPS, I don't get any warnings even though I did before and the JSON report shows port 80. Seems like a different issue.
|
|
I looked back at the settings and there is a port setting. It must default to port 80. I wish it would use the default HTTP port of the URL. I set this explicitly like below and now everything works properly.
|
|
now bumped into another issue, scanner just frozes after, in azure pipeline but works fine on the seperate run |
|
Hi @IvanKirianov, not sure what issue are you facing now but now it just hung after i even tried in other servers as well. |
|
These issues do not necessarily pertain to the Azure DevOps ZAP plugin created by this team. What's not immediately clear from the plugin is that it mostly relies on the ZAP Docker container. The plugin merely takes a few settings from you and applies them to ZAP running in Docker. One such example is the port number that @mikedouglasdev referred to. If your issues continue to exist, please provide an update @pragadeeshraju. Otherwise, please consider closing this issue. |
|
I nedd help please |
|
in my case, i had the SSL port specified correctly for an HTTPS only web app. but, it was failing when using a pipeline variable. the error went away once putting the URL directly in |
|
How did you fix initial issue? I am also getting the same issue in yml based pipeline. But in classic mode. pipeline:-
Error:- |
|
Did you find a solution for the rror ? |
|
Hi All, While executing the OWASP ZAP scan in the azure pipeline for the "targeted scan" type, getting below error, Any solution for this issue.
Earliest response is much appreciated , Since because of this we have blocked with few releases. |
I was trying the use ZAP from Azure market place and getting bumped into the error.
any help would be appreciated.
let me know if more information are needed
The text was updated successfully, but these errors were encountered: