Supabase Session Pooler hostname shows "hidden" in Dashboard

[vmora18-hub]

Hello Supabase community,

I'm trying to create a PostgreSQL backup of a Supabase Free Plan project using pg_dump from macOS.

Problem

In Dashboard → Connect → Session pooler, the hostname displays literally as hidden.

Clicking the copy icon also copies hidden, rather than a valid hostname.

Environment

• Supabase region: West US (Oregon)
• Supabase plan: Free
• PostgreSQL server: 17.11
• PostgreSQL client: 18.1 on macOS
• Session pooler port: 5432
• IPv4 connectivity: Available
• Direct PostgreSQL IPv6 connection: No route to host

Troubleshooting already performed

1. Refreshed the Dashboard.
2. Tried different connection string formats.
3. Tried an incognito browser window.
4. Confirmed IPv4 HTTPS connectivity.
5. Verified that the direct database hostname has an IPv6 DNS record, but IPv6 connections fail because there is no network route.

The Session pooler hostname remains hidden.

Questions

1. Is this a known Dashboard issue?
2. Is there an official alternative way to retrieve the correct Session pooler hostname?
3. What TLS certificate verification method is recommended for pg_dump through the Session pooler?

I have also submitted a Supabase support request: SU-540617.

I don't want to reset my database password or change my project configuration.

Thank you for your help!

[GaryAustin1]

Not a known issue and does not appear in any search.
Try a different browser?
Does the Transaction pooler show info? It is the same except for port number.

This screen?

[YOYOMAII]

There is an official read-only alternative for getting the hostname: the Management API's Get pooler config endpoint.

curl --fail --silent --show-error \
  "https://api.supabase.com/v1/projects/$PROJECT_REF/config/database/pooler" \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN"

Use a personal access token with permission to read the project's pooling configuration, rather than an anon/publishable key. The response includes connection_string; take the hostname from the primary database's entry. For the shared pooler's session mode, use port 5432. This avoids guessing a hostname from the region.

For pg_dump, Supabase documents sslmode=verify-full with the CA certificate downloaded from Database settings → SSL Configuration:

pg_dump "host=YOUR_POOLER_HOST port=5432 dbname=postgres user=postgres.YOUR_PROJECT_REF sslmode=verify-full sslrootcert=/path/to/prod-supabase.cer" \
  -W --format=custom --file=backup.dump

Supabase's SSL connection example uses the same pooler setup. Neither step requires a password reset or a project configuration change. If the API also returns hidden or no usable connection string, include that result in your existing support ticket; this doesn't establish what's causing the Dashboard display issue.

[sunriseinkyoto]

Something else is already bound to that port.

Windows: netstat -ano | findstr :<port> then stop that PID.
Linux/macOS: lsof -i :<port> / ss -ltnp | grep <port>.
Or change the app port in env/config and retry. Docker: also check host port mappings in compose.

[fedyfsgerana]

Hi,

Since you're on the Free Plan and your network only supports IPv4, using the Shared Session Pooler on port 5432 is the correct approach.

A few things I would suggest:

1. Try accessing the connection details through Dashboard → Connect → Session Pooler and check whether the hostname is still displayed as "hidden" after refreshing the project dashboard.

2. You can also check the official Supabase connection documentation to understand the expected hostname format. However, I would not recommend guessing the pooler hostname based only on the region, because the pooler cluster index can vary.

3. For TLS, I recommend using sslmode=verify-full with the Supabase root certificate downloaded from Database Settings. This verifies both the certificate authority and hostname, rather than only encrypting the connection.

4. Since you're using pg_dump, make sure you use the actual Session Pooler hostname, port 5432, and the pooler username format postgres.[PROJECT_REF].

If the Dashboard continues to return the literal value "hidden", I think this should be investigated by Supabase support. They may need to verify whether the pooler endpoint is correctly provisioned for your project.

I would avoid resetting the database password or recreating the project, as neither action is an appropriate first step for a hostname display or DNS issue.

Hopefully the support team can resolve this without affecting your existing database.

Thanks!