How to access Supabase Studio? #62

Open
opened 2025-11-22 20:29:59 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @jhonatanlituma1 on GitHub (Jun 3, 2025).

Template Name

Supabase

Relevant Logs of the Error

No specific errors shown in logs; the Supabase Studio page simply does not load or fails to connect.

Steps to Reproduce the Error

  1. Deployed Supabase using the official template.
  2. Tried accessing the Supabase Studio at the Traefik-generated domain.
  3. The page does not load or shows an access error (timeout).

Environment Information

Operating System: Ubuntu 20.04
Dokploy version: 0.22.7
VPS Provider: Contabo
Template Version: 1.25.04
Browser: Microsoft Edge

When does this error occur?

After successful deployment

Additional Context

I am trying to access the Supabase Studio using the domain automatically generated by Traefik for my service, but I cannot enter the dashboard. I am using the official Supabase template.
I only get timeouts.
Does anyone have any idea what could be going on?
Maybe a port conflict?

Will you send a PR to fix it?

Maybe, need help

Originally created by @jhonatanlituma1 on GitHub (Jun 3, 2025). ### Template Name Supabase ### Relevant Logs of the Error No specific errors shown in logs; the Supabase Studio page simply does not load or fails to connect. ### Steps to Reproduce the Error 1. Deployed Supabase using the official template. 2. Tried accessing the Supabase Studio at the Traefik-generated domain. 3. The page does not load or shows an access error (timeout). ### Environment Information ```bash Operating System: Ubuntu 20.04 Dokploy version: 0.22.7 VPS Provider: Contabo Template Version: 1.25.04 Browser: Microsoft Edge ``` ### When does this error occur? After successful deployment ### Additional Context I am trying to access the Supabase Studio using the domain automatically generated by Traefik for my service, but I cannot enter the dashboard. I am using the official Supabase template. I only get timeouts. Does anyone have any idea what could be going on? Maybe a port conflict? ### Will you send a PR to fix it? Maybe, need help
GiteaMirror added the bug label 2025-11-22 20:29:59 -06:00
Author
Owner

@sebasegura97 commented on GitHub (Jul 7, 2025):

Hello! I'm facing the same issue

Operating System: Ubuntu 24.04
Dokploy version: 0.22.7
VPS Provider: Hostinger
Template Version: 1.25.04
Browser: Chrome

Image

Image

@sebasegura97 commented on GitHub (Jul 7, 2025): Hello! I'm facing the same issue Operating System: Ubuntu 24.04 Dokploy version: 0.22.7 VPS Provider: Hostinger Template Version: 1.25.04 Browser: Chrome ![Image](https://github.com/user-attachments/assets/b4cf71d7-fecc-4306-ab16-beadec9d4403) ![Image](https://github.com/user-attachments/assets/4ddffaed-4fdb-475a-a237-cd3ec354c9e8)
Author
Owner

@sebasegura97 commented on GitHub (Jul 7, 2025):

It' seems that the problem is with the supabase-studio port conflicting with dokploy port, i don't have experience in devops but i solved the issue mapping a port in the docker-compose.yml of the template, and now the service is accessible through http:mydomain.com:3001

studio:
  ports: 
        - 3001:3000

Image

@sebasegura97 commented on GitHub (Jul 7, 2025): It' seems that the problem is with the supabase-studio port conflicting with dokploy port, i don't have experience in devops but i solved the issue mapping a port in the docker-compose.yml of the template, and now the service is accessible through `http:mydomain.com:3001` ``` studio: ports: - 3001:3000 ``` ![Image](https://github.com/user-attachments/assets/858cfe6b-3748-470b-b98c-2d1b393e6deb)
Author
Owner

@samiralavi commented on GitHub (Nov 15, 2025):

The Supabase template is updated to the recent release in https://github.com/Dokploy/templates/pull/537. Supabase studio is not meant to be accessed directly via exposing its port, but from the kong proxy, which is already behind DokPloy traefic proxy. So it should just work out of the box.

@samiralavi commented on GitHub (Nov 15, 2025): The Supabase template is updated to the recent release in https://github.com/Dokploy/templates/pull/537. Supabase studio is not meant to be accessed directly via exposing its port, but from the kong proxy, which is already behind DokPloy traefic proxy. So it should just work out of the box.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#62