Description

When an explicit proxy is configured on an SRX Series device using TCP port 8080, the explicit proxy does not accept client connections and proxy traffic is not processed.

Symptoms

> show services web-proxy explicit-proxy statistics

Explicit Proxy :
    Active Explicit HTTPS proxy sessions       0
    Active Explicit HTTP proxy sessions        0
    Total Explicit HTTPS proxy sessions        0
    Total Explicit HTTP proxy sessions         0
    Sessions Dropped due to rate limit         0
    Listen port conflicts with system port     37

The Listen port conflicts with system port counter increases when the explicit proxy is configured to listen on port 8080.

Solution

TCP port 8080 is used by the Junos webapi-clear-text service. Because the port is already associated with a system service, configuring the explicit proxy to use the same port results in a system-port conflict. Consequently, the explicit proxy is unable to listen on port 8080.

 

Configure the explicit proxy to use another available random port that is not already assigned .

 

For example:

set services web-proxy explicit-proxy profile <explicit-proxy-profile-name> port <1025..65535>

Then verify the explicit proxy statistics:

> show services web-proxy explicit-proxy statistics

Modification History

2026-08-12 : Article Created