mirror of
https://github.com/supabase/supabase.git
synced 2026-10-17 23:29:08 +03:00
a0eff938ff
* recreated connecting-to-postgres * adding GUI quickstart section with DBeaver * moved psql and pgadmin docs to GUI quickstart * added Prisma installation docs. Moved postgres.js and Drizzle into own section * added connection management docs * moved supavisor troubleshooting guide into troubleshooting section. Probably should not merge without adding more guides * updated IPv4 Add ons docs * removed typo * Update apps/docs/content/guides/platform/ipv4-address.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/platform/ipv4-address.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/database/supavisor.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/database/prisma.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/database/connection-management.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/database/connection-management.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * removed repetition in connection-management | added photos * Update apps/docs/content/guides/database/connecting-to-postgres.mdx Co-authored-by: Stas <sts@abc3.dev> * Update apps/docs/content/guides/platform/ipv4-address.mdx Co-authored-by: Stas <sts@abc3.dev> * Update apps/docs/content/guides/database/connection-management.mdx Co-authored-by: Stas <sts@abc3.dev> * Update apps/docs/content/guides/database/connecting-to-postgres.mdx Co-authored-by: Stas <sts@abc3.dev> * Update apps/docs/content/guides/platform/ipv4-address.mdx Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> * Update apps/docs/content/guides/database/connecting-to-postgres.mdx Co-authored-by: Stas <sts@abc3.dev> * updated proxy suggestions * added redirects * added images to connection-management guide * added unique ids to titles in prisma-troubleshooting section * added images to connection guide * added new images to prisma guide * reformatted admonition --------- Co-authored-by: Brian Brennglass <brian@Brians-MacBook-Pro.local> Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> Co-authored-by: Stas <sts@abc3.dev>
17 lines
4.0 KiB
Plaintext
17 lines
4.0 KiB
Plaintext
---
|
||
title: Supavisor
|
||
subtitle: Troubleshooting Supavisor errors
|
||
---
|
||
|
||
Supavisor logs are available under [Pooler Logs](/dashboard/project/_/logs/pooler-logs) in the Dashboard. The following are common errors and their solutions:
|
||
|
||
| Error Type | Description | Resolution Link |
|
||
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
|
||
| Max client connections reached | This error happens when the number of connections to Supavisor is more than [the allowed limit of your compute add-on](https://supabase.com/docs/guides/platform/compute-add-ons). | Follow this [guide](https://github.com/orgs/supabase/discussions/22305) to resolve. |
|
||
| Connection failed \{:error, :eaddrnotavail} to 'db.xxx.supabase.co':5432 | Supavisor cannot connect to the customer database. This is usually caused if the target database is unable to respond. | N/A |
|
||
| Connection failed \{:error, :nxdomain} to 'db.xxx.supabase.co':5432 | Supavisor cannot connect to the customer database. This is usually caused if the target database is unable to respond. | N/A |
|
||
| Connection closed when state was authentication | This error happens when either the database doesn’t exist or if the user doesn't have the right credentials. | N/A |
|
||
| Subscribe error: \{:error, :worker_not_found} | This log event is emitted when the client tries to connect to the database, but Supavisor does not have the necessary information to route the connection. Try reconnecting to the database as it can take some time for the project information to propagate to Supavisor. | N/A |
|
||
| Subscribe error: \{:error, \{:badrpc, \{:error, \{:erpc, :timeout}}}} | This is a timeout error when the communication between different Supavisor nodes takes longer than expected. Try reconnecting to the database. | N/A |
|
||
| Terminating with reason :client_termination when state was :busy | This error happens when the client terminates the connection before the connection with the database is completed. | N/A |
|