[Bug Report] CubeEgress nginx.conf listen IP not updated when using custom CUBE_SANDBOX_NETWORK_CIDR

[Yousri]

Summary

CubeEgress nginx.conf listen IP not updated when using custom CUBE_SANDBOX_NETWORK_CIDR

Environment

• CubeSandbox version / commit: v0.5.0-amd64
• Host OS and kernel version: ubuntu24.04

Steps to Reproduce

Core issue:

• After installing with CUBE_SANDBOX_NETWORK_CIDR=10.100.0.0/18, the cube-dev gateway IP becomes 10.100.0.1.
• However, the nginx.conf inside the CubeEgress container still listens on 192.168.0.1:8080 and 192.168.0.1:8443.
• The TPROXY rules use --on-ip 10.100.0.1, which no longer matches the Nginx listen address, resulting in a configuration mismatch.

Suggestion:

During installation, install.sh should detect the configured CUBE_SANDBOX_NETWORK_CIDR and render the corresponding gateway IP into the CubeEgress nginx.conf. Alternatively, the gateway IP could be passed as an environment variable, with the container updating nginx.conf via sed (or a similar templating mechanism) during startup. This would ensure that the Nginx listen address always stays in sync with the configured sandbox network CIDR.

[Yousri]

I'd also like to add one more observation:

• The TPROXY rules were not updated either—they still point to 192.168.0.1:8080/8443 instead of the gateway IP derived from the configured CIDR. ❌
• From what I can tell, this is likely because the default .one-click.env does not define a CUBE_TPROXY_ON_IP variable. As a result, the installation process appears to fall back to the default value of 192.168.0.1 instead of using the gateway IP corresponding to CUBE_SANDBOX_NETWORK_CIDR.

It would probably make sense for CUBE_TPROXY_ON_IP to be automatically derived from CUBE_SANDBOX_NETWORK_CIDR during installation (or generated if not explicitly provided), ensuring that the TPROXY configuration, Nginx configuration, and sandbox network CIDR always remain consistent.

[chenhengqi]

Fixed in #851.