github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-18 07:32:46 -05:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[GH-ISSUE #558] Cannot create multiple instances of Supabase #15481

New Issue
Closed
opened 2026-07-14 22:44:04 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-07-14 22:44:04 -05:00
Owner
Copy Link

Originally created by @OmarUsman on GitHub (Nov 29, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/558

Template Name

Supabase

Relevant Logs of the Error

Creating multiple instances of Supabase on the same machine will give this error:

Image

Steps to Reproduce the Error

  1. Deploy the Supabase template - this will be project one
  2. Deploy the same template in a new project - this is project two and doesn't work without changing the ports

Environment Information

Operating system: Debian 12
Dokploy version: v0.25.11
VPS provider: OVH
Template version: latest

When does this error occur?

During template deployment

Additional Context

The workaround im using is changing these variables in my ENV:
POSTGRES_PORT=5432 -> POSTGRES_PORT=5532
POOLER_PROXY_PORT_TRANSACTION=6543 -> POOLER_PROXY_PORT_TRANSACTION=6643

It should 100% be possible to route different domains for example data.project-one.com -> instance 1 and data.project-two.com to the different instances and make supabase not accessable by the machine IP at all, I just can't seem to figure it out.

I've tried creating a new entry point for postgres in the traefik.yml, then using labels to route request based on the domain to their coressponding instance however this just didn't work - no error messages just no success.

Any help would be much appreciated!

Will you send a PR to fix it?

Maybe, need help

Originally created by @OmarUsman on GitHub (Nov 29, 2025). Original GitHub issue: https://github.com/Dokploy/templates/issues/558 ### Template Name Supabase ### Relevant Logs of the Error Creating multiple instances of Supabase on the same machine will give this error: <img width="994" height="211" alt="Image" src="https://github.com/user-attachments/assets/6d3fa76f-b24f-4071-a2a6-39a4aad37830" /> ### Steps to Reproduce the Error 1. Deploy the Supabase template - this will be project one 2. Deploy the same template in a new project - this is project two and doesn't work without changing the ports ### Environment Information ```bash Operating system: Debian 12 Dokploy version: v0.25.11 VPS provider: OVH Template version: latest ``` ### When does this error occur? During template deployment ### Additional Context The workaround im using is changing these variables in my ENV: POSTGRES_PORT=5432 -> POSTGRES_PORT=5532 POOLER_PROXY_PORT_TRANSACTION=6543 -> POOLER_PROXY_PORT_TRANSACTION=6643 It should 100% be possible to route different domains for example data.project-one.com -> instance 1 and data.project-two.com to the different instances and make supabase not accessable by the machine IP at all, I just can't seem to figure it out. I've tried creating a new entry point for postgres in the traefik.yml, then using labels to route request based on the domain to their coressponding instance however this just didn't work - no error messages just no success. Any help would be much appreciated! ### Will you send a PR to fix it? Maybe, need help
GiteaMirror added the bug label 2026-07-14 22:44:04 -05:00
GiteaMirror commented 2026-07-14 22:44:06 -05:00
Author
Owner
Copy Link

@aseha231ha commented on GitHub (Dec 29, 2025):

I think is a bug snince last update, i have same issue in all my servers

<!-- gh-comment-id:3697647619 --> @aseha231ha commented on GitHub (Dec 29, 2025): I think is a bug snince last update, i have same issue in all my servers
GiteaMirror commented 2026-07-14 22:44:06 -05:00
Author
Owner
Copy Link

@muhammedalibilgin commented on GitHub (Jan 30, 2026):

I experienced the same problem; I couldn't access the Dokploy panel because supabase and Dokploy PostgreSQL were using the same port. I deleted data while trying to solve it with ChatGPT, I'm very frustrated.

<!-- gh-comment-id:3822626653 --> @muhammedalibilgin commented on GitHub (Jan 30, 2026): I experienced the same problem; I couldn't access the Dokploy panel because supabase and Dokploy PostgreSQL were using the same port. I deleted data while trying to solve it with ChatGPT, I'm very frustrated.
GiteaMirror commented 2026-07-14 22:44:07 -05:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Jul 14, 2026):

The Supabase template was substantially reworked (#872/#961) and each deployment gets unique generated credentials/volumes per compose project, so multiple instances shouldn't collide anymore. Please retest with the current template and reopen with the exact error if it persists.

<!-- gh-comment-id:4971735680 --> @Siumauricio commented on GitHub (Jul 14, 2026): The Supabase template was substantially reworked (#872/#961) and each deployment gets unique generated credentials/volumes per compose project, so multiple instances shouldn't collide anymore. Please retest with the current template and reopen with the exact error if it persists.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#15481
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?