I initially loved the project and self-hosted it for the startup I worked at, Confinity, we had our development and production environment on Dokploy as it seemed stable, and was actively maintained, as-well as a really nice cost cutting measure
At some point, purely to support the project, I convinced the CEO to subscribe to Dokploy cloud, their paid service to manage the panel, all we had to do was just add the servers, and things were fine for a while
Though at some point, I found an issue, I pushed a change to our repository, then merged it to staging, so the dev branch was "deploying" in Dokploy, and staging was queued, since we didn't use dev anymore, I deleted that branch, assuming it'll clean up after itself, so staging can build instead of being in queue
How wrong I was, that instantly bricked both the server and the Dokploy panel, couldn't deploy, delete, stop, start or for the better part of 6 hours, do anything at all to our services, which became unresponsive entirely, both on the panel, and the sites themselves went down, despite the server still being up (and yes, we rebooted it multiple times), the issue was via Dokploy's PAID service that had cause everything to be stuck in limbo pretty much
We had to do an emergency migration out of Dokploy cloud to get our services and site back up, including all our databases, multiple times during this process I told the founder of Dokploy, as a paying customer, about this issue, and his response was simply "User issue", at which point I gave up and unsubscribed to the service, moving to Easypanel
definitely not a service I'd ever check out again
clandad · 27m ago
Hard to believe they left such an obvious security hole open for 6 months. Any random PR can access environment variables? That's concerning for a project with 20k+ stars.
I initially loved the project and self-hosted it for the startup I worked at, Confinity, we had our development and production environment on Dokploy as it seemed stable, and was actively maintained, as-well as a really nice cost cutting measure
At some point, purely to support the project, I convinced the CEO to subscribe to Dokploy cloud, their paid service to manage the panel, all we had to do was just add the servers, and things were fine for a while
Though at some point, I found an issue, I pushed a change to our repository, then merged it to staging, so the dev branch was "deploying" in Dokploy, and staging was queued, since we didn't use dev anymore, I deleted that branch, assuming it'll clean up after itself, so staging can build instead of being in queue
How wrong I was, that instantly bricked both the server and the Dokploy panel, couldn't deploy, delete, stop, start or for the better part of 6 hours, do anything at all to our services, which became unresponsive entirely, both on the panel, and the sites themselves went down, despite the server still being up (and yes, we rebooted it multiple times), the issue was via Dokploy's PAID service that had cause everything to be stuck in limbo pretty much
We had to do an emergency migration out of Dokploy cloud to get our services and site back up, including all our databases, multiple times during this process I told the founder of Dokploy, as a paying customer, about this issue, and his response was simply "User issue", at which point I gave up and unsubscribed to the service, moving to Easypanel
definitely not a service I'd ever check out again