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).
Original GitHub issue: https://github.com/Dokploy/templates/issues/163
### 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 2026-04-16 11:08:42 -05:00
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
<!-- gh-comment-id:3044713341 -->
@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
```
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.
<!-- gh-comment-id:3536853864 -->
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jhonatanlituma1 on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/163
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
Environment Information
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
@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
@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@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.