Add: IPv6-only support => Update docker/nginx-unit.json

[MikuuW]

Related Issue: N/A

New Behavior

We have noticed that since the release of Netbox v4.2.0. Our deployments stopped working in a pure IPv6 environment. After some troubleshooting we've found this PR where the nginx interface bindings have been changed. After overwriting docker/nginx-unit.json, our netbox was up and running again.

Contrast to Current Behavior

Bind IPv6 interfaces too

Discussion: Benefits and Drawbacks

Something like this would be a much nicer solution.

  "listeners": {
        "*:8080": {
          "pass": "routes/main",
          "forwarded": {
            "client_ip": "X-Forwarded-For",
            "protocol": "X-Forwarded-Proto",
            "source": [
              "10.0.0.0/8",
              "172.16.0.0/12",
              "192.168.0.0/16",
              "fc00::/7",
              "fe80::/10"
            ]
          }
        },
        "*:8081": {
          "pass": "routes/status",
          "forwarded": {
            "client_ip": "X-Forwarded-For",
            "protocol": "X-Forwarded-Proto",
            "source": [
              "10.0.0.0/8",
              "172.16.0.0/12",
              "192.168.0.0/16",
              "fc00::/7",
              "fe80::/10"
            ]
          }
        }
      }

But did not get it to work with the wildcard (but were not nginx experts).
Not explicitly tested in IPv4 environments.

Double Check

• I have read the comments and followed the PR template.
• I have explained my PR according to the information in the comments.
• My PR targets the develop branch.