Running kardscm sync fails immediately on the first page fetch with a DNS resolution error. The endpoint api.kards.com appears to be unreachable — not just from this tool, but from a browser and direct DNS lookup as well.
Steps to reproduce:
uv run kardscm sync
Error:
ConnectError: [Errno 11001] getaddrinfo failed
Failing on POST https://api.kards.com/graphql at page 1 (offset=0), inside kardscm/scraping/fetcher.py → fetch_all_cards.
Environment:
OS: Windows
Python: 3.12 (via uv-managed interpreter)
kardscm: 0.9.0 (installed via git clone + uv sync)
Install method: cloned repo, uv sync, uv run kardscm sync
Additional diagnostics:
https://www.kards.com loads fine in browser
https://api.kards.com/graphql fails to load in browser directly ("can't reach this page")
Resolve-DnsName api.kards.com returns a CNAME to horizontal-pandsy-.herokudns.com, but no resolved A record — the DNS chain appears to dead-end at Heroku's DNS without returning an IP
General DNS resolution works fine (google.com resolves correctly)
This looks like an issue on the API host's side (possibly a Heroku custom-domain/DNS misconfiguration or the app being suspended), rather than a client-side networking problem, but flagging here in case others are seeing the same thing or there's a known status update.
Running kardscm sync fails immediately on the first page fetch with a DNS resolution error. The endpoint api.kards.com appears to be unreachable — not just from this tool, but from a browser and direct DNS lookup as well.
Steps to reproduce:
uv run kardscm sync
Error:
ConnectError: [Errno 11001] getaddrinfo failed
Failing on POST https://api.kards.com/graphql at page 1 (offset=0), inside kardscm/scraping/fetcher.py → fetch_all_cards.
Environment:
OS: Windows
Python: 3.12 (via uv-managed interpreter)
kardscm: 0.9.0 (installed via git clone + uv sync)
Install method: cloned repo, uv sync, uv run kardscm sync
Additional diagnostics:
https://www.kards.com loads fine in browser
https://api.kards.com/graphql fails to load in browser directly ("can't reach this page")
Resolve-DnsName api.kards.com returns a CNAME to horizontal-pandsy-.herokudns.com, but no resolved A record — the DNS chain appears to dead-end at Heroku's DNS without returning an IP
General DNS resolution works fine (google.com resolves correctly)
This looks like an issue on the API host's side (possibly a Heroku custom-domain/DNS misconfiguration or the app being suspended), rather than a client-side networking problem, but flagging here in case others are seeing the same thing or there's a known status update.