Allow fixed proxy IPs per destination and disabling the automatic network for Compose service stacks

[nuxwin]

Problem

I’m using Coolify 4.4.6 with its integrated Traefik proxy to deploy a Docker Compose service stack with explicitly defined networks and static container IPs.

I would like to control two aspects through Coolify:

1. The IP address assigned to Traefik on a destination network.
2. Which destination networks a service stack uses, with the ability to disable its automatically added UUID-named network.

1. Configure Traefik’s IP when creating a destination

When creating or editing a destination, please provide an optional static proxy IP address setting.
For example:

Destination network: atrium-ingress
Subnet:             10.203.0.0/24
Traefik IP:          10.203.0.2

Coolify would manage the corresponding proxy network attachment:

services:
  traefik:
    networks:
      atrium-ingress:
        ipv4_address: 10.203.0.2

Currently, I configure this manually in the proxy’s Compose configuration. A destination setting would make this configuration explicit and maintainable through Coolify.

The address should be validated against the network’s subnet and existing allocations.

2. Select destination networks without adding the automatic stack network

Please allow a Compose service stack to use selected destination networks and its explicitly declared private networks without automatically attaching every service to the UUID-named stack network.

For example, my Compose definition explicitly connects the frontend to:

networks:
  atrium-ingress:
    ipv4_address: 10.203.0.40
  identity-application:
    ipv4_address: 10.203.2.40

Coolify additionally generates an attachment such as:

networks:
  atrium-ingress:
    ipv4_address: 10.203.0.40
  identity-application:
    ipv4_address: 10.203.2.40
  qgfjgztd858z31irx9km3wr4: null

I would like an option to disable that last attachment and preserve the network memberships declared in Compose.
The UUID-named stack network is distinct from the shared Docker network named coolify. The request concerns disabling the automatically added stack network, not merely disabling attachment to the predefined destination network.

Why this matters

The stack separates public ingress, identity management and application traffic.

Adding a common network to every component introduces connectivity outside those intended boundaries. It can also create multiple shared network paths between services.

This matters when downstream services trust forwarded headers only from a proxy’s exact IP address. If a connection uses the additional network, its source address can differ from the configured trusted address.

We currently avoid that ambiguity by configuring private upstream destinations with static IPs instead of Docker service names.

Expected behavior

• An optional fixed Traefik IP can be configured per destination.
• Destination networks can be selected for a service stack.
• An explicit option disables the automatic UUID-named stack network.
• Per-service network memberships and static addresses declared in Compose are preserved.
• Generated Traefik network labels select the intended ingress network.
• Existing automatic networking remains available as the default behavior.

Environment

• Coolify: 4.4.6.
• Proxy: integrated Traefik.
• Deployment type: Docker Compose service stack.
• Custom Docker bridge networks with explicit subnets and static service IPs.

Thanks.