What problem will this feature address?
Currently, when a domain is configured in Dokploy, it remains active and publicly accessible as long as it is defined. In some scenarios, I need to expose services temporarily (such as a VNC web interface, phpMyAdmin, or a development tool) but I don't want to leave the URL active 24/7.
To "hide" the service today, I have to either delete the domain configuration entirely or stop the service/container. Deleting the domain is counterproductive because it requires re-entering the host, path, and port settings later. Stopping the container isn't always an option if the service performs background tasks while not being accessed.
Describe the solution you'd like
would like to see a "Status" toggle (Enable/Disable) added to the domain configuration interface.
Behavior: When toggled "Off", Dokploy should update the reverse proxy configuration (Nginx/Traefik) to stop routing traffic to that specific domain or return a 403/503 status code, effectively "deactivating" the entry point without deleting the settings.
UI: A simple switch or toggle button next to the "HTTPS" or "Strip Path" options would be ideal.
Benefit: This allows users to keep their domain configurations saved but only "turn them on" during the specific window of time they are actually needed, improving security and convenience.
Describe alternatives you've considered
Deleting and recreating: This is the current workaround, but it's prone to human error and time-consuming, especially when managing multiple domains or complex paths.
Stopping the container: Not always viable if the application needs to keep running background jobs, cron tasks, or internal processing while the public access is closed.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
What problem will this feature address?
Currently, when a domain is configured in Dokploy, it remains active and publicly accessible as long as it is defined. In some scenarios, I need to expose services temporarily (such as a VNC web interface, phpMyAdmin, or a development tool) but I don't want to leave the URL active 24/7.
To "hide" the service today, I have to either delete the domain configuration entirely or stop the service/container. Deleting the domain is counterproductive because it requires re-entering the host, path, and port settings later. Stopping the container isn't always an option if the service performs background tasks while not being accessed.
Describe the solution you'd like
would like to see a "Status" toggle (Enable/Disable) added to the domain configuration interface.
Behavior: When toggled "Off", Dokploy should update the reverse proxy configuration (Nginx/Traefik) to stop routing traffic to that specific domain or return a 403/503 status code, effectively "deactivating" the entry point without deleting the settings.
UI: A simple switch or toggle button next to the "HTTPS" or "Strip Path" options would be ideal.
Benefit: This allows users to keep their domain configurations saved but only "turn them on" during the specific window of time they are actually needed, improving security and convenience.
Describe alternatives you've considered
Deleting and recreating: This is the current workaround, but it's prone to human error and time-consuming, especially when managing multiple domains or complex paths.
Stopping the container: Not always viable if the application needs to keep running background jobs, cron tasks, or internal processing while the public access is closed.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help