Teams can't share a server?

[bitnom]

This question has been asked many times on Discord without being answered. I install locally (1 server), create a new team, and I cannot give the team access to the server. Please tell me if it can somehow be done without breaking anything. If not, it needs to be a feature request (Multiple teams using the same server(s))

[maaaathis]

I also find it really confusing, especially as this option exists in the Sources. There it is a "System Wide?" checkbox.

[dawnniie]

A 'system wide' option for servers (or even just a way to clone) would be incredibly useful, at the moment for me it's just totally unrealistic to copy over keys and configurations for all my different servers. I can't use teams at all right now for this exact reason. Please make this easier!

[nsrau]

Does anyone know how to solve the problem of using localhost for more than one team?

[gmrizzo]

I don't think that this would be possible right now. If you setup the same server on another team, it would try to setup a second proxy as of my understanding. Two cannot run in parallel with the same configurations.

[nsrau]

ok, but what I don't understand is why it isn't possible to just hide projects between teams for example, but keep the same settings needed for the minimum to work.

[luckydonald]

My current work around is just adding the same server (i.e. localhost) to the other team under the server section as well.
Server may need a restart physically, because it doesn't seem to expect the docker to change from the install script, but after that it seems to work well enough.

[gabrielcossette]

I agree this makes the permission model much less useful.

However, this issue added to 4.1 milestone would solve the issue it seems?

#2378

[luckydonald]

My current work around is just adding the same server (i.e. localhost) to the other team under the server section as well.
Server may need a restart physically, because it doesn't seem to expect the docker to change from the install script, but after that it seems to work well enough.

---

Update 2026-03-14:

If you get an error the server with domain… is already in use by a different team, try to add it under a different name:

• for localhost, you may try 127.0.0.1 for IPv4 or ::1 for IPv6 as alternative, maybe this (new?) duplicate detection is dumb enough to consider it as a new host instead, if the strings don't match.
• If you use a domain, try adding it with a different (sub-)domain alias (Second A or AAAA record pointing to the same IP) or a raw IP address instead of the previously used domain.

[enesbala5]

@rubslopes @luckydonald Any update on this? Did it cause issues for you? I can't access services on the secondary team right now at all

[luckydonald]

So far no problems. Took a couple attempts to get it started initially (web interface will be gone for a minute, the it will cry for about 5 minutes and I spam restart), but it's been running since.

[endquote]

I tried to do this but it insists on me selecting a private key, and there's none to select from.

[luckydonald]

@endquote
Yeah, because it's a different team. Obviously they wouldn't automatically share login credentials.

Just generate a new one, and add it to authorized_keys like you normally would.
Or copy the root private key over.

[luckydonald]

If you get an error the server with domain… is already in use by a different team, try to add it under a different name:

• for localhost, you may try 127.0.0.1 for IPv4 or ::1 for IPv6 as alternative, maybe this (new?) duplicate detection is dumb enough.
• If it's a domain, try adding it with a different (sub-)domain or a raw IP address instead.

[rubslopes]

Me too. No problems so far. Em sáb., 12 de abr. de 2025, 09:30, Luckydonald ***@***.***> escreveu:

…

So far no problems. Took a couple attempts to get it started initially, but running since. — Reply to this email directly, view it on GitHub <#1820 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHCJLN26SQBSLGZNSGJHAM32ZEBOPAVCNFSM6AAAAABEMCV7UCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBRGIYDAMQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[derSato]

to be fair I don't want to run the same traefik + crowdsec + appsec + rate limiter on the new teams proxy again since its somewhat taxing on the system.
Like people point out hiding projects would be all that's needed.

[luckydonald]

Yeah, having an option to invite to simply share an existing server with a existing team would be way better.
Registering a server twice is only an ugly workaround until that's implemented.

[Default-01]

We need this, and it should be added asap!

[gauel]

Any update on this?

[luckydonald]

#1820 (comment) still works, that's all we know. My guess is that they are very busy with the coolify rewrite #5685.

[nicanordlc]

🙏🙏🙏 It would be good to divide group of projects by team on one big instance/server.

[yipfram]

Maybe by using different docker networks you can make this more secure?

Because sharing the server means everyone has access to root via terminal section... Not very safe :)

[luckydonald]

Probably a docker proxy could help?
I had no need as I trust my team.

[amirhmoradi]

Hi, thanks for the great work on Coolify.
I would love to see this feature implemented or at least workarounds documented please.

[endquote]

I swear that in an earlier version, I was able to have multiple teams all using localhost. I think this changed at some point.

Also need the ability to move things between teams that are using the same server.

[luckydonald]

First part is still possible: #1820 (comment)

[maukoese]

When I try to add the same server to another team I get an error about "the server with domain is already in use by a different team", so unable to use this workaround.

[luckydonald]

If it's localhost, you may try 127.0.0.1 for IPv4 or ::1 for IPv6 as alternative, maybe this (new?) duplicate detection is dumb enough to think it's a "different" server.
If you use a domain, try adding it with a different (sub-)domain or a raw IP address instead.

[Cinzya]

Just to clarify some things here, as this topic comes up more often now:
Teams are not supposed to share the same server as of this moment. The main reason is, there need to be more safeguards put in place, to ensure Team A can't access and alter the deployments of Team B, when both use the same server. Coolify does not have those safeguards yet, even if it might appear so on first glance.

Even if you disable the Terminal for the Team, nothing stops a user to mount the directory / volume of an App from the other team and make changes to this App.

Workarounds are at the moment being patched, as Coolify v4's stable release is being prepared. It is unclear, when / if this will be made possible again for v4, but it is on the roadmap for Coolify v5. Until then, we do not recommend trying to make two teams share the same server-

[maukoese]

Thank you for the heads up. Our use case was same VPS handling some 5 projects from 3 different Github organizations and would have preferred them to be under different teams - but of course can't deploy with that setup.

I suppose we can have all of them on one team for now and look at moving in the future.