[Feature] Application Installation Should Support Custom IP Binding and Persistent Container Network Configuration

[transnull]

1Panel Version

v1.10.24-lts

Please describe your needs or suggestions for improvements

Problem Description:
When installing applications via 1Panel, containers are bound to the 0.0.0.0 IP address by default, allowing external users to directly access applications via server-ip:port. Some users (e.g., those using Nginx reverse proxy setups) prefer to restrict access exclusively through the proxy, which currently requires manual adjustment of container network configurations. Additionally, when an application is reinstalled or updated after deletion, the container's IP address changes, causing Nginx reverse proxy configurations to break.

Proposed Solutions:

1. Custom IP Binding: Add a "Bind IP" option in the application installation interface (e.g., defaulting to 127.18.0.1 or allowing custom values) to prevent direct external access.

Please describe the solution you suggest

No response

Additional Information

No response

[wanghe-fit2cloud]

Thank you for the feedback. We will consider supporting this request in a future version.