Developers Facing Supabase Connectivity Issues
11 posts in the last 60 days, all from GitHub.
“Hi. Im on the free plan and cannot really getnsupport, i think. Can anyone please try to help me with this question? I'm reviewing the PostgresSQL privilege posture in my project. Our catalogue inspection shows a pg\_defsult\_acl entry associated with the Supabase managed…”
“Intermittent Auth token timeouts and database connection timeouts in eu west 1 Confirmation [x] I have searched the Supabase documentation, GitHub Discussions, and existing issues. [ ] I have reproduced this in a minimal local Supabase project. [x] The issue appears to affect…”
“Bug report Describe the bug When trying to rebuild our supabase views, we receive a postgres error 'Connection terminated unexpectedly'. We suspect this is coming from creating a cloudflare workers QB client with the supabase pooler connection string. To Reproduce Our client…”
Multiple posts detail significant connectivity problems with Supabase services, particularly from Yemen. Users are experiencing DNS resolution failures and inability to access domains, impacting applications and Realtime functionality.
SOURCES (14)
“Hello Supabase Support, I'm experiencing persistent PostgreSQL authentication failures on my Supabase project. Project ref: zwrlcffyjwpmglclwygc Both connection methods fail: Session Pooler: aws 0 eu west 1.pooler.supabase.com:5432 Transaction Pooler: aws 0 eu west 1.pooler.supabase.com:6543 Username: postgres.zwrlcffyjwpmglclwygc The error is: FATAL: password authentication failed for user…”
“Hello Supabase Support, I have an active Supabase project with the following details: Project name: smart gestao Project ID: jaedhfcmjwbghoxplpa Region: South America (São Paulo) API URL: https://jaedhfcmjwbghoxplpa.supabase.co/ The project appears active in the Supabase Dashboard, and the service logs show successful requests. However, the API domain is not resolving consistently. DNS lookups using Google DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), and multiple international DNS servers return NXD”
“Intermittent Auth token timeouts and database connection timeouts in eu west 1 Confirmation [x] I have searched the Supabase documentation, GitHub Discussions, and existing issues. [ ] I have reproduced this in a minimal local Supabase project. [x] The issue appears to affect Supabase infrastructure/services, not only my application. Project information Project region: West EU (Ireland), eu west 1 Compute size: t4g.nano Project reference: ksuziuwcytavmoqisjso Affected production application: htt”
“Bug report [ ] I confirm this is a bug with Supabase, not with my own application. [ ] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug We are experiencing persistent PostgreSQL authentication failures through the Supavisor Session Pooler after rotating our database password in the Supabase Dashboard. The database password previously worked successfully through the Session Pooler. However, subsequent connection attempts using the same password are now rejecte”
“Bug report [ ] I confirm this is a bug with Supabase, not with my own application. [ ] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Go to '…' 2. Click on '…' 3. Scroll down to '…' 4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screen”
“Bug report [ ] I confirm this is a bug with Supabase, not with my own application. [ ] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Go to '…' 2. Click on '…' 3. Scroll down to '…' 4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screen”
“supabase team: Due to disconnect of Github / Supabase we are no longer able to access the supabase environment (ID snzjwioctymjhuzyzici · Supabase project entual proto, region eu west 1). We run a pro environment but since the disconnect we are not recognized as such as receive 0 support. Since early AUGUST, when this was first flagged. This is now causing operational blockades downstream. Nneither support or other teams are responsive; multiple outreaches have been attempted across multiple lan”
“Bug report [x] I confirm this is a bug with Supabase, not with my own application. [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Go to '…' 2. Click on '…' 3. Scroll down to '…' 4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screen”
“Bug report [x] I confirm this is a bug with Supabase, not with my own application. [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). Describe the bug I am unable to log in to the Supabase Dashboard using my email and password. The Supabase login page loads successfully, and I can enter my credentials. However, when I click Sign in , the login fails and displays”
“Bug report [ ] I confirm this is a bug with Supabase, not with my own application. [ ] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Go to '…' 2. Click on '…' 3. Scroll down to '…' 4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screen”
“Bug report Describe the bug When trying to rebuild our supabase views, we receive a postgres error 'Connection terminated unexpectedly'. We suspect this is coming from creating a cloudflare workers QB client with the supabase pooler connection string. To Reproduce Our client creation function Expected behavior The pooler connection to be successful Screenshots If applicable, add screenshots to help explain your problem. System information OS: [e.g. macOS, Windows] Browser (if applies) [e.g. chro”
“Hi. Im on the free plan and cannot really getnsupport, i think. Can anyone please try to help me with this question? I'm reviewing the PostgresSQL privilege posture in my project. Our catalogue inspection shows a pg\_defsult\_acl entry associated with the Supabase managed supabase\_admin role for tables created in the public schema. That entry grants table privileges to the anon and authenticated roles. Our application migrations run through the tenant postgres role and we have removed anon”
“Subject: Connectivity Issues with .supabase.co domains from Yemen (ISP: Yemen Net) Body: Hello Supabase Support Team, I am writing to report a recurring issue regarding connectivity to our Supabase project [tsmfstpbmcjkjpukccct.supabase.co] from Yemen. The Problem: We are experiencing consistent connection failures (specifically WebSocket connection drops and DNS/Handshake timeouts) when accessing our Supabase project from Yemen. This affects both our frontend application and Realtime services.”