Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unable to add domains to certain docker compose services #4730

Open
Soulusions opened this issue Jan 3, 2025 · 2 comments
Open

[Bug]: Unable to add domains to certain docker compose services #4730

Soulusions opened this issue Jan 3, 2025 · 2 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@Soulusions
Copy link

Error Message and Logs

UI shows success, no errors in logs.

Steps to Reproduce

I have a docker compose file with several services, some services I can add domains to and visit with no issues, while other services will seemingly add the domain successfully, but refreshing the page causes it to disappear, and even without doing that, deploying doesn't actually inject the config into the docker compose file.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

Here is a slightly cut-down version of the docker compose file, with a service that works as expected and one that fails.

version: "3.1"

services:
  app: # This service can't use domains.
    image: app
    restart: unless-stopped
    build:
      context: .
      dockerfile: app/Dockerfile
    ports:
      - "4200:8080"
    environment:
      OTEL_EXPORTER_OTLP_ENDPOINT: "http://otel-collector:4317"
      OTEL_SERVICE_NAME: "app"
        
  seq: # This service is able to use domains fine!
    image: datalust/seq:2024.3
    restart: unless-stopped
    ports:
      - "8082:80"
    volumes:
      - seq:/data
    environment:
      ACCEPT_EULA: "Y"
      SEQ_FIRSTRUN_ADMINPASSWORDHASH: ${SEQ_FIRSTRUN_PASSWORDHASH}

volumes:
  seq:

I'm not using any custom advanced settings or anything on this application, I have just about everything bone-stock, which is why I'm surprised it's failing like this.

Only thing i see being the problem maybe is that the services causing issues seem to be the ones with a build step, but that's all I've got.

@Soulusions Soulusions added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 3, 2025
@dre-on
Copy link
Contributor

dre-on commented Jan 4, 2025

Looks like this is similar/same origin:
#4722

build: within compose file messes up domain configs?

@Soulusions
Copy link
Author

It's possible!
Though in my case, I tried recreating the application and it magically works again so I'm not sure what's up there...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants