Re: failed to start the main proxy: java.net.bindexception address already in use - ZAP DOCKER

[Nicollas Teixeira]

it happens on softwaresecurityproject/zap-stable  image. If i use ghcr.io image im getting other selenium errors and cannot run scans

Em terça-feira, 26 de setembro de 2023 às 12:54:54 UTC-3, Nicollas Teixeira escreveu:

Hey guys, im facing this issue, i already tried to use -p 8090 command to change port but keep the same error and i cant run the scan

[phil young]

Concur, this has caused me head-scratching all this pm cos I thought I had changed my code/config...

docker run -u zap -p 8080:8080 -i softwaresecurityproject/zap-stable zap.sh -daemon -host 0.0.0.0 -port 8080 -config api.addrs.addr.name=.* -config api.addrs.addr.regex=true -config api.disablekey=true

33285 [ZAP-daemon] WARN  org.zaproxy.addon.network.ExtensionNetwork - Failed to start the main proxy: java.net.BindException Address already in use
33291 [ZAP-daemon] ERROR org.parosproxy.paros.CommandLine - Terminating ZAP, unable to start the main proxy.
38026 [ZAP-daemon] INFO  org.zaproxy.zap.DaemonBootstrap - OWASP ZAP 2.13.0 terminated.

But with :
docker run -u zap -p 8080:8080 -i owasp/zap2docker-stable zap.sh -daemon -host 0.0.0.0 -port 8080 -config api.addrs.addr.name=.* -config api.addrs.addr.regex=true -config api.disablekey=true
30257 [ZAP-daemon] INFO  org.zaproxy.addon.network.ExtensionNetwork - ZAP is now listening on 0.0.0.0:8080

[thc...@gmail.com]

Hi,

This issue is fixed with the latest version of Network add-on.

Best regards.