Open pieveee opened 2 years ago
In my case this solution does not work, I am getting 401 Unauthorized from https://api.<hostname>.tld/rest/v1/
, not sure where to look at....
@Kiho Do you use ingresses for the kong API? Make sure, that the SUPABASE_REST_URL
points to the kong API service. Depending on your implementation this is either the ingress hostname (SUB-DOMAIN.DOMAIN.TLD
, e.g. api.example.com) or the service hostname RELEASE_NAME-kong.NAMESPACE.svc.cluster.local
, e.g. supabase-supabase-kong.my-namespace.cluster.local).
@pieveee thanks for help, but my problem was just silly mistake, I don't know how I missed it but somehow key for rest service was not matching with other services.
Now everything work except real-time, I think issue is caused by Postgres image tdeoliv/supabase-bitnami-postgres
.
I tried to use supabase/postgres:14.1.0.21
but it throws error on installation.
@Kiho The usual case;) Regarding the Postgres Docker image try to use your own, as the one provided in the docs of this repo isn't quite up to date. Also, make sure the following dependencies are installed in the Database container:
This is the error I am facing.
2022-06-02 07:24:17.125 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.auto.conf"
2022-06-02 07:24:17.125 UTC [1] FATAL: data directory "/var/lib/postgresql/data" has invalid permissions
2022-06-02 07:24:17.125 UTC [1] DETAIL: Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml#L155 I think this is the part I need to translate it but don't know how?
I had that one too, but can't remember right now how I solved this. Please try to open a new issue, as it is unrelated to that one here. :)
anyone perhaps knows the resolution of this ? I am working on it and facing same problem. Thnks in advance.
OK I just fixed by using the latest supabase image version
This issue should be solvable quite easy.
When you access the Supabase Studio at
/project/default/api
it fails with the following error:This is similar to a issue in the official repo.
We concluded, that the request is made to
http://localhost:8000/rest/v1/
which is obviously not working, as there is no REST API running on my local machine. But it's the default value.The solution is to to set
SUPABASE_REST_URL
tohttps://api.<hostname>.tld/rest/v1/
in addition to the already existingSUPABASE_URL
env variable. This is convenient, as the user is able to see that this variable might needs to be adjusted.I assume the following files need to be changed for that: