search

coollabsio / coolify

An open-source & self-hostable Heroku / Netlify / Vercel alternative.
https://coolify.io
Apache License 2.0
32.16k stars 1.67k forks source link

[Bug]: Traefik does not proxy services on another server in the same network #2968

Open cabaalexander opened 2 months ago

cabaalexander commented 2 months ago

Description

Context: I have my Coolify server on my network where I deploy my services, it is attached to a domain and static IP, and all is good so far. I have another machine that I want to use for deploying more services keeping my main server for controlling all.

I added the second server on my control server, it is pointing to my second server on the network ( 10.0.0.29 ) it is validated and when I deploy things to that server those services are built there with docker and I get the URL for the service but It seems that traefik cannot route to that machine + service.

Resolution/Expectation: If one deploys something to another server, once the service is finished deploying it resolves alright regarding IP on the network it is.

Minimal Reproduction (if possible, example repository)

  1. prepare two machines with Coolify, one master and the other non-master
  2. on your create another server on the master and configure it to point to the non-master machine
  3. create a service and when prompted to select a server, select the non-master server
  4. next deploy the service there and here you should have a link for that service

Here is the issue, the link for the service is not found because the service got created on the other machine (that has it's own traefix there)

The app is created on the second server but the URL I get is regarding the master server.

Exception or Error

Service example deployed on master: image

Traefik on master: image

Traefik on non-master: image

Version

v4.0.0-beta.319

Cloud?

cabaalexander commented 2 months ago

(Rephrasing what I intend here maybe this provides more context of what I want)

I have a server with coolify implemented, I want to configure a slave server for deploying applications there with the routing working for the main server