mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 19:05:06 +03:00
608040b8cb
Contributes to DOCS-1052 ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Resolves MDX linting errors related to "simple" where it applies. There was a couple cases that did not apply. For example, a product with "Simple" in the name. These changes are made in context, either by removing or using a more descriptive synonym like "minimal" or "basic". ## Tophatting 1. Read each of the diffs. 2. See that the text still makes sense in context. For extra due diligence, you can run `pnpm lint:mdx` locally and see the 'simple' errors that remain and whether they are worth addressing. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Summary by CodeRabbit * **Documentation** * Updated many guide, tutorial, and troubleshooting pages with clearer “basic”/“minimal” wording across setup steps, local testing instructions, security cautions, and RLS guidance. * Refined headings, example descriptions, and inline comments for consistency (including deployment, MCP, metrics API, and search/function phrasing). * Improved readability with small snippet formatting tweaks (whitespace plus import/comment ordering) and added a self-hosting debugging note for Envoy admin endpoints via a short-lived `curl` container. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io> Co-authored-by: Nik Richers <nrichers@gmail.com>
57 lines
4.1 KiB
Plaintext
57 lines
4.1 KiB
Plaintext
---
|
|
title = "Diagnose HTTP API issues"
|
|
topics = [ "platform" ]
|
|
keywords = [ "API", "REST API", "GraphQL", "HTTP" ]
|
|
database_id = "e9fb853f-a37f-442a-b180-4aefd234a385"
|
|
|
|
[[errors]]
|
|
code = "5xx"
|
|
|
|
[[errors]]
|
|
message = "Connections refused"
|
|
---
|
|
|
|
Symptoms of HTTP API issues include:
|
|
|
|
- HTTP timeouts
|
|
- 5xx response codes
|
|
- High response times
|
|
|
|
### Under-provisioned resources
|
|
|
|
The most common class of issues that causes HTTP timeouts and 5xx response codes is the under-provisioning of resources for your project. This can cause your project to be unable to service the traffic it is receiving.
|
|
|
|
Each Supabase project is provisioned with [segregated compute resources](../platform/compute-add-ons). This allows the project to serve unlimited requests, as long as they can be handled using the resources that have been provisioned. Complex queries, or queries that process larger amounts of data, will require higher amounts of resources. As such, the amount of resources that can handle a high volume of basic queries (or queries involving small amounts of data), will likely be unable to handle a similar volume of complex queries.
|
|
|
|
You can view the resource utilization of your Supabase Project using the [reports in the Dashboard](/dashboard/project/_/observability/database).
|
|
|
|
Some common solutions for this issue are:
|
|
|
|
- [Upgrading](/dashboard/project/_/settings/compute-and-disk) to a [larger compute add-on](../platform/compute-add-ons) in order to serve higher volumes of traffic.
|
|
- [Optimizing the queries](../platform/performance#examining-query-performance) being executed.
|
|
- [Using fewer Postgres connections](../platform/performance#configuring-clients-to-use-fewer-connections) can reduce the amount of resources needed on the project.
|
|
- [Restarting](/dashboard/project/_/settings/general) the project. This only temporarily solves the issue by terminating any ongoing workloads that might be tying up your compute resources.
|
|
- All databases of the project, including [Read replicas](/docs/guides/platform/read-replicas), will be restarted.
|
|
- If you only want to restart a specific Read Replica, you can do so from the [Infrastructure Settings page](/dashboard/project/_/settings/infrastructure).
|
|
|
|
If your [Disk IO budget](../platform/compute-add-ons#disk-io) has been drained, you will need to either wait for it to be replenished the next day, or upgrade to a larger compute add-on to increase the budget available to your project.
|
|
|
|
## Unable to connect to your Supabase project
|
|
|
|
Symptom: You're unable to connect to your Postgres database directly, but can open the Project in the [Supabase Dashboard](/dashboard/project/_/).
|
|
|
|
### Too many open connections
|
|
|
|
Errors about too many open connections can be _temporarily_ resolved by [restarting the database](/dashboard/project/_/settings/general). However, this won't solve the underlying issue for a permanent solution.
|
|
|
|
- If you're receiving a `No more connections allowed (max_client_conn)` error:
|
|
- Configure your applications and services to [use fewer connections](../platform/performance#configuring-clients-to-use-fewer-connections).
|
|
- [Upgrade](/dashboard/project/_/settings/compute-and-disk) to a [larger compute add-on](../platform/compute-add-ons) to increase the number of available connections.
|
|
- If you're receiving a `sorry, too many clients already` or `remaining connection slots are reserved for non-replication superuser connections` error message in addition to the above suggestions, switch to using the [connection pooler](/docs/guides/database/connecting-to-postgres#connection-pool) instead.
|
|
|
|
### Connection refused
|
|
|
|
If you receive a `connection refused` error after a few initial failed connection attempts, your client has likely been temporarily blocked in order to protect the database from brute-force attacks. You can wait 30 minutes before trying again with the correct password, or you can [contact support](/dashboard/support/new) with your client's IP address to manually unblock you.
|
|
|
|
If you're also unable to open the project using the [Supabase Dashboard](/dashboard/project/_/), review the solutions for [under-provisioned projects](#under-provisioned-resources).
|