Why ExtraHosts in Docker pushed as `172.18.0.1`?

[potemkin_ai]

if (manifest.id !== 'com.adguard.home.cloudronapp') containerOptions.HostConfig.ExtraHosts.push(`${dashboardFqdn}:172.18.0.1`);

in docker.js:698 you have the code from below - I understand you are trying to work around the cases, when my.domain.com is defined via /etc/hosts to be something weird.

But why don't you push the public IP address?

In my specific case, Cloudron is behind a kind of WAF and that WAF is taking care on the SSL certificates, so any connections to 172.18.0.1 are just failing due to SSL issues (and Synapse, for example, can't start due to OIDC issue).

And a question/ask: can you change that to the Cloudron IP please? It shouldn't be difficult, as you it as a variable already.

[potemkin_ai]

or, could you just make it optional?

In my specific case I just commented out the string to let the apps running.

[james]

Hello @potemkin_ai
172.18.0.1 is the CLOUDRON_PROXY_IP.
Normally all connections to 172.18.0.1 should be internal, so I am a little confused why WAF would interfere here.

[potemkin_ai]

Yeah, I know what that IP is

WAF -> nginx -> cloudron apps

So, if WAF manages the SSL, connection to nginx will fail