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

Removing domain not working #38

Closed
TheoCouss opened this issue May 3, 2024 · 3 comments · Fixed by #44
Closed

Removing domain not working #38

TheoCouss opened this issue May 3, 2024 · 3 comments · Fixed by #44
Assignees
Labels
bug Something isn't working

Comments

@TheoCouss
Copy link

TheoCouss commented May 3, 2024

Removing a domain from a service does not work, the domain is still mapped to the service in Traefik, rebooting Traefik does not solve the issue. It even breaks the custom domain of the panel.

I had to delete the service

@Siumauricio
Copy link
Contributor

Hi, @TheoCouss can you provide steps to reproduce the issue?

@TheoCouss
Copy link
Author

Sure!

To reproduce the issue:

  1. Begin with an empty project.
  2. Create a service using the nginxdemos/hello:plain-text Docker image.
  3. Add a domain to this service.
  4. Verify if the service is functioning properly.
  5. Remove the domain from the service in Dokploy.

Despite redeploying, Traefik continues to forward the domain to the service, which shouldn't be the case.

Additionally, attempting to restart Traefik from the settings exacerbates the problem by breaking the panel. To resolve this, it becomes necessary to delete the file associated with the service we initially created.

@Siumauricio
Copy link
Contributor

Thank you! you were right, in order to prevent this if we delete the last domain, traefik config should be deleted aswell, since traefik cannot containt this structure by default.

http:
  routers:
  services:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants