Supavisor connection error: FATAL: (EAUTHQUERY) unsupported or invalid secret format
Last edited: 10/14/2026
如果你在连接 Supavisor 连接池(端口 5432 或 6543)时遇到 FATAL: (EAUTHQUERY) unsupported or invalid secret format 错误,这通常表示数据库角色的凭据有问题。
🌐 If you are observing a FATAL: (EAUTHQUERY) unsupported or invalid secret format error when connecting to the Supavisor pooler (ports 5432 or 6543), it typically indicates an issue with the database role's credentials.
这为什么会发生? #
🌐 Why does this happen?
当用于连接的自定义 Postgres 角色的 VALID UNTIL 时间戳过期时,就会出现此错误。当角色过期时,Supavisor 使用的内部认证查询会返回一个空的密码密钥,这会阻止连接池完成 SCRAM 认证过程。
🌐 This error occurs when the custom Postgres role used for the connection has an expired VALID UNTIL timestamp. When a role is expired, the internal authentication query used by Supavisor returns a null password secret, which prevents the pooler from completing the SCRAM authentication process.
如何解决这个问题 #
🌐 How to resolve this issue
你可以通过 SQL 编辑器 验证并更新角色的到期状态:
🌐 You can verify and update the role's expiration status via the SQL editor:
-
通过运行以下查询来确认角色是否已过期:
select rolname, rolvaliduntil, rolvaliduntil < now() as expiredfrom pg_authidwhere rolname = 'example_role'; -
如果
expired列返回 true,就更新角色以延长或移除过期限制:ALTER ROLE example_role VALID UNTIL 'infinity'; -
使用你的 Supavisor 连接字符串重新尝试连接。
如果问题仍然存在或角色未过期,请联系 supabase.help 寻求帮助。
🌐 If the issue persists or the role is not expired, reach out to supabase.help for assistance.