Deploying vibe-kanban to server for remote access + auth & Docker questions

[bmajkut]

Hi everyone,

I'm looking for advice on hosting vibe-kanban on a server to access it from any computer. Has anyone done this successfully? How do you deploy it (e.g., Docker container, systemd, etc.), handle authentication to secure it properly, and connect it to an AI agent running on the server?

Specifically, I'm curious if anyone has run vibe-kanban in a Docker container and integrated it with server-side AI agents like Claude Code or similar.
​

My current setup: Running vibe-kanban via bash on the server using PM2 (on localhost). I have a Docker container in Coolify that proxies traffic from a subdomain to vibe-kanban on localhost and secures it with basic auth.

The issue: Every time I try to create a workspace, it keeps prompting for basic auth credentials repeatedly. Not sure if this is a Coolify config problem, proxy misconfiguration, or just a bad hosting approach for vibe-kanban. Any tips on fixing this or better alternatives?
​

Thanks in advance!

Bartosz

[iamriajul]

We've been using Vibe Kanban as a Coder app, and recently introduced central installation with multi-user support so people don't have to configure things again and again, specially this will be helpful for non-coders, they won't have to configure repo, etc to trigger a contribution.

[iamriajul]

We've got full deployment with helm chart (includes relay, remote, frontend optionally) for deploying it to k8s cluster. Thinking to opensource the helm chart.

[douglas-pereira-1]

@iamriajul

Could you provide some documentation on how you managed to do it?

I've already managed to run the server and have a connected client, however, when one user logs in, all other users access the same account because we're basically only running one client.

We wanted to achieve the goal of having an application running and executing everything on the server.

[iamriajul]

@iamriajul

Could you provide some documentation on how you managed to do it?

I've already managed to run the server and have a connected client, however, when one user logs in, all other users access the same account because we're basically only running one client.

We wanted to achieve the goal of having an application running and executing everything on the server.

I've open sourced the setup here:
https://github.com/iamriajul/vibe-kanban-team

[douglas-pereira-1]

I managed to run remote-server application but when trying to select a project directory, the message "Host context is required for local API requests. Navigate under /hosts/{hostId}/..." appears.
Also in the settings, there are several settings that are disabled, is that something I need to configure on the server?

I have managed to configure a client in my server too exposing port 3001/3002 to a public URL but when a user logs in, all other users who access the same URL see the first user's session because the client application is unique; this is not the behavior we need.

[iamriajul]

@douglas-pereira-1 are you facing issues using the vibe-kanban-team?

[bmajkut]

Ultimately, I got it working by running vibe‑kanban with PM2 to ensure it always starts on the same port and restarts automatically after server reboots.

For security, I used Tailscale VPN and defined a Tailscale service on that port. This gives me access to vibe‑kanban via a subdomain in the Tailscale network—so I can work on my tasks from anywhere in the world, even from my phone using just a browser.

With this setup, I no longer expose vibe‑kanban directly to the public internet, and the repeated basic auth prompts are gone. Everything works smoothly over the Tailscale network, and I can access my workspaces from any device.