Skip to content

Public registry Supabase hostname does not resolve #3

Description

@BennyWnj

The built-in public registry URL currently appears unreachable because the configured Supabase hostname does not resolve in DNS.

Reproduction

From a fresh clone of this repo:

python3 scripts/search.py --list-all --limit 5

Observed result:

ERROR: Supabase GET network error: <urlopen error [Errno 8] nodename nor servname provided, or not known>

Direct curl with the anon key from scripts/lib/supabase.py fails before any HTTP/auth response:

curl -v \
  'https://ptwosnmrcfwmfnluufww.supabase.co/rest/v1/skills?select=name,variant&limit=5' \
  -H 'apikey: sb_publishable_BNikqoeKRZEp2FSqAOJu4A_pJ0UBzby' \
  -H 'Authorization: Bearer sb_publishable_BNikqoeKRZEp2FSqAOJu4A_pJ0UBzby'

Observed result:

Could not resolve host: ptwosnmrcfwmfnluufww.supabase.co

I also checked DNS resolution directly; supabase.co resolves, but ptwosnmrcfwmfnluufww.supabase.co returns NXDOMAIN.

Expected

The zero-config public registry described in the README should be reachable, and scripts/search.py --list-all --limit 5 should return registry results or an empty JSON result.

Possible cause

The Supabase project may have been deleted, paused, renamed, or the hardcoded project ref in scripts/lib/supabase.py may be stale.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions