Restricting ports to 80, 443, and > 1023 wasn't quite doing what we wanted because there's still restricted ports above 1024 (like 6000, which TJ ran into when randomly choosing a port).
Instead of limiting ports based on range, instead use Chrome/FF's restricted port list and don't allow those specifically.
Related to the issue here: https://gitlab.com/architect-io/architect-cli/-/issues/662 and an update of https://github.com/architect-team/architect-cli/pull/895.
Restricting ports to 80, 443, and > 1023 wasn't quite doing what we wanted because there's still restricted ports above 1024 (like 6000, which TJ ran into when randomly choosing a port).
Instead of limiting ports based on range, instead use Chrome/FF's restricted port list and don't allow those specifically.