You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the update, it seems the ability to add multiple servers to an App instance — particularly in a load-balanced configuration using NFS for shared volumes — has been removed or is no longer available in the UI showing a message like:
Cannot add additional servers
This application has persistent storage volumes configured. Applications with persistent storage cannot be deployed to multiple servers as the storage would not be accessible across different servers.
I understand the concern around syncing volumes, but in my case, I'm not using local volumes — I'm using a dedicated external NFS server, which is properly mounted and configured on each server I use for deployment. This setup allows my app instances to safely share a common persistent storage, and it worked perfectly before v4.0.0-beta.420.
The feature that allowed selecting multiple servers (primary and additional servers) for a service instance was not just a convenience — it was essential for deploying the same app with the same configuration across multiple nodes using a shared NFS volume. Now, with this option removed, I'm unable to deploy the same service to more than one server, even though the underlying shared storage (NFS) is properly configured and ready.
This feels more like a regression than a design choice. Could you clarify the reasoning behind limiting deployments to a single server in this scenario? And would it be possible to restore the previous behavior, at least when a shared volume is detected?
Thanks again for your work — Coolify is an awesome platform, and I’d really appreciate having this flexibility back.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Coolify team,
After the update, it seems the ability to add multiple servers to an App instance — particularly in a load-balanced configuration using NFS for shared volumes — has been removed or is no longer available in the UI showing a message like:
I understand the concern around syncing volumes, but in my case, I'm not using local volumes — I'm using a dedicated external NFS server, which is properly mounted and configured on each server I use for deployment. This setup allows my app instances to safely share a common persistent storage, and it worked perfectly before v4.0.0-beta.420.
The feature that allowed selecting multiple servers (primary and additional servers) for a service instance was not just a convenience — it was essential for deploying the same app with the same configuration across multiple nodes using a shared NFS volume. Now, with this option removed, I'm unable to deploy the same service to more than one server, even though the underlying shared storage (NFS) is properly configured and ready.
This feels more like a regression than a design choice. Could you clarify the reasoning behind limiting deployments to a single server in this scenario? And would it be possible to restore the previous behavior, at least when a shared volume is detected?
Thanks again for your work — Coolify is an awesome platform, and I’d really appreciate having this flexibility back.
Beta Was this translation helpful? Give feedback.
All reactions