Update port listening from '0.0.0.0' to '::'

[icepcp]

Docker does not necessarily use IPv6 for the internal network by default, which allows for listening on IPv4 addresses. Hosting on external platforms, like Fly, where its internal network is strictly IPv6, leads to errors when trying to use TrafficAnalytics. Updating the port to be listening on :: would solve this issue

---

Note

Change server listen host to IPv6 :: instead of IPv4 0.0.0.0.

^{Written by Cursor Bugbot for commit 682fd21. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: IPv6-Only Bind Breaks IPv4-Only Environments

Changing the listen host from '0.0.0.0' to '::' breaks compatibility with IPv4-only systems and environments without IPv6 support. While '::' works on IPv6-enabled systems (and often accepts IPv4 connections via IPv4-mapped IPv6 addresses on dual-stack systems), it will fail on systems where IPv6 is disabled or not supported, making the application unable to start in those environments. This is a breaking change that trades fixing IPv6-only platforms (like Fly) at the cost of breaking IPv4-only deployments.

 

[icepcp]

I did not realise it would break on non-IPv6 environments, my apologies, I guess there could be an env var set to enable IPv6 support

[cmraible]

Thanks @icepcp — I'd welcome a PR that uses an environment variable for the host 👍

[cmraible]

Thanks for the contribution!

To avoid any potential breaking changes, we should make this configurable via an environment variable, and default to the current '0.0.0.0'. Happy to take another look if you want to update this PR to use the environment variable.