-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"API Gateway" and "Postgres" infrastructure links in logs explorer are broken for self-hosted GA image(1.24.04 and newer) #26309
Comments
Oddly enough, this is happening to me using the |
Interesting. Are you referring to the 502 error, or the timestamp error specifically? Here are all the containers I'm using
I was working on updating the DigitalOcean self-hosted repo, so 2 of my containers differ compared to what's in this repo
There are also some other slight variations in configurations and health check addresses. So if using the above containers still fail, feel free to check out my repo and see if you get some better results. https://github.com/0reo/supabase-on-do It's a bit more involved the then officially supported one though. Instructions are in the readme or https://docs.digitalocean.com/developer-center/hosting-supabase-on-digitalocean/ |
Bug report
Describe the bug
trying to access API Gateway or Postgress via the dashboard using docker imgae supabase/studio:v1.24.04 and newer displays the following error
The logs from the analytics container provided the following for accessing API Gateway and Postgress respectively
After a lot of searching, I found the following issue/comment
https://github.com/orgs/supabase/discussions/19682#discussioncomment-7845129
and confirmed that the following does not work(as is now the default used by GA studio)
But manually running this does
timestamp
is not human readable though. trying to cast it usingtimestamp::date
gives the following errorand trying to use
date(timestamp)
gives the following errorthis does NOT happen using the studio:20240422-5cf8f30 image
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
Query logs should be displayed
System information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: