Skip to content

[Bug]: FQDN In Compose services do not get updated #3881

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

Open
davidpp opened this issue Oct 11, 2024 · 2 comments
Open

[Bug]: FQDN In Compose services do not get updated #3881

davidpp opened this issue Oct 11, 2024 · 2 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team.

Comments

@davidpp
Copy link

davidpp commented Oct 11, 2024

Error Message and Logs

Auto generated FQDN variable on service do not get updated when changing the service domain.

Steps to Reproduce

  1. Create a new service from one of the templates
  2. Change assigned domain to the front-end service of the stack and Save change
  3. Hit deploy
  4. FQDN still contain the domain that was generated when the service was created

Example Repository URL

No response

Coolify Version

v4.0.0-beta.358

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

@davidpp davidpp added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Oct 11, 2024
@snake302
Copy link

snake302 commented Oct 23, 2024

Yeah, I’m facing the same issue with Coolify Cloud + Docker Compose and have no idea what to do. Clicking 'Generate New Domain' creates a new domain, but the server is still accessible from the old one and returns a 404 error on the new URL. Custom URLs are also not working, and I’m unable to add or change anything

@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Nov 20, 2024
@peaklabs-dev peaklabs-dev removed the 🔍 Triage Issues that need assessment and prioritization. label Nov 20, 2024
@HomingHamster
Copy link

still facing this, and according to #1906 deleting the environment variable doesnt work

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.
Projects
None yet
Development

No branches or pull requests

4 participants