Network requirements

Black Duck requires the following ports to be externally accessible:

  • Port 443 – Web server HTTPS port for Black Duck via NGiNX

  • Port 55436 – Read-only database port from PostgreSQL for reporting

If your corporate security policy requires registration of specific URLs, connectivity from your Black Duck installation to Black Duck Software hosted servers is limited to communications via HTTPS/TCP on port 443 with the following servers:

  • updates.suite.blackducksoftware.com (to register your software)

  • kb.blackducksoftware.com (access Black Duck KB data)

  • https://auth.docker.io/token?scope=repository/blackducksoftware/blackduckregistration/pull&service=registry.docker.io (access to Docker Registry)

  • data.reversinglabs.com and api.reversinglabs.com (if ReversingLabs scanning is enabled)

Note: If you are using a network proxy, these URLs must be configured as destinations in your proxy configuration.

Ensure that the following addresses are on the allow list:

  • kb.blackducksoftware.com
    • 35.224.73.200
    • 35.242.234.51
    • 35.220.236.106

  • updates.suite.blackducksoftware.com

  • repo.blackduck.com

    • 34.110.245.127

  • hub.docker.com

  • production.cloudflare.docker.com
    • 103.21.244.0/22
    • 103.22.200.0/22
    • 103.31.4.0/22
    • 104.16.0.0/13
    • 104.24.0.0/14
    • 108.162.192.0/18
    • 131.0.72.0/22
    • 141.101.64.0/18
    • 162.158.0.0/15
    • 172.64.0.0/13
    • 173.245.48.0/20
    • 188.114.96.0/20
    • 190.93.240.0/20
    • 197.234.240.0/22
    • 198.41.128.0/17

  • registry-1.docker.io

  • auth.docker.io

  • github.com

  • docker.io

Verifying connectivity

To verify connectivity, use the cURL command as shown in the following example.

curl -v https://kb.blackducksoftware.com
Tip: It's good to check connectivity on the Docker host but it's better to verify the connectivity from within your Docker network.

IPv4 and IPv6 networks

Black Duck supports IPv4 and IPv6 for ingress and egress traffic. However, the internal Black Duck container network requires IPv4 to function properly. Specifically, Black Duck can handle IPv6 for inbound and outbound network traffic from the Black Duck container cluster to NGiNX, but internal traffic within the cluster must use IPv4.