[Bug]: Bug Report: Supabase Template uses SERVICE_FQDN instead of SERVICE_URL causing Studio to fail #7607
Description
Error Message and Logs
The Supabase service template uses ${SERVICE_FQDN_SUPABASEKONG} for SUPABASE_PUBLIC_URL and SUPABASE_PUBLIC_API environment variables. However, SERVICE_FQDN only returns the domain name without the protocol (e.g., devdb.example.com), while Supabase Studio requires a full URL with protocol (e.g., https://devdb.example.com). This causes the Studio container to become unhealthy with the error:
TypeError: Invalid URL
code: 'ERR_INVALID_URL',
input: 'devdb.example.com'
Expected behavior The template should use ${SERVICE_URL_SUPABASEKONG} which includes the https:// protocol. Affected lines in docker-compose (supabase-studio service)
Current (broken):
- 'SUPABASE_PUBLIC_URL=${SERVICE_FQDN_SUPABASEKONG}'
- 'SUPABASE_PUBLIC_API=${SERVICE_FQDN_SUPABASEKONG}'
Should be:
- 'SUPABASE_PUBLIC_URL=${SERVICE_URL_SUPABASEKONG}'
- 'SUPABASE_PUBLIC_API=${SERVICE_URL_SUPABASEKONG}'
Environment
- Coolify version: 4.0.0-beta.454
- Supabase Studio image: supabase/studio:20241202-71e5240
Workaround
Manually edit the Docker Compose in Coolify and change SERVICE_FQDN_SUPABASEKONG to SERVICE_URL_SUPABASEKONG for the affected variables, then redeploy.
Steps to Reproduce
Example Repository URL
No response
Coolify Version
4.0.0-beta.454
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response