Hetzner Internal Network

[gitekDev]

Hello,

It would be nice to use Hetzner's internal network to communicate between servers.
For example a DB Server can communicate internal between Server A and Server C for example and Coolify Server.

Thanks

gitek

[maietta]

Correct me if I'm wrong, but I believe that would be outside the scope of this project.

[gitekDev]

Hey @maietta

I used Ploi before. There I was able to add an internal IP address to the respective server.

As an example, with a Wordpress installation I was able to use the internal IP address for the database connection.
I think there are some scenarios to use only internal IP connection.

[djsisson]

you can already do this,

when adding servers, use the internal network ip

then either map containers to internal ip:port

e.g you set hetzner internal network range to be 10.0.0.0/24 with ip 10.0.0.2-10.0.0.4 for A B C
then on c you bind your db to 10.0.0.4:5432
on A and B you can access your db using 10.0.0.4:5432

or you switch to swarm mode, and set the default address pool from say 10.10.x.x
set a label for your db to only run on a specific node
then you can connect as usual providing they are in same docker overlay network, irrespective of which node they are running on

ps. the subet of 10.0.0.0 assumes the default docker subnet in use of 172.16 (currently coolify changes this on new installations)

[gitekDev]

Hey @djsisson
I'll try it tomorrow. Thanks for the information :=).