Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Supabase Docker self-hosting throws 500 errors

See original GitHub issue

Bug report

Describe the bug

The web interface loads but other areas either load infinity or throw various server errors.

To Reproduce

Follow the steps at Docker https://supabase.com/docs/guides/hosting/docker and head to localhost:3000 as instructed. The web interface (studio) loads but navigating to areas such as tables, API, and database, will show 500 errors.

Expected behavior

Able to navigate to areas such as tables, API, and database, without seeing 500 errors.

Screenshots

Below are screenshots of errors I get when running docker-compose up.

After these errors the images are constantly rebooted due to errors (mostly about connecting to the DB).

On the web panel:

System information

Ubuntu 20.04 on Raspberry Pi, using docker-compose

Issue Analytics

State:
Created 2 years ago
Reactions:6
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

franklinharveycommented, Jan 21, 2022

@xMdb try changing

KONG_URL=http://kong:8000

KONG_URL=http://localhost:8000

in your docker/env file

0reactions

xMdbcommented, Jan 30, 2022

very strange. Are you sure you’re rebuilding? With new a new environment you might need something like docker compose up --build or docker compose up --force-recreate --no-deps that might wipe your volume though

(sorry for the late reply, been busy)

@franklinharvey I did docker-compose with --build and it worked, but also after wiping my images/volumes and omitting the --build it worked. Not sure what happened, could have been those old images, my Docker version, or someone fixing it since the last time I tried (which was when I opened this issue)

If you have problems loading the api page: Pay attention that if you have changed the default ANON_KEY and SERVICE_ROLE_KEY they are also necessary in docker/volumes/api/kong.yml.

@rotemrevivo91 this also could have been my issue, as this time I re-cloned the repo and made sure to edit the kong.yml file.

I’m going to close this issue, as either wiping the images/volumes, using docker-compose up with --build, updating Docker, or changing the values in kong.yml was obviously the issue.

Edit: come to think of it, I also omitted special characters in my JTW secret. One special character could have also been messing up the API.

Top Results From Across the Web

Self-Hosting with Docker - Supabase

Learn how to configure and deploy Supabase with Docker. ... However, you might miss important log messages such as database errors.

Ask HN: Do you self-host your database? - Hacker News

Self-hosting in the cloud is ludicrously complicated in comparison. Docker, Sandstorm, Cloudron, your command line script - these are ...

Self-hosting with Supabase - DEV Community ‍ ‍

Tagged with docker, supabase, nginx, postgres. ... signUp() method from the supabase-js library, you may get an error 500.

supabase/supabase (Raised $0.00) - Issuehunt

Project cannot be deleted, showing error code 500 ... self-hosting supabase with docker on ubuntu 22 ... Edge Functions throws error when deployed....

Supabase Self Hosted responded with 404 - Stack Overflow

Here are my started containers. enter image description here. docker · docker-compose · self-hosting · supabase.