Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

chore(docs) - update troubleshooting links to new destinations (#52095)

Kody Jacksond4a2c464b25b
diff --git a/apps/docs/content/_partials/quickstart_connection_string.mdx b/apps/docs/content/_partials/quickstart_connection_string.mdx
index 48422f629c2..37b91e01f10 100644
--- a/apps/docs/content/_partials/quickstart_connection_string.mdx
+++ b/apps/docs/content/_partials/quickstart_connection_string.mdx
@@ -2,7 +2,7 @@
<Admonition type="caution">
- Don't use the Transaction pooler (port `6543`) as your app's main data source. Most ORMs rely on server-side prepared statements, which the Transaction pooler doesn't support. Use the Session pooler (port `5432`), or the direct connection string if you're in an [IPv6 environment](/docs/guides/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP) or have the [IPv4 Add-On](/docs/guides/platform/ipv4-address).
+ Don't use the Transaction pooler (port `6543`) as your app's main data source. Most ORMs rely on server-side prepared statements, which the Transaction pooler doesn't support. Use the Session pooler (port `5432`), or the direct connection string if you're in an [IPv6 environment](/kb/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP) or have the [IPv4 Add-On](/docs/guides/platform/ipv4-address).
</Admonition>
diff --git a/apps/docs/content/guides/ai-tools/mcp.mdx b/apps/docs/content/guides/ai-tools/mcp.mdx
index 361850963d7..94fd2bf7e04 100644
--- a/apps/docs/content/guides/ai-tools/mcp.mdx
+++ b/apps/docs/content/guides/ai-tools/mcp.mdx
@@ -144,7 +144,7 @@ To check which flow a creation tool uses, ask your client to list the available
Your MCP client controls how the confirmation is collected. Some clients support hooks or rules that answer elicitations automatically, so treat cost confirmation as a guardrail rather than proof that a person approved each action.
-Troubleshooting: If you expect a dialog and don't see one, see [Cost confirmations do not appear in your MCP client](/docs/guides/troubleshooting/cost-confirmations-do-not-appear-in-your-mcp-client-mVq3Lp).
+Troubleshooting: If you expect a dialog and don't see one, see [Cost confirmations do not appear in your MCP client](/kb/troubleshooting/cost-confirmations-do-not-appear-in-your-mcp-client-mVq3Lp).
### Destructive SQL confirmations
@@ -152,7 +152,7 @@ When SQL elicitation is available and your client supports forms, `execute_sql`
If SQL elicitation is unavailable, unsupported by your client, or skipped with [`skip_elicitations`](#skip-form-confirmations), SQL follows the existing execution path without an additional MCP confirmation. Read-only restrictions and permissions still apply. Keep the [security recommendations](#recommendations) in place.
-Troubleshooting: If you expect a dialog and don't see one, see [SQL confirmations do not appear in your MCP client](/docs/guides/troubleshooting/sql-confirmations-do-not-appear-in-your-mcp-client-sQf7Kp).
+Troubleshooting: If you expect a dialog and don't see one, see [SQL confirmations do not appear in your MCP client](/kb/troubleshooting/sql-confirmations-do-not-appear-in-your-mcp-client-sQf7Kp).
### Edge Function secrets
@@ -167,7 +167,7 @@ Enter secret values only in the Supabase Dashboard, never in chat, model input,
Save the secret in the Dashboard before confirming in your MCP client. If you cancel the request, this does not undo a secret you already saved in the Dashboard.
-Troubleshooting: If the tool is unavailable or the Dashboard flow is incomplete, see [Edge Function secret collection is unavailable or incomplete](/docs/guides/troubleshooting/edge-function-secret-collection-is-unavailable-or-incomplete-eFs4Nx).
+Troubleshooting: If the tool is unavailable or the Dashboard flow is incomplete, see [Edge Function secret collection is unavailable or incomplete](/kb/troubleshooting/edge-function-secret-collection-is-unavailable-or-incomplete-eFs4Nx).
## Configuration options
diff --git a/apps/docs/content/guides/api/securing-your-api.mdx b/apps/docs/content/guides/api/securing-your-api.mdx
index 6fd97443abc..a028d1f5265 100644
--- a/apps/docs/content/guides/api/securing-your-api.mdx
+++ b/apps/docs/content/guides/api/securing-your-api.mdx
@@ -177,7 +177,7 @@ If a required grant is missing, PostgREST returns a `42501` error with a hint th
}
```
-See [Database API 42501 errors](/docs/guides/troubleshooting/database-api-42501-errors) for the full troubleshooting flow.
+See [Database API 42501 errors](/kb/troubleshooting/database-api-42501-errors) for the full troubleshooting flow.
**Migration:** Bundle grants with your RLS setup in the same migration. The `grant` command controls role access. The `enable row level security` command and policies control row access.
diff --git a/apps/docs/content/guides/auth/server-side/migrating-to-ssr-from-auth-helpers.mdx b/apps/docs/content/guides/auth/server-side/migrating-to-ssr-from-auth-helpers.mdx
index c4eaa3a8b47..5ae290ef91f 100644
--- a/apps/docs/content/guides/auth/server-side/migrating-to-ssr-from-auth-helpers.mdx
+++ b/apps/docs/content/guides/auth/server-side/migrating-to-ssr-from-auth-helpers.mdx
@@ -41,7 +41,7 @@ npm install @supabase/ssr
The new `ssr` package exports two functions for creating a Supabase client. The `createBrowserClient` function is used in the client, and the `createServerClient` function is used in the server.
-Read the [Creating a client](/docs/guides/auth/server-side/creating-a-client) page for examples of creating a client in your framework [and our migration guide](/docs/guides/troubleshooting/how-to-migrate-from-supabase-auth-helpers-to-ssr-package-5NRunM).
+Read the [Creating a client](/docs/guides/auth/server-side/creating-a-client) page for examples of creating a client in your framework [and our migration guide](/kb/troubleshooting/how-to-migrate-from-supabase-auth-helpers-to-ssr-package-5NRunM).
## Next steps
diff --git a/apps/docs/content/guides/database/connecting-to-postgres.mdx b/apps/docs/content/guides/database/connecting-to-postgres.mdx
index 8c431c6101e..5cd7b55ec1b 100644
--- a/apps/docs/content/guides/database/connecting-to-postgres.mdx
+++ b/apps/docs/content/guides/database/connecting-to-postgres.mdx
@@ -170,7 +170,7 @@ Library defaults are too high for serverless. [Postgres.js](https://github.com/p
Raise the pool above 1 only when you have evidence that concurrent invocations on one instance are queuing for the connection.
-For more on sizing an application-side pool, see the [Supavisor FAQ](/docs/guides/troubleshooting/supavisor-faq-YyP5tI). If you use Prisma, [Prisma troubleshooting](/docs/guides/database/prisma/prisma-troubleshooting) covers the equivalent `connection_limit` setting.
+For more on sizing an application-side pool, see the [Supavisor FAQ](/kb/troubleshooting/supavisor-faq-YyP5tI). If you use Prisma, [Prisma troubleshooting](/docs/guides/database/prisma/prisma-troubleshooting) covers the equivalent `connection_limit` setting.
### Transaction mode limitations
@@ -185,7 +185,7 @@ For more on sizing an application-side pool, see the [Supavisor FAQ](/docs/guide
| asyncpg | `statement_cache_size=0` |
| JDBC | `prepareThreshold=0` |
-For node-postgres, Psycopg, and Rust drivers, see [Disabling prepared statements](/docs/guides/troubleshooting/disabling-prepared-statements-qL8lEL).
+For node-postgres, Psycopg, and Rust drivers, see [Disabling prepared statements](/kb/troubleshooting/disabling-prepared-statements-qL8lEL).
**Cursors** work inside a single transaction only. A `with hold` cursor is meant to outlive its transaction, and it doesn't survive the connection returning to the pool.
@@ -213,7 +213,7 @@ Set SSL to `require` so the driver refuses to connect without encryption. Most d
### Stale connections
-Serverless runtimes freeze a function between requests, which can leave a pooled TCP socket stale. If you see `CONNECT_TIMEOUT` errors or queries that hang until the execution limit, see [Troubleshooting `CONNECT_TIMEOUT` or hanging queries in Serverless Functions](/docs/guides/troubleshooting/troubleshooting-connect_timeout-or-hanging-queries-in-vercel-serverless-functions-775f92).
+Serverless runtimes freeze a function between requests, which can leave a pooled TCP socket stale. If you see `CONNECT_TIMEOUT` errors or queries that hang until the execution limit, see [Troubleshooting `CONNECT_TIMEOUT` or hanging queries in Serverless Functions](/kb/troubleshooting/troubleshooting-connect_timeout-or-hanging-queries-in-vercel-serverless-functions).
## Quickstarts [#quickstarts]
@@ -258,7 +258,7 @@ Each quickstart connects one ORM or database GUI to your Supabase database.
### Troubleshooting
-- [Tenant or user not found](/docs/guides/troubleshooting/tenant-or-user-not-found), when the pooler can't match your host and username to a project.
-- [FATAL: Password authentication failed](/docs/guides/troubleshooting/fatal-password-authentication-failed)
-- [Connection refused](/docs/guides/troubleshooting/error-connection-refused-when-trying-to-connect-to-supabase-database-hwG0Dr), which is usually an IP ban rather than an outage.
-- [Too many connections](/docs/guides/troubleshooting/too-many-connections-for-database-postgres)
+- [Tenant or user not found](/kb/troubleshooting/tenant-or-user-not-found), when the pooler can't match your host and username to a project.
+- [FATAL: Password authentication failed](/kb/troubleshooting/fatal-password-authentication-failed)
+- [Connection refused](/kb/troubleshooting/error-connection-refused-when-trying-to-connect-to-supabase-database-hwG0Dr), which is usually an IP ban rather than an outage.
+- [Too many connections](/kb/troubleshooting/too-many-connections-for-database-postgres)
diff --git a/apps/docs/content/guides/database/connecting-to-postgres/pooling-and-limits.mdx b/apps/docs/content/guides/database/connecting-to-postgres/pooling-and-limits.mdx
index 48e93635a53..e16a63f12b7 100644
--- a/apps/docs/content/guides/database/connecting-to-postgres/pooling-and-limits.mdx
+++ b/apps/docs/content/guides/database/connecting-to-postgres/pooling-and-limits.mdx
@@ -34,7 +34,7 @@ There are two kinds, and they work together.
**Server-side poolers**, such as Supavisor in transaction mode, run in front of the database and serve many clients. Use one when connections come from serverless or edge functions, or from anything that scales horizontally. These environments open many short-lived connections, which is the case an application-side pooler can't cover.
-For more on when each is needed and how to size them, see the [Supavisor FAQ](/docs/guides/troubleshooting/supavisor-faq-YyP5tI).
+For more on when each is needed and how to size them, see the [Supavisor FAQ](/kb/troubleshooting/supavisor-faq-YyP5tI).
### Shared and dedicated poolers [#shared-pooler]
@@ -52,7 +52,7 @@ Pool size sets how many connections a pooler is allowed to open to Postgres. You
Supavisor and PgBouncer read the same setting but apply it independently, so raising it raises the ceiling for both.
-For what the setting counts, and how it interacts with the user, database, and mode combinations connecting to your project, see [the Supavisor FAQ](/docs/guides/troubleshooting/supavisor-faq-YyP5tI).
+For what the setting counts, and how it interacts with the user, database, and mode combinations connecting to your project, see [the Supavisor FAQ](/kb/troubleshooting/supavisor-faq-YyP5tI).
### Client connections and backend connections [#client-connections-and-backend-connections]
@@ -74,7 +74,7 @@ Direct connections +
Stay below the maximum rather than at it. Supabase services hold their own connections, including Auth, Storage, PostgREST, and the health checker, and those come out of the same total. [Managing connections](/docs/guides/database/connection-management) covers how much headroom to leave.
-For the connection counts that come with each compute size, see [compute and disk](/docs/guides/platform/compute-and-disk#postgres-replication-slots-wal-senders-and-connections). For the terminology, see [Supavisor and connection terminology explained](/docs/guides/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO).
+For the connection counts that come with each compute size, see [compute and disk](/docs/guides/platform/compute-and-disk#postgres-replication-slots-wal-senders-and-connections). For the terminology, see [Supavisor and connection terminology explained](/kb/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO).
### Monitor connection usage [#monitor-connection-usage]
@@ -105,4 +105,4 @@ To list every connection with its state and query, and to read which Supabase se
- [Connect to your database](/docs/guides/database/connecting-to-postgres)
- [Managing connections](/docs/guides/database/connection-management)
-- [Supavisor FAQ](/docs/guides/troubleshooting/supavisor-faq-YyP5tI)
+- [Supavisor FAQ](/kb/troubleshooting/supavisor-faq-YyP5tI)
diff --git a/apps/docs/content/guides/database/connection-management.mdx b/apps/docs/content/guides/database/connection-management.mdx
index 91d54ef6e4c..56140196938 100644
--- a/apps/docs/content/guides/database/connection-management.mdx
+++ b/apps/docs/content/guides/database/connection-management.mdx
@@ -170,7 +170,7 @@ Which one to use depends on the session's state:
- For a session that's `idle in transaction`, cancelling does nothing - there's no running query to cancel, and the open transaction stays open regardless. Terminating the session is the only way to force the transaction closed and release its locks.
- For a session that's `idle in transaction (aborted)`, its ordinary locks were already released when the transaction aborted. The correct fix is for the client to issue `rollback`, which closes the transaction cleanly. Reserve `pg_terminate_backend` for a client that's unresponsive or a connection that needs to close regardless - it won't release anything further in this case, aside from a session-level advisory lock, which persists until the session ends.
-Both functions require you to either be a superuser, hold the `pg_signal_backend` role, or be signalling your own session - and even `pg_signal_backend` can't be used to stop a session belonging to an actual superuser role. If you hit a permission error while terminating a session, see [this troubleshooting guide](/docs/guides/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process).
+Both functions require you to either be a superuser, hold the `pg_signal_backend` role, or be signalling your own session - and even `pg_signal_backend` can't be used to stop a session belonging to an actual superuser role. If you hit a permission error while terminating a session, see [this troubleshooting guide](/kb/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process).
---
diff --git a/apps/docs/content/guides/database/custom-postgres-config.mdx b/apps/docs/content/guides/database/custom-postgres-config.mdx
index 26cb649347d..fae9f0891c3 100644
--- a/apps/docs/content/guides/database/custom-postgres-config.mdx
+++ b/apps/docs/content/guides/database/custom-postgres-config.mdx
@@ -121,45 +121,45 @@ Parameters marked with **Restart: Yes** cause the CLI to automatically restart y
Use the examples below with `supabase postgres-config update --project-ref <project-ref> --experimental`:
-| Parameter | Type | Restart | Example |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- | ------- | ----------------------------------------------- |
-| [cron.log_statement](https://github.com/citusdata/pg_cron#extension-settings) | CLI only | Yes | `--config cron.log_statement=false` |
-| [checkpoint_timeout](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-CHECKPOINT-TIMEOUT) | CLI only | No | `--config checkpoint_timeout=15min` |
-| [effective_cache_size](https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-EFFECTIVE-CACHE-SIZE) | CLI + SQL | No | `--config effective_cache_size=8GB` |
-| [hot_standby_feedback](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-HOT-STANDBY-FEEDBACK) | CLI only | No | `--config hot_standby_feedback=true` |
-| [logical_decoding_work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-LOGICAL-DECODING-WORK-MEM) | CLI + SQL | No | `--config logical_decoding_work_mem=128MB` |
-| [log_autovacuum_min_duration](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION) | CLI only | No | `--config log_autovacuum_min_duration=10s` |
-| [log_checkpoints](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-CHECKPOINTS) | CLI only | No | `--config log_checkpoints=true` |
-| [log_connections](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-CONNECTIONS) | CLI only | No | `--config log_connections=true` |
-| [log_disconnections](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-DISCONNECTIONS) | CLI only | No | `--config log_disconnections=true` |
-| [log_lock_waits](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LOCK-WAITS) | CLI + SQL | No | `--config log_lock_waits=true` |
-| [log_recovery_conflict_waits](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-RECOVERY-CONFLICT-WAITS) | CLI only | No | `--config log_recovery_conflict_waits=true` |
-| [log_replication_commands](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-REPLICATION-COMMANDS) | CLI + SQL | No | `--config log_replication_commands=true` |
-| [log_startup_progress_interval](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STARTUP-PROGRESS-INTERVAL) | CLI only | No | `--config log_startup_progress_interval=10s` |
-| [log_temp_files](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-TEMP-FILES) | CLI + SQL | No | `--config log_temp_files=10MB` |
-| [maintenance_work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM) | CLI + SQL | No | `--config maintenance_work_mem=512MB` |
-| [max_connections](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-MAX-CONNECTIONS) (Be aware of [these considerations](/docs/guides/troubleshooting/how-to-change-max-database-connections-_BQ8P5)) | CLI only | Yes | `--config max_connections=200` |
-| [max_locks_per_transaction](https://www.postgresql.org/docs/current/runtime-config-locks.html#GUC-MAX-LOCKS-PER-TRANSACTION) | CLI only | Yes | `--config max_locks_per_transaction=128` |
-| [max_logical_replication_workers](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-LOGICAL-REPLICATION-WORKERS) | CLI only | Yes | `--config max_logical_replication_workers=10` |
-| [max_parallel_maintenance_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-MAINTENANCE-WORKERS) | CLI + SQL | No | `--config max_parallel_maintenance_workers=2` |
-| [max_parallel_workers_per_gather](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS-PER-GATHER) | CLI + SQL | No | `--config max_parallel_workers_per_gather=2` |
-| [max_parallel_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS) | CLI + SQL | No | `--config max_parallel_workers=4` |
-| [max_replication_slots](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS) | CLI only | Yes | `--config max_replication_slots=10` |
-| [max_slot_wal_keep_size](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-SLOT-WAL-KEEP-SIZE) | CLI only | No | `--config max_slot_wal_keep_size=4GB` |
-| [max_standby_archive_delay](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-STANDBY-ARCHIVE-DELAY) | CLI only | No | `--config max_standby_archive_delay=30s` |
-| [max_standby_streaming_delay](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-STANDBY-STREAMING-DELAY) | CLI only | No | `--config max_standby_streaming_delay=30s` |
-| [max_sync_workers_per_subscription](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-SYNC-WORKERS-PER-SUBSCRIPTION) | CLI only | No | `--config max_sync_workers_per_subscription=10` |
-| [max_wal_size](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE) | CLI only | No | `--config max_wal_size=2GB` |
-| [max_wal_senders](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-WAL-SENDERS) | CLI only | Yes | `--config max_wal_senders=10` |
-| [max_worker_processes](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES) | CLI only | Yes | `--config max_worker_processes=8` |
-| [session_replication_role](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-SESSION-REPLICATION-ROLE) | CLI only | No | `--config session_replication_role=replica` |
-| [shared_buffers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-SHARED-BUFFERS) | CLI only | Yes | `--config shared_buffers=256MB` |
-| [statement_timeout](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-STATEMENT-TIMEOUT) | CLI + SQL | No | `--config statement_timeout=60s` |
-| [track_activity_query_size](https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-ACTIVITY-QUERY-SIZE) | CLI only | Yes | `--config track_activity_query_size=2048B` |
-| [track_commit_timestamp](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-TRACK-COMMIT-TIMESTAMP) | CLI only | Yes | `--config track_commit_timestamp=true` |
-| [wal_keep_size](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-KEEP-SIZE) | CLI only | No | `--config wal_keep_size=1GB` |
-| [wal_sender_timeout](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-SENDER-TIMEOUT) | CLI only | No | `--config wal_sender_timeout=60s` |
-| [work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-WORK-MEM) | CLI + SQL | No | `--config work_mem=64MB` |
+| Parameter | Type | Restart | Example |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------- | ----------------------------------------------- |
+| [cron.log_statement](https://github.com/citusdata/pg_cron#extension-settings) | CLI only | Yes | `--config cron.log_statement=false` |
+| [checkpoint_timeout](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-CHECKPOINT-TIMEOUT) | CLI only | No | `--config checkpoint_timeout=15min` |
+| [effective_cache_size](https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-EFFECTIVE-CACHE-SIZE) | CLI + SQL | No | `--config effective_cache_size=8GB` |
+| [hot_standby_feedback](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-HOT-STANDBY-FEEDBACK) | CLI only | No | `--config hot_standby_feedback=true` |
+| [logical_decoding_work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-LOGICAL-DECODING-WORK-MEM) | CLI + SQL | No | `--config logical_decoding_work_mem=128MB` |
+| [log_autovacuum_min_duration](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-AUTOVACUUM-MIN-DURATION) | CLI only | No | `--config log_autovacuum_min_duration=10s` |
+| [log_checkpoints](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-CHECKPOINTS) | CLI only | No | `--config log_checkpoints=true` |
+| [log_connections](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-CONNECTIONS) | CLI only | No | `--config log_connections=true` |
+| [log_disconnections](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-DISCONNECTIONS) | CLI only | No | `--config log_disconnections=true` |
+| [log_lock_waits](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LOCK-WAITS) | CLI + SQL | No | `--config log_lock_waits=true` |
+| [log_recovery_conflict_waits](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-RECOVERY-CONFLICT-WAITS) | CLI only | No | `--config log_recovery_conflict_waits=true` |
+| [log_replication_commands](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-REPLICATION-COMMANDS) | CLI + SQL | No | `--config log_replication_commands=true` |
+| [log_startup_progress_interval](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STARTUP-PROGRESS-INTERVAL) | CLI only | No | `--config log_startup_progress_interval=10s` |
+| [log_temp_files](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-TEMP-FILES) | CLI + SQL | No | `--config log_temp_files=10MB` |
+| [maintenance_work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM) | CLI + SQL | No | `--config maintenance_work_mem=512MB` |
+| [max_connections](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-MAX-CONNECTIONS) (Be aware of [these considerations](/kb/troubleshooting/how-to-change-max-database-connections-_BQ8P5)) | CLI only | Yes | `--config max_connections=200` |
+| [max_locks_per_transaction](https://www.postgresql.org/docs/current/runtime-config-locks.html#GUC-MAX-LOCKS-PER-TRANSACTION) | CLI only | Yes | `--config max_locks_per_transaction=128` |
+| [max_logical_replication_workers](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-LOGICAL-REPLICATION-WORKERS) | CLI only | Yes | `--config max_logical_replication_workers=10` |
+| [max_parallel_maintenance_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-MAINTENANCE-WORKERS) | CLI + SQL | No | `--config max_parallel_maintenance_workers=2` |
+| [max_parallel_workers_per_gather](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS-PER-GATHER) | CLI + SQL | No | `--config max_parallel_workers_per_gather=2` |
+| [max_parallel_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS) | CLI + SQL | No | `--config max_parallel_workers=4` |
+| [max_replication_slots](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS) | CLI only | Yes | `--config max_replication_slots=10` |
+| [max_slot_wal_keep_size](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-SLOT-WAL-KEEP-SIZE) | CLI only | No | `--config max_slot_wal_keep_size=4GB` |
+| [max_standby_archive_delay](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-STANDBY-ARCHIVE-DELAY) | CLI only | No | `--config max_standby_archive_delay=30s` |
+| [max_standby_streaming_delay](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-STANDBY-STREAMING-DELAY) | CLI only | No | `--config max_standby_streaming_delay=30s` |
+| [max_sync_workers_per_subscription](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-SYNC-WORKERS-PER-SUBSCRIPTION) | CLI only | No | `--config max_sync_workers_per_subscription=10` |
+| [max_wal_size](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE) | CLI only | No | `--config max_wal_size=2GB` |
+| [max_wal_senders](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-WAL-SENDERS) | CLI only | Yes | `--config max_wal_senders=10` |
+| [max_worker_processes](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES) | CLI only | Yes | `--config max_worker_processes=8` |
+| [session_replication_role](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-SESSION-REPLICATION-ROLE) | CLI only | No | `--config session_replication_role=replica` |
+| [shared_buffers](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-SHARED-BUFFERS) | CLI only | Yes | `--config shared_buffers=256MB` |
+| [statement_timeout](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-STATEMENT-TIMEOUT) | CLI + SQL | No | `--config statement_timeout=60s` |
+| [track_activity_query_size](https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-ACTIVITY-QUERY-SIZE) | CLI only | Yes | `--config track_activity_query_size=2048B` |
+| [track_commit_timestamp](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-TRACK-COMMIT-TIMESTAMP) | CLI only | Yes | `--config track_commit_timestamp=true` |
+| [wal_keep_size](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-KEEP-SIZE) | CLI only | No | `--config wal_keep_size=1GB` |
+| [wal_sender_timeout](https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-SENDER-TIMEOUT) | CLI only | No | `--config wal_sender_timeout=60s` |
+| [work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-WORK-MEM) | CLI + SQL | No | `--config work_mem=64MB` |
#### Managing Postgres configuration with the CLI
diff --git a/apps/docs/content/guides/database/postgres/roles.mdx b/apps/docs/content/guides/database/postgres/roles.mdx
index 5e57b21f01d..4f2c97836e7 100644
--- a/apps/docs/content/guides/database/postgres/roles.mdx
+++ b/apps/docs/content/guides/database/postgres/roles.mdx
@@ -125,7 +125,7 @@ This role:
### `dashboard_user`
-The Supabase Dashboard doesn't connect as this role. Queries you run in the Dashboard execute as `postgres` and include a `-- source: dashboard` comment, which you can use to [find them in the Postgres logs](/docs/guides/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj).
+The Supabase Dashboard doesn't connect as this role. Queries you run in the Dashboard execute as `postgres` and include a `-- source: dashboard` comment, which you can use to [find them in the Postgres logs](/kb/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj).
### `supabase_admin`
diff --git a/apps/docs/content/guides/functions/auth-headers.mdx b/apps/docs/content/guides/functions/auth-headers.mdx
index f358bbab67d..5d3097bc5fa 100644
--- a/apps/docs/content/guides/functions/auth-headers.mdx
+++ b/apps/docs/content/guides/functions/auth-headers.mdx
@@ -50,4 +50,4 @@ Set the flag per function in `supabase/config.toml`:
verify_jwt = false
```
-For 401 failure modes and how to diagnose them, see [Edge Function 401 error response](/docs/guides/troubleshooting/edge-function-401-error-response).
+For 401 failure modes and how to diagnose them, see [Edge Function 401 error response](/kb/troubleshooting/edge-function-401-error-response).
diff --git a/apps/docs/content/guides/functions/error-codes.mdx b/apps/docs/content/guides/functions/error-codes.mdx
index d7e48aeed33..dcaed444f7a 100644
--- a/apps/docs/content/guides/functions/error-codes.mdx
+++ b/apps/docs/content/guides/functions/error-codes.mdx
@@ -264,7 +264,7 @@ These errors indicate issues with function loading, execution, or the underlying
### NOT_FOUND_FUNCTION_BLOB
-**Cause:** Your Edge Function metadata resolved, but its deployment bundle was missing from storage and could not be loaded (the metadata points at a different version than the stored bundle). This returns the same `Requested function was not found` message as `NOT_FOUND`, so the `sb-error-code` header is what distinguishes them — see [Edge Function 404 error response](/docs/guides/troubleshooting/edge-function-404-error-response).
+**Cause:** Your Edge Function metadata resolved, but its deployment bundle was missing from storage and could not be loaded (the metadata points at a different version than the stored bundle). This returns the same `Requested function was not found` message as `NOT_FOUND`, so the `sb-error-code` header is what distinguishes them — see [Edge Function 404 error response](/kb/troubleshooting/edge-function-404-error-response).
**Common causes:**
diff --git a/apps/docs/content/guides/functions/limits.mdx b/apps/docs/content/guides/functions/limits.mdx
index 6de5dcfecee..63c043896ba 100644
--- a/apps/docs/content/guides/functions/limits.mdx
+++ b/apps/docs/content/guides/functions/limits.mdx
@@ -33,7 +33,7 @@ subtitle: "Limits applied Edge Functions in Supabase's hosted platform."
- Secret name length: up to **256** characters
- Maximum secret size: **48 KiB** (**24,576** characters)
- Names must NOT start with the prefix `SUPABASE_` (this prefix is reserved).
-- Need more than 100 secrets? [Bundle secrets into a JSON value](/docs/guides/troubleshooting/working-around-the-edge-function-secrets-limit).
+- Need more than 100 secrets? [Bundle secrets into a JSON value](/kb/troubleshooting/working-around-the-edge-function-secrets-limit).
## Other limits & restrictions
diff --git a/apps/docs/content/guides/observability/detecting.mdx b/apps/docs/content/guides/observability/detecting.mdx
index c1eff9aa597..2090e068eb5 100644
--- a/apps/docs/content/guides/observability/detecting.mdx
+++ b/apps/docs/content/guides/observability/detecting.mdx
@@ -44,7 +44,7 @@ limit 2;
Rates use valid statuses only. Report `unknown_status` separately; no valid statuses makes the check unable to assess. Auth events without response statuses are not successful requests. A missing source row requires a capture/traffic check, not an assumed zero error rate.
-**Next:** narrow to the source and hour. Collect at most five event IDs with timestamps and status, then follow [API error troubleshooting](/docs/guides/troubleshooting/discovering-and-interpreting-api-errors-in-the-logs-7xREI9). Redact paths and messages. After a fix, rerun on a comparable window.
+**Next:** narrow to the source and hour. Collect at most five event IDs with timestamps and status, then follow [API error troubleshooting](/kb/troubleshooting/discovering-and-interpreting-api-errors-in-the-logs-7xREI9). Redact paths and messages. After a fix, rerun on a comparable window.
### Check connection pressure
diff --git a/apps/docs/content/guides/platform/billing-faq.mdx b/apps/docs/content/guides/platform/billing-faq.mdx
index ad9612b77d9..849f2a2052a 100644
--- a/apps/docs/content/guides/platform/billing-faq.mdx
+++ b/apps/docs/content/guides/platform/billing-faq.mdx
@@ -130,7 +130,7 @@ The Fair Use Policy is applied through service restrictions. This could mean:
- Pausing projects
- Switching databases to read-only mode
- Disabling new project launches/transfers
-- Responding with a [402 status code](/docs/guides/troubleshooting/http-status-codes#402-service-restriction) for all API requests
+- Responding with a [402 status code](/kb/troubleshooting/http-status-codes#402-service-restriction) for all API requests
The Fair Use Policy is generally applied to all projects of the restricted organization.
diff --git a/apps/docs/content/guides/platform/compute-and-disk.mdx b/apps/docs/content/guides/platform/compute-and-disk.mdx
index ba5284349cf..55e44257fa6 100644
--- a/apps/docs/content/guides/platform/compute-and-disk.mdx
+++ b/apps/docs/content/guides/platform/compute-and-disk.mdx
@@ -31,7 +31,7 @@ In paid organizations, Nano Compute are billed at the same price as Micro Comput
| 16XL | <Price price="5.12" /> | ~<Price price="3" />,730 | Dedicated · 64 vCPUs | 256 GB | 10 TB |
| >16XL | - | [Contact Us](/dashboard/support/new?category=sales&subject=Enquiry%20about%20larger%20instance%20sizes) | Custom | Custom | Custom |
-[^1]: Database max connections are recommended values and can be [customized via `max_connections`](/docs/guides/database/custom-postgres-config) depending on your use case. Be aware of [these considerations](/docs/guides/troubleshooting/how-to-change-max-database-connections-_BQ8P5) before modifying.
+[^1]: Database max connections are recommended values and can be [customized via `max_connections`](/docs/guides/database/custom-postgres-config) depending on your use case. Be aware of [these considerations](/kb/troubleshooting/how-to-change-max-database-connections-_BQ8P5) before modifying.
[^2]: Database size for each compute instance is the default recommendation but the actual performance of your database has many contributing factors, including resources available to it and the size of the data contained within it. See the [shared responsibility model](/docs/guides/deployment/shared-responsibility-model) for more information.
diff --git a/apps/docs/content/guides/realtime/authorization.mdx b/apps/docs/content/guides/realtime/authorization.mdx
index a467f43d6fa..52eec7892be 100644
--- a/apps/docs/content/guides/realtime/authorization.mdx
+++ b/apps/docs/content/guides/realtime/authorization.mdx
@@ -35,7 +35,7 @@ Remove the `ALTER TABLE` line and the rest of the migration passes. If a migrati
select relrowsecurity from pg_class where oid = 'realtime.messages'::regclass;
```
-If you hit that error, see [must be owner of table messages](/docs/guides/troubleshooting/realtime-must-be-owner-of-table-messages).
+If you hit that error, see [must be owner of table messages](/kb/troubleshooting/realtime-must-be-owner-of-table-messages).
</Admonition>
diff --git a/apps/docs/content/guides/realtime/broadcast.mdx b/apps/docs/content/guides/realtime/broadcast.mdx
index a3cac8f4605..a089a6c38c0 100644
--- a/apps/docs/content/guides/realtime/broadcast.mdx
+++ b/apps/docs/content/guides/realtime/broadcast.mdx
@@ -1021,7 +1021,7 @@ Broadcast Changes allows you to trigger messages from your database. To achieve
It uses partitioned tables per day, which allows performant deletion of your previous messages by dropping the physical tables of this partitioned table. Tables older than 3 days are deleted.
-A client connecting over WebSocket creates those daily partitions. `realtime.send` does not. With no partition for today, the insert fails and Postgres logs a `WarnSendingBroadcastMessage` warning, so connect a client before you broadcast from the database. See [Realtime: `WarnSendingBroadcastMessage`](/docs/guides/troubleshooting/realtime-warn-sending-broadcast-message) if you hit that warning.
+A client connecting over WebSocket creates those daily partitions. `realtime.send` does not. With no partition for today, the insert fails and Postgres logs a `WarnSendingBroadcastMessage` warning, so connect a client before you broadcast from the database. See [Realtime: `WarnSendingBroadcastMessage`](/kb/troubleshooting/realtime-warn-sending-broadcast-message) if you hit that warning.
Broadcasting from the database works like a client-side broadcast, using WebSockets to send JSON payloads. [Realtime Authorization](/docs/guides/realtime/authorization) is required and enabled by default to protect your data.
diff --git a/apps/docs/content/guides/realtime/reports.mdx b/apps/docs/content/guides/realtime/reports.mdx
index f853cdc4d93..623a057913c 100644
--- a/apps/docs/content/guides/realtime/reports.mdx
+++ b/apps/docs/content/guides/realtime/reports.mdx
@@ -55,15 +55,15 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Configure connection limit | Adjust the "Max concurrent connections" setting to increase or decrease the connection limit for your project | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Upgrade plan | Increase available client connections. Connection limits vary by plan: Free (200), Pro (500), Pro no spend cap (10,000), Team (10,000), Enterprise (10,000+) | [Pricing and Plans](/pricing) |
-| Review quotas | Understand connection limits and other Realtime quotas for your plan | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
-| Understand connection quota | Learn how the concurrent connections quota works and how to configure it for your plan | [Concurrent Peak Connections Quota Troubleshooting](/docs/guides/troubleshooting/realtime-concurrent-peak-connections-quota-jdDqcp) |
-| Fix silent disconnections | Fix connection issues in background applications using heartbeat callbacks and Web Workers | [Handling Silent Disconnections in Background Apps](/docs/guides/troubleshooting/realtime-handling-silent-disconnections-in-backgrounded-applications-592794) |
-| Check logs | Investigate connection errors and quota errors in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Contact support | Request custom quota increases for Enterprise plans or discuss connection requirements | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| Configure connection limit | Adjust the "Max concurrent connections" setting to increase or decrease the connection limit for your project | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Upgrade plan | Increase available client connections. Connection limits vary by plan: Free (200), Pro (500), Pro no spend cap (10,000), Team (10,000), Enterprise (10,000+) | [Pricing and Plans](/pricing) |
+| Review quotas | Understand connection limits and other Realtime quotas for your plan | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
+| Understand connection quota | Learn how the concurrent connections quota works and how to configure it for your plan | [Concurrent Peak Connections Quota Troubleshooting](/kb/troubleshooting/realtime-concurrent-peak-connections-quota-jdDqcp) |
+| Fix silent disconnections | Fix connection issues in background applications using heartbeat callbacks and Web Workers | [Handling Silent Disconnections in Background Apps](/kb/troubleshooting/realtime-handling-silent-disconnections-in-backgrounded-applications) |
+| Check logs | Investigate connection errors and quota errors in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Contact support | Request custom quota increases for Enterprise plans or discuss connection requirements | [Support Portal](/dashboard/support/new) |
## Broadcast Events
@@ -85,14 +85,14 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
-| Configure event limits | Adjust "Max events per second" and "Max payload size in KB" settings to optimize broadcast throughput and message size limits | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Review quotas | Understand message per second limits (Free: 100, Pro: 500, Pro no spend cap/Team/Enterprise: 2,500) and broadcast payload size limits (Free: 256 KB, Pro+: 3,000 KB) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
-| Check logs | Investigate broadcast errors or quota limit issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Debug with logger | Enable logging to track messages sent and received, and diagnose broadcast delivery issues | [Debugging Realtime with Logger](/docs/guides/troubleshooting/realtime-debugging-with-logger) |
-| Learn broadcast basics | Understand how to implement and optimize broadcast messaging in your application | [Broadcast Guide](/docs/guides/realtime/broadcast) |
-| Contact support | Request custom quota increases for Enterprise plans or discuss messaging requirements | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| Configure event limits | Adjust "Max events per second" and "Max payload size in KB" settings to optimize broadcast throughput and message size limits | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Review quotas | Understand message per second limits (Free: 100, Pro: 500, Pro no spend cap/Team/Enterprise: 2,500) and broadcast payload size limits (Free: 256 KB, Pro+: 3,000 KB) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
+| Check logs | Investigate broadcast errors or quota limit issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Debug with logger | Enable logging to track messages sent and received, and diagnose broadcast delivery issues | [Debugging Realtime with Logger](/kb/troubleshooting/realtime-debugging-with-logger) |
+| Learn broadcast basics | Understand how to implement and optimize broadcast messaging in your application | [Broadcast Guide](/docs/guides/realtime/broadcast) |
+| Contact support | Request custom quota increases for Enterprise plans or discuss messaging requirements | [Support Portal](/dashboard/support/new) |
## Presence Events
@@ -114,14 +114,14 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
-| Configure presence limits | Adjust the "Max presence events per second" setting to optimize presence state update throughput | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Review quotas | Understand presence messages per second limits (Free: 20, Pro: 50, Pro no spend cap/Team/Enterprise: 1,000) and presence keys per object limits (10 for most plans) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
-| Check logs | Investigate presence errors or quota limit issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Debug with logger | Enable logging to track presence events and diagnose state synchronization issues | [Debugging Realtime with Logger](/docs/guides/troubleshooting/realtime-debugging-with-logger) |
-| Learn presence basics | Understand how to implement and optimize presence state tracking in your application | [Presence Guide](/docs/guides/realtime/presence) |
-| Contact support | Request custom quota increases for Enterprise plans or discuss presence requirements | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| Configure presence limits | Adjust the "Max presence events per second" setting to optimize presence state update throughput | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Review quotas | Understand presence messages per second limits (Free: 20, Pro: 50, Pro no spend cap/Team/Enterprise: 1,000) and presence keys per object limits (10 for most plans) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
+| Check logs | Investigate presence errors or quota limit issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Debug with logger | Enable logging to track presence events and diagnose state synchronization issues | [Debugging Realtime with Logger](/kb/troubleshooting/realtime-debugging-with-logger) |
+| Learn presence basics | Understand how to implement and optimize presence state tracking in your application | [Presence Guide](/docs/guides/realtime/presence) |
+| Contact support | Request custom quota increases for Enterprise plans or discuss presence requirements | [Support Portal](/dashboard/support/new) |
## Postgres Changes Events
@@ -173,13 +173,13 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| Review quotas | Understand channel joins per second limits (Free: 100, Pro: 500, Pro no spend cap/Team/Enterprise: 2,500) and channels per connection limits (100 for most plans) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
-| Check logs | Investigate `too_many_joins` errors or channel join failures in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Fix channel errors | Learn how to properly manage channel lifecycle and prevent channel leaks in your application | [TooManyChannels Error Troubleshooting](/docs/guides/troubleshooting/realtime-too-many-channels-error) |
-| Learn channel basics | Understand how Realtime channels work and best practices for channel management | [Realtime Channels Concepts](/docs/guides/realtime/concepts#channels) |
-| Contact support | Request custom quota increases for Enterprise plans or discuss high-volume channel join requirements | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
+| Review quotas | Understand channel joins per second limits (Free: 100, Pro: 500, Pro no spend cap/Team/Enterprise: 2,500) and channels per connection limits (100 for most plans) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
+| Check logs | Investigate `too_many_joins` errors or channel join failures in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Fix channel errors | Learn how to properly manage channel lifecycle and prevent channel leaks in your application | [TooManyChannels Error Troubleshooting](/kb/troubleshooting/realtime-too-many-channels-error) |
+| Learn channel basics | Understand how Realtime channels work and best practices for channel management | [Realtime Channels Concepts](/docs/guides/realtime/concepts#channels) |
+| Contact support | Request custom quota increases for Enterprise plans or discuss high-volume channel join requirements | [Support Portal](/dashboard/support/new) |
## Message Payload Size
@@ -264,17 +264,17 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| Configure connection pool | Adjust the "Database connection pool size" setting to increase the number of connections available for RLS authorization checks, which can improve performance for high-volume channel subscriptions | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Optimize RLS policies | Learn how to optimize RLS policies with indexes, function wrapping, and query optimization techniques | [RLS Performance Best Practices](/docs/guides/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
-| Check logs | Investigate RLS authorization errors or timeout issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Learn authorization basics | Understand how RLS policies work with private channels and best practices for implementation | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
-| Create indexes | Add indexes on columns frequently used in RLS policy conditions to speed up authorization checks | [Database Indexes Guide](/docs/guides/database/postgres/indexes) |
-| Use index advisor | Automatically detect missing indexes that could improve RLS policy performance | [Index Advisor Extension Guide](/docs/guides/database/extensions/index_advisor) |
-| Optimize queries | Learn techniques for optimizing queries including partial indexes and composite indexes for RLS conditions | [Query Optimization Guide](/docs/guides/database/query-optimization) |
-| Monitor database | Review database query performance and identify slow queries that may be affecting RLS execution | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
-| Contact support | Discuss RLS optimization strategies or get assistance with complex authorization requirements | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| Configure connection pool | Adjust the "Database connection pool size" setting to increase the number of connections available for RLS authorization checks, which can improve performance for high-volume channel subscriptions | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Optimize RLS policies | Learn how to optimize RLS policies with indexes, function wrapping, and query optimization techniques | [RLS Performance Best Practices](/kb/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
+| Check logs | Investigate RLS authorization errors or timeout issues in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Learn authorization basics | Understand how RLS policies work with private channels and best practices for implementation | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
+| Create indexes | Add indexes on columns frequently used in RLS policy conditions to speed up authorization checks | [Database Indexes Guide](/docs/guides/database/postgres/indexes) |
+| Use index advisor | Automatically detect missing indexes that could improve RLS policy performance | [Index Advisor Extension Guide](/docs/guides/database/extensions/index_advisor) |
+| Optimize queries | Learn techniques for optimizing queries including partial indexes and composite indexes for RLS conditions | [Query Optimization Guide](/docs/guides/database/query-optimization) |
+| Monitor database | Review database query performance and identify slow queries that may be affecting RLS execution | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
+| Contact support | Discuss RLS optimization strategies or get assistance with complex authorization requirements | [Support Portal](/dashboard/support/new) |
## (Write) Private Channel Subscription RLS Execution Time
@@ -297,17 +297,17 @@ height={625}
### Actions you can take
-| Action | Description | More information |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| Configure connection pool | Adjust the "Database connection pool size" setting to increase the number of connections available for RLS authorization checks, which can improve performance for high-frequency message publishing | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Optimize RLS policies | Learn how to optimize RLS policies with indexes, function wrapping, and query optimization techniques | [RLS Performance Best Practices](/docs/guides/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
-| Check logs | Investigate RLS authorization errors or timeout issues when publishing messages in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Learn authorization basics | Understand how RLS policies work with private channels for write operations and best practices for implementation | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
-| Create indexes | Add indexes on columns used in INSERT policies to speed up write authorization checks | [Database Indexes Guide](/docs/guides/database/postgres/indexes) |
-| Use index advisor | Automatically detect missing indexes that could improve write RLS policy performance | [Index Advisor Extension Guide](/docs/guides/database/extensions/index_advisor) |
-| Optimize queries | Learn techniques for optimizing INSERT policy queries including partial indexes for specific conditions | [Query Optimization Guide](/docs/guides/database/query-optimization) |
-| Monitor database | Review database query performance and identify slow queries that may be affecting write RLS execution | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
-| Contact support | Discuss RLS optimization strategies or get assistance with complex authorization requirements for high-frequency messaging | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| Configure connection pool | Adjust the "Database connection pool size" setting to increase the number of connections available for RLS authorization checks, which can improve performance for high-frequency message publishing | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Optimize RLS policies | Learn how to optimize RLS policies with indexes, function wrapping, and query optimization techniques | [RLS Performance Best Practices](/kb/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
+| Check logs | Investigate RLS authorization errors or timeout issues when publishing messages in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Learn authorization basics | Understand how RLS policies work with private channels for write operations and best practices for implementation | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
+| Create indexes | Add indexes on columns used in INSERT policies to speed up write authorization checks | [Database Indexes Guide](/docs/guides/database/postgres/indexes) |
+| Use index advisor | Automatically detect missing indexes that could improve write RLS policy performance | [Index Advisor Extension Guide](/docs/guides/database/extensions/index_advisor) |
+| Optimize queries | Learn techniques for optimizing INSERT policy queries including partial indexes for specific conditions | [Query Optimization Guide](/docs/guides/database/query-optimization) |
+| Monitor database | Review database query performance and identify slow queries that may be affecting write RLS execution | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
+| Contact support | Discuss RLS optimization strategies or get assistance with complex authorization requirements for high-frequency messaging | [Support Portal](/dashboard/support/new) |
## Total Requests
@@ -358,18 +358,18 @@ height={645}
### Actions you can take
-| Action | Description | More information |
-| ----------------------- | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Configure limits | Adjust "Max concurrent connections" or "Max events per second" settings if errors are related to quota limits being reached | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Check logs | Investigate specific error messages, error codes, and request details in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Review request volume | Compare error rates with total request volume to calculate error percentages and identify trends | [Total Requests Report](#total-requests) |
-| Understand error codes | Understand specific error codes and their resolutions | [Realtime Error Codes Reference](/docs/guides/realtime/error_codes) |
-| Learn HTTP status codes | Learn about HTTP status codes including 4XX client errors and 5XX server errors | [HTTP Status Codes Troubleshooting](/docs/guides/troubleshooting/http-status-codes) |
-| Fix timeout errors | Resolve WebSocket timeout errors caused by Node.js version incompatibility | [TIMED_OUT Connection Errors Troubleshooting](/docs/guides/troubleshooting/realtime-connections-timed_out-status) |
-| Understand heartbeats | Monitor heartbeat status to detect connection issues and handle timeouts | [Realtime Heartbeats Guide](/docs/guides/troubleshooting/realtime-heartbeat-messages) |
-| Review quotas | Check if errors are related to quota limits (e.g., `too_many_connections`, `too_many_joins`) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
-| Learn authorization | Troubleshoot authorization-related errors for private channels | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
-| Contact support | Get assistance with persistent errors or investigate service-level issues | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| ----------------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Configure limits | Adjust "Max concurrent connections" or "Max events per second" settings if errors are related to quota limits being reached | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Check logs | Investigate specific error messages, error codes, and request details in your project dashboard | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Review request volume | Compare error rates with total request volume to calculate error percentages and identify trends | [Total Requests Report](#total-requests) |
+| Understand error codes | Understand specific error codes and their resolutions | [Realtime Error Codes Reference](/docs/guides/realtime/error_codes) |
+| Learn HTTP status codes | Learn about HTTP status codes including 4XX client errors and 5XX server errors | [HTTP Status Codes Troubleshooting](/kb/troubleshooting/http-status-codes) |
+| Fix timeout errors | Resolve WebSocket timeout errors caused by Node.js version incompatibility | [TIMED_OUT Connection Errors Troubleshooting](/kb/troubleshooting/realtime-connections-timed_out-status) |
+| Understand heartbeats | Monitor heartbeat status to detect connection issues and handle timeouts | [Realtime Heartbeats Guide](/kb/troubleshooting/realtime-heartbeat-messages) |
+| Review quotas | Check if errors are related to quota limits (e.g., `too_many_connections`, `too_many_joins`) | [Realtime Quotas Reference](/docs/guides/realtime/limits) |
+| Learn authorization | Troubleshoot authorization-related errors for private channels | [Realtime Authorization Guide](/docs/guides/realtime/authorization) |
+| Contact support | Get assistance with persistent errors or investigate service-level issues | [Support Portal](/dashboard/support/new) |
## Response Speed
@@ -391,13 +391,13 @@ height={834}
### Actions you can take
-| Action | Description | More information |
-| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| Configure connection pool | Adjust the "Database connection pool size" setting to optimize database connection usage, which can improve response times for authorization checks | [Realtime Settings Guide](/docs/guides/realtime/settings) |
-| Check logs | Investigate slow requests and identify specific endpoints or operations causing delays | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
-| Review request volume | Correlate response times with request volume to identify performance degradation under load | [Total Requests Report](#total-requests) |
-| Monitor database | Review database resource utilization, connection counts, and query performance that may affect response times | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
-| Review benchmarks | Understand expected latency and throughput for different Realtime operations | [Realtime Performance Benchmarks](/docs/guides/realtime/benchmarks) |
-| Understand heartbeats | Monitor heartbeat status and customize intervals to balance detection speed with network overhead | [Realtime Heartbeats Guide](/docs/guides/troubleshooting/realtime-heartbeat-messages) |
-| Optimize RLS policies | If using private channels, optimize RLS policies that may be slowing down authorization checks | [RLS Performance Best Practices](/docs/guides/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
-| Contact support | Discuss performance optimization strategies or investigate persistent latency issues | [Support Portal](/dashboard/support/new) |
+| Action | Description | More information |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| Configure connection pool | Adjust the "Database connection pool size" setting to optimize database connection usage, which can improve response times for authorization checks | [Realtime Settings Guide](/docs/guides/realtime/settings) |
+| Check logs | Investigate slow requests and identify specific endpoints or operations causing delays | [Realtime Logs Dashboard](/dashboard/project/_/database/realtime-logs) |
+| Review request volume | Correlate response times with request volume to identify performance degradation under load | [Total Requests Report](#total-requests) |
+| Monitor database | Review database resource utilization, connection counts, and query performance that may affect response times | [Database Observability Dashboard](/dashboard/project/_/observability/database) |
+| Review benchmarks | Understand expected latency and throughput for different Realtime operations | [Realtime Performance Benchmarks](/docs/guides/realtime/benchmarks) |
+| Understand heartbeats | Monitor heartbeat status and customize intervals to balance detection speed with network overhead | [Realtime Heartbeats Guide](/kb/troubleshooting/realtime-heartbeat-messages) |
+| Optimize RLS policies | If using private channels, optimize RLS policies that may be slowing down authorization checks | [RLS Performance Best Practices](/kb/troubleshooting/rls-performance-and-best-practices-Z5Jjwv) |
+| Contact support | Discuss performance optimization strategies or investigate persistent latency issues | [Support Portal](/dashboard/support/new) |
diff --git a/apps/docs/content/troubleshooting/branch-in-migrations-failed-status.mdx b/apps/docs/content/troubleshooting/branch-in-migrations-failed-status.mdx
index 879a192b77d..5d5038219d1 100644
--- a/apps/docs/content/troubleshooting/branch-in-migrations-failed-status.mdx
+++ b/apps/docs/content/troubleshooting/branch-in-migrations-failed-status.mdx
@@ -83,4 +83,4 @@ Branch creation can fail more than once because more than one migration is out o
If issues persist after repairing migration history, such as schema drift or repeated mismatches, review the [branching troubleshooting documentation](/docs/guides/deployment/branching/troubleshooting#migration-issues) and consider further manual repair with [`supabase migration repair`](/docs/reference/cli/supabase-migration-repair).
-If your migration history has drifted too far out of sync for repairing individual migrations to be practical, consider creating a single baseline migration that encapsulates your production project's current schema instead. The [new branch doesn't copy database troubleshooting guide](/docs/guides/troubleshooting/new-branch-doesnt-copy-database) walks through the commands for setting this up.
+If your migration history has drifted too far out of sync for repairing individual migrations to be practical, consider creating a single baseline migration that encapsulates your production project's current schema instead. The [new branch doesn't copy database troubleshooting guide](/kb/troubleshooting/new-branch-doesnt-copy-database) walks through the commands for setting this up.
diff --git a/apps/docs/content/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted-ddaa1c.mdx b/apps/docs/content/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted-ddaa1c.mdx
index f1e1a8cc694..7c962444a5a 100644
--- a/apps/docs/content/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted-ddaa1c.mdx
+++ b/apps/docs/content/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted-ddaa1c.mdx
@@ -90,7 +90,7 @@ The following table lists what `PUBLIC` holds and whether the `postgres` role ca
| Large-object functions such as `lo_create` | `execute`. A role can create large objects in the database. | No |
| System catalogs such as `pg_class` and `pg_proc` | Read access to the names and definitions of database objects | No |
-The `postgres` role owns the `postgres` database, and through it the `public` schema, so it can revoke the `PUBLIC` grants on those. Supabase roles own the other objects, so a revoke on them prints the `no privileges could be revoked` warning. For the pg_net grants, see [Revoking access to pg_net objects has no effect](/docs/guides/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16).
+The `postgres` role owns the `postgres` database, and through it the `public` schema, so it can revoke the `PUBLIC` grants on those. Supabase roles own the other objects, so a revoke on them prints the `no privileges could be revoked` warning. For the pg_net grants, see [Revoking access to pg_net objects has no effect](/kb/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect).
Extensions you enable can grant more privileges to `PUBLIC`. After you enable an extension, check the role again.
diff --git a/apps/docs/content/troubleshooting/dashboard-errors-when-managing-users-N1ls4A.mdx b/apps/docs/content/troubleshooting/dashboard-errors-when-managing-users-N1ls4A.mdx
index c5d6ece3bb6..417c7d4a3b4 100644
--- a/apps/docs/content/troubleshooting/dashboard-errors-when-managing-users-N1ls4A.mdx
+++ b/apps/docs/content/troubleshooting/dashboard-errors-when-managing-users-N1ls4A.mdx
@@ -72,13 +72,13 @@ These error are normal a side effect of issues in your custom user management lo
Use the hints provided in the error message to fix issues in your custom user management logic.
-**Trigger/trigger function related error messages** - [Solution for trigger related issues](/docs/guides/troubleshooting/dashboard-errors-when-managing-users-N1ls4A#solution-for-trigger-related-issues)
+**Trigger/trigger function related error messages** - [Solution for trigger related issues](/kb/troubleshooting/dashboard-errors-when-managing-users-N1ls4A#solution-for-trigger-related-issues)
```
"error":"error update user`s last_sign_in field: ERROR: permission denied for table profiles (SQLSTATE 42501)"
```
-**Constraint related error message** - [Solution for constraint related issues](/docs/guides/troubleshooting/dashboard-errors-when-managing-users-N1ls4A#solution-for-constraint-related-issues)
+**Constraint related error message** - [Solution for constraint related issues](/kb/troubleshooting/dashboard-errors-when-managing-users-N1ls4A#solution-for-constraint-related-issues)
```
ERROR: 23503: update or delete on table "users" violates foreign key constraint "profiles_id_fkey" on table "profiles"
@@ -91,7 +91,7 @@ DETAIL: Key (id)=(7428a53c-75b7-4531-9ae9-1567d9c4ac0a) is still referenced fro
ERROR: column \"updated_at\" of relation \"profiles\" does not exist (SQLSTATE 42703)
```
-**Broken search path / incorrect name** - [42P01 related solution](/docs/guides/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V)
+**Broken search path / incorrect name** - [42P01 related solution](/kb/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V)
```
failed to close prepared statement: ERROR: current transaction is aborted, commands ignored until end of transaction block (SQLSTATE 25P02): ERROR: relation \"public.profiles\" does not exist (SQLSTATE 42P01)
diff --git a/apps/docs/content/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net-ad6357.mdx b/apps/docs/content/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net-ad6357.mdx
index 62a3c37ee0b..0ac1a4b71f5 100644
--- a/apps/docs/content/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net-ad6357.mdx
+++ b/apps/docs/content/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net-ad6357.mdx
@@ -4,7 +4,7 @@ topics = [ "database" ]
keywords = [ "pg_net", "net", "http_request_queue", "_http_response", "http_post", "headers", "Authorization", "bearer token", "secret key", "service_role", "Vault", "credentials", "Row Level Security" ]
---
-When you call `net.http_get`, `net.http_post`, or `net.http_delete`, pg_net stores the request as a row in `net.http_request_queue`. The row holds the URL, headers, and body until the pg_net worker sends the request. Any role that can use pg_net can read the row while it waits, including an `Authorization` or `apikey` header. For which roles can use pg_net, see [Revoking access to pg_net objects has no effect](/docs/guides/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16#which-roles-can-use-pg_net).
+When you call `net.http_get`, `net.http_post`, or `net.http_delete`, pg_net stores the request as a row in `net.http_request_queue`. The row holds the URL, headers, and body until the pg_net worker sends the request. Any role that can use pg_net can read the row while it waits, including an `Authorization` or `apikey` header. For which roles can use pg_net, see [Revoking access to pg_net objects has no effect](/kb/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect#which-roles-can-use-pg_net).
## Check what your requests expose
diff --git a/apps/docs/content/troubleshooting/exhaust-ram.mdx b/apps/docs/content/troubleshooting/exhaust-ram.mdx
index 51128f0f31e..004512dcd72 100644
--- a/apps/docs/content/troubleshooting/exhaust-ram.mdx
+++ b/apps/docs/content/troubleshooting/exhaust-ram.mdx
@@ -38,7 +38,7 @@ It is also possible to monitor your resources and set up alerts using Prometheus
Everything you do with your Supabase project requires memory in some form. Hence, there can be many reasons for high RAM usage. Here are some common ones:
- **Query performance:** Queries that take a long time to complete (>1 second) could be using your RAM inefficiently. Check our guide on [examining query performance](/docs/guides/platform/performance#examining-query-performance).
-- **Too many connections:** Every connection to your database consumes memory. You can check the number of active connections under [Database Roles](/dashboard/project/_/database/roles) after you select your project. Read our guide on [too many open connections](/docs/guides/troubleshooting/http-api-issues#too-many-open-connections).
+- **Too many connections:** Every connection to your database consumes memory. You can check the number of active connections under [Database Roles](/dashboard/project/_/database/roles) after you select your project. Read our guide on [too many open connections](/kb/troubleshooting/http-api-issues#too-many-open-connections).
- **Extensions:** Some extensions such as `timescaledb` or `pg_cron` can use a lot of memory. It can also add up when you have too many extensions running. You can manage your database extensions in the dashboard under [Extensions](/dashboard/project/_/database/extensions).
## How to fix your memory issues
diff --git a/apps/docs/content/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.mdx b/apps/docs/content/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.mdx
index e10774c29ec..302b7870b9c 100644
--- a/apps/docs/content/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.mdx
+++ b/apps/docs/content/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.mdx
@@ -17,10 +17,10 @@ This error typically happens when the database is overloaded and causing an outa
Review the appropriate guides based on your scenario:
-- [High CPU usage](/docs/guides/troubleshooting/high-cpu-usage)
-- [High RAM usage](/docs/guides/troubleshooting/exhaust-ram)
-- [High Swap usage](/docs/guides/troubleshooting/exhaust-swap)
-- [High Disk I/O](/docs/guides/troubleshooting/exhaust-disk-io)
+- [High CPU usage](/kb/troubleshooting/high-cpu-usage)
+- [High RAM usage](/kb/troubleshooting/exhaust-ram)
+- [High Swap usage](/kb/troubleshooting/exhaust-swap)
+- [High Disk I/O](/kb/troubleshooting/exhaust-disk-io)
- [Query optimization](/docs/guides/database/query-optimization)
You can also set up alerts using a [Prometheus endpoint / Grafana charts](/docs/guides/observability/metrics) to monitor vital resources.
diff --git a/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx b/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
index c7c6890a336..f30be684e71 100644
--- a/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
+++ b/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
@@ -16,17 +16,17 @@ The username depends on how you connect:
- Direct connections and the dedicated pooler use `postgres`.
- Shared pooler connections use `postgres.[PROJECT-REF]`.
-Supplying the wrong one usually produces [Tenant or user not found](/docs/guides/troubleshooting/tenant-or-user-not-found) rather than this error, but a valid username with the wrong password lands here.
+Supplying the wrong one usually produces [Tenant or user not found](/kb/troubleshooting/tenant-or-user-not-found) rather than this error, but a valid username with the wrong password lands here.
## Check the password
Reserved characters in a password have to be [percent-encoded](https://en.wikipedia.org/wiki/Percent-encoding) when they appear in a connection string. This covers `&`, `#`, `?`, and spaces, among others. A password that works in a GUI field can fail in a URI for this reason alone.
-If you don't have the password, [reset it](/docs/guides/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB) in [Database settings](/dashboard/project/_/database/settings).
+If you don't have the password, [reset it](/kb/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB) in [Database settings](/dashboard/project/_/database/settings).
## Rotated the password?
-If you're connecting through the shared pooler and this started right after resetting the role's password — with the username and password otherwise correct — see [Supavisor error: "password authentication failed" after rotating database password](/docs/guides/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation).
+If you're connecting through the shared pooler and this started right after resetting the role's password — with the username and password otherwise correct — see [Supavisor error: "password authentication failed" after rotating database password](/kb/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation).
## Using a custom role
@@ -34,12 +34,12 @@ If you're connecting through the shared pooler and this started right after rese
If you reset the password of a custom role while using the shared pooler (Supavisor), a pooled connection can still fail with `FATAL: password authentication failed` (SQLSTATE `28P01`) even when the new password is correct. The pooler may still use cached credentials briefly. Confirm the new password with a direct connection, then retry through Supavisor with bounded retries. Direct connections and the dedicated pooler are not affected by this cache behavior.
-For the full rotation flow, see [Supavisor error: "password authentication failed" after rotating database password](/docs/guides/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation).
+For the full rotation flow, see [Supavisor error: "password authentication failed" after rotating database password](/kb/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation).
## Repeated failures cause a different error
-Repeated authentication failures from the same address get that address banned. Once banned, connections stop failing with this error and start failing with [connection refused](/docs/guides/troubleshooting/error-connection-refused-when-trying-to-connect-to-supabase-database-hwG0Dr) instead.
+Repeated authentication failures from the same address get that address banned. Once banned, connections stop failing with this error and start failing with [connection refused](/kb/troubleshooting/error-connection-refused-when-trying-to-connect-to-supabase-database-hwG0Dr) instead.
If your error changes from authentication failed to connection refused while you're testing credentials, you're banned rather than locked out. That page has the unban procedure.
-This applies to direct connections and the dedicated pooler. The shared pooler has its own separate mechanism for repeated failures: instead of a banned IP, you'll see `FATAL: Circuit breaker open`. See [Supavisor error: "Circuit breaker open" after password rotation](/docs/guides/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72).
+This applies to direct connections and the dedicated pooler. The shared pooler has its own separate mechanism for repeated failures: instead of a banned IP, you'll see `FATAL: Circuit breaker open`. See [Supavisor error: "Circuit breaker open" after password rotation](/kb/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation).
diff --git a/apps/docs/content/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB.mdx b/apps/docs/content/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB.mdx
index 3f5a572b90f..cc53998cc6b 100644
--- a/apps/docs/content/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB.mdx
+++ b/apps/docs/content/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB.mdx
@@ -9,4 +9,4 @@ database_id = "6e4a515c-5e70-4b92-808c-f076d47d4e35"
You can reset your database password from the [**Database > Settings**](/dashboard/project/_/database/settings) section of the Dashboard.
-If connections through the [Shared Pooler (Supavisor)](/docs/guides/database/connecting-to-postgres) start failing right after you reset it — including for the built-in `postgres` role — this `28P01` error is expected, and retrying with the new password usually succeeds. See [Supavisor error: "password authentication failed" after rotating database password](/docs/guides/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation) for more detail.
+If connections through the [Shared Pooler (Supavisor)](/docs/guides/database/connecting-to-postgres) start failing right after you reset it — including for the built-in `postgres` role — this `28P01` error is expected, and retrying with the new password usually succeeds. See [Supavisor error: "password authentication failed" after rotating database password](/kb/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation) for more detail.
diff --git a/apps/docs/content/troubleshooting/identify-lovable-cloud-or-supabase-backend.mdx b/apps/docs/content/troubleshooting/identify-lovable-cloud-or-supabase-backend.mdx
index 084a2bdf19a..71f13e838f8 100644
--- a/apps/docs/content/troubleshooting/identify-lovable-cloud-or-supabase-backend.mdx
+++ b/apps/docs/content/troubleshooting/identify-lovable-cloud-or-supabase-backend.mdx
@@ -108,7 +108,7 @@ If the page displays the Supabase icon, your Supabase project name, and some lin
You can create a new Supabase project and migrate your data manually.
- See [Can't Access Your Supabase Project When Using Lovable Cloud](/docs/guides/troubleshooting/cant-access-supabase-project-lovable-cloud) for more details.
+ See [Can't Access Your Supabase Project When Using Lovable Cloud](/kb/troubleshooting/cant-access-supabase-project-lovable-cloud) for more details.
</AccordionItem>
@@ -119,7 +119,7 @@ If the page displays the Supabase icon, your Supabase project name, and some lin
That's expected — Lovable Cloud backend is managed by Lovable and doesn't appear in your Supabase Dashboard.
- Learn more in [Can't Access Your Supabase Project When Using Lovable Cloud](/docs/guides/troubleshooting/cant-access-supabase-project-lovable-cloud).
+ Learn more in [Can't Access Your Supabase Project When Using Lovable Cloud](/kb/troubleshooting/cant-access-supabase-project-lovable-cloud).
</AccordionItem>
diff --git a/apps/docs/content/troubleshooting/pg_dump-fails-with-query-would-be-affected-by-row-level-security-policy-1d5783.mdx b/apps/docs/content/troubleshooting/pg_dump-fails-with-query-would-be-affected-by-row-level-security-policy-1d5783.mdx
index ebe1f9b77f1..e92de02b434 100644
--- a/apps/docs/content/troubleshooting/pg_dump-fails-with-query-would-be-affected-by-row-level-security-policy-1d5783.mdx
+++ b/apps/docs/content/troubleshooting/pg_dump-fails-with-query-would-be-affected-by-row-level-security-policy-1d5783.mdx
@@ -101,7 +101,7 @@ A session as `backup_reader` can still write in these ways:
- If the pg_net extension is enabled, the session can add rows to `net.http_request_queue`, which pg_net sends as HTTP requests. The role receives this privilege from `PUBLIC`.
- The session can create large objects with functions such as `lo_create`, which `PUBLIC` can run.
-For the full list of privileges every role receives, see [Custom role inherits privileges that were not explicitly granted](/docs/guides/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted-ddaa1c#what-every-role-receives-from-public).
+For the full list of privileges every role receives, see [Custom role inherits privileges that were not explicitly granted](/kb/troubleshooting/custom-role-inherits-privileges-that-were-not-explicitly-granted#what-every-role-receives-from-public).
## Rotate the password
diff --git a/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx b/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
index 757491852ba..71244f23011 100644
--- a/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
+++ b/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
@@ -10,7 +10,7 @@ If the project was recently restored, it can take up a couple minutes to become
Services rely on the backend database. Unhealthy services can indicate a database being overloaded due to being undersized or not tuned appropriately.
-- Review this [troubleshooting doc](/docs/guides/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout) to determine if it could be a resource issue.
+- Review this [troubleshooting doc](/kb/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout) to determine if it could be a resource issue.
- If services recover and become unhealthy again, there is likely a repeated issue overloading the database.
Possible resolutions:
diff --git a/apps/docs/content/troubleshooting/realtime-isolating-server-side-vs-client-side-issues-with-inspector-and-devtools.mdx b/apps/docs/content/troubleshooting/realtime-isolating-server-side-vs-client-side-issues-with-inspector-and-devtools.mdx
index b08d234617e..916bf43d71f 100644
--- a/apps/docs/content/troubleshooting/realtime-isolating-server-side-vs-client-side-issues-with-inspector-and-devtools.mdx
+++ b/apps/docs/content/troubleshooting/realtime-isolating-server-side-vs-client-side-issues-with-inspector-and-devtools.mdx
@@ -23,12 +23,12 @@ For `broadcast`, you can trigger the message directly from Inspector. For `prese
**If the test fails as `postgres`:**
-- For `postgres_changes`, see [Realtime: Postgres Changes Troubleshooting](/docs/guides/troubleshooting/realtime-postgres-changes-troubleshooting#step-1-is-the-table-in-the-realtime-publication). It covers publication membership and other server-side configuration.
+- For `postgres_changes`, see [Realtime: Postgres Changes Troubleshooting](/kb/troubleshooting/realtime-postgres-changes-troubleshooting#step-1-is-the-table-in-the-realtime-publication). It covers publication membership and other server-side configuration.
- For `broadcast` or `presence`, the failure occurs before authorization. Verify that the trigger or send call is firing.
**If the test succeeds as `postgres` but fails as the authenticated user:**
-- For `postgres_changes`, the issue is likely related to RLS. See [Realtime: Postgres Changes Troubleshooting](/docs/guides/troubleshooting/realtime-postgres-changes-troubleshooting#step-2-is-rls-quietly-blocking-the-row) for guidance on testing and fixing policies.
+- For `postgres_changes`, the issue is likely related to RLS. See [Realtime: Postgres Changes Troubleshooting](/kb/troubleshooting/realtime-postgres-changes-troubleshooting#step-2-is-rls-quietly-blocking-the-row) for guidance on testing and fixing policies.
- For `broadcast` or `presence`, the issue is likely related to channel authorization on `realtime.messages` for that role. Review the [policy examples in the Realtime Authorization docs](/docs/guides/realtime/authorization?queryGroups=language&language=js#examples). Also check whether a complex policy is causing authorization checks to run slowly or time out.
**If both tests succeed:** The Realtime server and Postgres are working as expected. The issue is likely in the client or network path. Continue to Step 2.
@@ -37,7 +37,7 @@ For `broadcast`, you can trigger the message directly from Inspector. For `prese
Check for these common configuration issues:
-- **`postgres_changes`:** Confirm that the filter, schema, table, and event type match. See the "Check the subscription code itself" section of [Realtime: Postgres Changes Troubleshooting](/docs/guides/troubleshooting/realtime-postgres-changes-troubleshooting#step-4-check-the-subscription-code-itself) for common mismatches.
+- **`postgres_changes`:** Confirm that the filter, schema, table, and event type match. See the "Check the subscription code itself" section of [Realtime: Postgres Changes Troubleshooting](/kb/troubleshooting/realtime-postgres-changes-troubleshooting#step-4-check-the-subscription-code-itself) for common mismatches.
- **`broadcast`:** Confirm that the sender and receiver use the same topic and event name.
- **`presence`:** Confirm that `track()` is called after the channel reaches `SUBSCRIBED` and that all clients use the same channel name.
diff --git a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
index 8af13dc5e4f..3287d75b6d9 100644
--- a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
+++ b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
@@ -29,7 +29,7 @@ Suspension is not automatic and is applied after review. The goal is to protect
In most cases, quota overages are accidental rather than intentional:
- **Reconnection loops**: A client that fails to authenticate or subscribe may retry rapidly, creating thousands of short-lived connections
-- **Uncontrolled channels**: Creating channels without cleaning them up leads to resource exhaustion (see [Fixing the TooManyChannels Error](/docs/guides/troubleshooting/realtime-too-many-channels-error))
+- **Uncontrolled channels**: Creating channels without cleaning them up leads to resource exhaustion (see [Fixing the TooManyChannels Error](/kb/troubleshooting/realtime-too-many-channels-error))
- **Missing cleanup on component tear down**: Single-page applications that don't unsubscribe when components are removed can accumulate connections over time
- **Unexpected traffic spikes**: A viral event or bot traffic can push usage well beyond normal levels
- **Development or testing misconfiguration**: Load tests or staging environments accidentally pointed at a production project
@@ -56,15 +56,15 @@ The Supabase team will review your case to understand whether the usage was acci
- Monitor your usage regularly through the [Realtime reports](/dashboard/project/_/database/realtime-logs) page
- Set up alerts if your connections or messages approach your plan limits
-- Follow the [channel management best practices](/docs/guides/troubleshooting/realtime-too-many-channels-error#best-practices-for-channel-management) to avoid resource leaks
+- Follow the [channel management best practices](/kb/troubleshooting/realtime-too-many-channels-error#best-practices-for-channel-management) to avoid resource leaks
- Review the [Realtime limits](/docs/guides/realtime/limits) for your plan and upgrade before you outgrow them
- Use the [Realtime Inspector](https://realtime.supabase.com/inspector/new) to test and debug connections before deploying
## Related troubleshooting guides
-- [Fixing the TooManyChannels Error](/docs/guides/troubleshooting/realtime-too-many-channels-error) — channel lifecycle management and cleanup best practices
-- [Concurrent Peak Connections quota](/docs/guides/troubleshooting/realtime-concurrent-peak-connections-quota-jdDqcp) — understanding the concurrent connections quota and how to adjust it
-- [Handling Silent Disconnections in Background Applications](/docs/guides/troubleshooting/realtime-handling-silent-disconnections-in-backgrounded-applications-592794) — fixing WebSocket drops caused by browser or OS background mode
-- [TIMED_OUT connection errors](/docs/guides/troubleshooting/realtime-connections-timed_out-status) — resolving Node.js version incompatibilities
-- [Debug Realtime with Logger and Log Levels](/docs/guides/troubleshooting/realtime-debugging-with-logger) — enabling client-side logging to diagnose connection and message issues
-- [Realtime Heartbeat Messages](/docs/guides/troubleshooting/realtime-heartbeat-messages) — monitoring connection health with heartbeat callbacks
+- [Fixing the TooManyChannels Error](/kb/troubleshooting/realtime-too-many-channels-error) — channel lifecycle management and cleanup best practices
+- [Concurrent Peak Connections quota](/kb/troubleshooting/realtime-concurrent-peak-connections-quota-jdDqcp) — understanding the concurrent connections quota and how to adjust it
+- [Handling Silent Disconnections in Background Applications](/kb/troubleshooting/realtime-handling-silent-disconnections-in-backgrounded-applications) — fixing WebSocket drops caused by browser or OS background mode
+- [TIMED_OUT connection errors](/kb/troubleshooting/realtime-connections-timed_out-status) — resolving Node.js version incompatibilities
+- [Debug Realtime with Logger and Log Levels](/kb/troubleshooting/realtime-debugging-with-logger) — enabling client-side logging to diagnose connection and message issues
+- [Realtime Heartbeat Messages](/kb/troubleshooting/realtime-heartbeat-messages) — monitoring connection health with heartbeat callbacks
diff --git a/apps/docs/content/troubleshooting/resolving-permission-denied-for-database-postgres-during-migrations-78f33a.mdx b/apps/docs/content/troubleshooting/resolving-permission-denied-for-database-postgres-during-migrations-78f33a.mdx
index 4ced34e7193..e5f546fe8a4 100644
--- a/apps/docs/content/troubleshooting/resolving-permission-denied-for-database-postgres-during-migrations-78f33a.mdx
+++ b/apps/docs/content/troubleshooting/resolving-permission-denied-for-database-postgres-during-migrations-78f33a.mdx
@@ -26,4 +26,4 @@ Replace `example_role` with the name of the role being assumed during the migrat
## Related
-If this happened via a REST/GraphQL request instead of a direct connection or migration script, see [Database API 42501 errors](/docs/guides/troubleshooting/database-api-42501-errors) instead — that guide covers a different set of causes specific to the Data API.
+If this happened via a REST/GraphQL request instead of a direct connection or migration script, see [Database API 42501 errors](/kb/troubleshooting/database-api-42501-errors) instead — that guide covers a different set of causes specific to the Data API.
diff --git a/apps/docs/content/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16.mdx b/apps/docs/content/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16.mdx
index acfb88d3a08..b43666564de 100644
--- a/apps/docs/content/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16.mdx
+++ b/apps/docs/content/troubleshooting/revoking-access-to-pg_net-objects-has-no-effect-0bbc16.mdx
@@ -79,7 +79,7 @@ The following table shows how each kind of role can reach the `net` schema.
On some projects, only `postgres`, `anon`, `authenticated`, `service_role`, and `supabase_functions_admin` can call `net.http_get` and `net.http_post`. For the events that revoke `execute` from `PUBLIC`, see [When the default grants are applied](#when-the-default-grants-are-applied). A role you create can still add rows to the queue, and the worker sends them. To check a role, run the `has_function_privilege` query from [Check which roles have access](#check-which-roles-have-access).
-A row in `net.http_request_queue` holds the request's URL, headers, and body until the pg_net worker sends it. To check what a queued request exposes, see [Database roles can read request headers queued by pg_net](/docs/guides/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net-ad6357).
+A row in `net.http_request_queue` holds the request's URL, headers, and body until the pg_net worker sends it. To check what a queued request exposes, see [Database roles can read request headers queued by pg_net](/kb/troubleshooting/database-roles-can-read-request-headers-queued-by-pg_net).
## Limit pg_net access on your project
diff --git a/apps/docs/content/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72.mdx b/apps/docs/content/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72.mdx
index f3120deee03..84bab77a082 100644
--- a/apps/docs/content/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72.mdx
+++ b/apps/docs/content/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72.mdx
@@ -32,4 +32,4 @@ To avoid this IP lockout issue in the future, stop application instances before
**See also:**
-- [Supavisor error: "password authentication failed" after rotating database password](/docs/guides/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation)
+- [Supavisor error: "password authentication failed" after rotating database password](/kb/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation)
diff --git a/apps/docs/content/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation.mdx b/apps/docs/content/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation.mdx
index 9daa3d2869d..230dc9e855c 100644
--- a/apps/docs/content/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation.mdx
+++ b/apps/docs/content/troubleshooting/supavisor-error-password-authentication-failed-after-password-rotation.mdx
@@ -30,7 +30,7 @@ This applies to regular database roles authenticating with a username/password (
These steps cover the pooler-side caching delay, which resolves on its own.
-Separately, if application instances keep connecting with the old password after changing an existing role's credential, those failed attempts can trip the [auth circuit breaker](/docs/guides/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72), blocking connections from that client and disrupting the system further.
+Separately, if application instances keep connecting with the old password after changing an existing role's credential, those failed attempts can trip the [auth circuit breaker](/kb/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation), blocking connections from that client and disrupting the system further.
To roll out a password change without downtime, create a new custom role with the new password alongside the existing one, migrate your clients over to it gradually, then retire the old role once every client has switched.
@@ -44,6 +44,6 @@ To roll out a password change without downtime, create a new custom role with th
**See also:**
-- [FATAL: Password authentication failed](/docs/guides/troubleshooting/fatal-password-authentication-failed)
-- [Supavisor error: "Circuit breaker open" after password rotation](/docs/guides/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation-0fdb72).
-- [Resetting a Supabase database password](/docs/guides/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB)
+- [FATAL: Password authentication failed](/kb/troubleshooting/fatal-password-authentication-failed)
+- [Supavisor error: "Circuit breaker open" after password rotation](/kb/troubleshooting/supavisor-error-circuit-breaker-open-after-password-rotation).
+- [Resetting a Supabase database password](/kb/troubleshooting/how-do-i-reset-my-supabase-database-password-oTs5sB)
diff --git a/apps/docs/data/errorCodes/realtimeErrorCodes.json b/apps/docs/data/errorCodes/realtimeErrorCodes.json
index efe6c1baf93..9530aaf541f 100644
--- a/apps/docs/data/errorCodes/realtimeErrorCodes.json
+++ b/apps/docs/data/errorCodes/realtimeErrorCodes.json
@@ -55,7 +55,7 @@
"resolution": "Your project may have been suspended for exceeding usage quotas. Contact support with your project reference ID and a description of your Realtime use case.",
"references": [
{
- "href": "/docs/guides/troubleshooting/realtime-project-suspended-for-exceeding-quotas",
+ "href": "/kb/troubleshooting/realtime-project-suspended-for-exceeding-quotas",
"description": "Troubleshooting guide for suspended projects"
}
]
@@ -243,7 +243,7 @@
"resolution": "Reserve Presence for slow-changing state and use Broadcast for high-frequency updates such as live cursors, or throttle your track() calls.",
"references": [
{
- "href": "/docs/guides/troubleshooting/realtime-client-presence-rate-limit-reached",
+ "href": "/kb/troubleshooting/realtime-client-presence-rate-limit-reached",
"description": "Troubleshooting guide for the ClientPresenceRateLimitReached error"
}
]
diff --git a/apps/docs/data/health-advisors.data.ts b/apps/docs/data/health-advisors.data.ts
index 7f5254eb35c..33e75aab4a0 100644
--- a/apps/docs/data/health-advisors.data.ts
+++ b/apps/docs/data/health-advisors.data.ts
@@ -14,7 +14,7 @@ export const healthAdvisors = [
### How to Resolve
-Pull up to five recent 5xx responses on \`/rest/v1\` paths from \`edge_logs\` with their IDs, timestamps, and status. You can use [Logs](/dashboard/project/_/logs/edge-logs) in Studio, the MCP [\`query_logs\`](/docs/guides/observability/advanced-log-filtering#mcp) tool, or the [Management API](/docs/guides/observability/advanced-log-filtering#api). Then follow [API error troubleshooting](/docs/guides/troubleshooting/discovering-and-interpreting-api-errors-in-the-logs-7xREI9).`,
+Pull up to five recent 5xx responses on \`/rest/v1\` paths from \`edge_logs\` with their IDs, timestamps, and status. You can use [Logs](/dashboard/project/_/logs/edge-logs) in Studio, the MCP [\`query_logs\`](/docs/guides/observability/advanced-log-filtering#mcp) tool, or the [Management API](/docs/guides/observability/advanced-log-filtering#api). Then follow [API error troubleshooting](/kb/troubleshooting/discovering-and-interpreting-api-errors-in-the-logs-7xREI9).`,
},
{
path: 'log_auth_error_rate_high',
diff --git a/apps/docs/style-guide/03-page-structure.md b/apps/docs/style-guide/03-page-structure.md
index 7e7ae1d0bd8..84594ff235d 100644
--- a/apps/docs/style-guide/03-page-structure.md
+++ b/apps/docs/style-guide/03-page-structure.md
@@ -24,13 +24,13 @@ Apply this document when you add a page or move content around on an existing on
Supabase docs contain five types of document. Decide which one you need before you start
writing.
-| Type | Purpose | Contains | Doesn't contain | Example |
-| --------------- | --------------------------- | ----------------------------------- | -------------------------------- | ---------------------------------------------------------------------------------- |
-| Explainer | Learn a topic | What it is, why, and when to use it | Instructions | [Auth architecture](/docs/guides/auth/architecture) |
-| Tutorial | Finish a multi-feature goal | Procedures plus the reasoning | — | [Build a Next.js app](/docs/guides/getting-started/tutorials/with-nextjs) |
-| Guide | Finish one task | Procedures in sequence | Background; link to an explainer | [Passwordless logins](/docs/guides/auth/auth-email-passwordless) |
-| Reference | Look something up | Parameters, return types, samples | Context and use cases | [JavaScript client](/docs/reference/javascript/introduction) |
-| Troubleshooting | Resolve one error | The symptom, the cause, the fix | Feature overviews | [Too many channels](/docs/guides/troubleshooting/realtime-too-many-channels-error) |
+| Type | Purpose | Contains | Doesn't contain | Example |
+| --------------- | --------------------------- | ----------------------------------- | -------------------------------- | ------------------------------------------------------------------------- |
+| Explainer | Learn a topic | What it is, why, and when to use it | Instructions | [Auth architecture](/docs/guides/auth/architecture) |
+| Tutorial | Finish a multi-feature goal | Procedures plus the reasoning | — | [Build a Next.js app](/docs/guides/getting-started/tutorials/with-nextjs) |
+| Guide | Finish one task | Procedures in sequence | Background; link to an explainer | [Passwordless logins](/docs/guides/auth/auth-email-passwordless) |
+| Reference | Look something up | Parameters, return types, samples | Context and use cases | [JavaScript client](/docs/reference/javascript/introduction) |
+| Troubleshooting | Resolve one error | The symptom, the cause, the fix | Feature overviews | [Too many channels](/kb/troubleshooting/realtime-too-many-channels-error) |
Reference content is generated from spec files rather than hand-authored. See
[CONTRIBUTING.md](../CONTRIBUTING.md) for the reference pipeline.