Add support for ipv6-only servers #259

open

opened by

jmml.tngl.sh edited 2 months ago

When trying to create a repository on my knot I get:

time=2025-10-10T01:17:13.264+03:00 level=ERROR msg="signature verification failed" command=knot url=/xrpc/sh.tangled.repo.create err="token is unverifiable: error while executing keyfunc: token has invalid issuer: resolving DID (did:plc:mytoken): DID resolution failed: PLC directory lookup: Get \"https://plc.directory/did:plc:mytoken\": dial tcp 18.217.126.127:443: connect: network is unreachable"

The server only has ipv6 connectivity but plc.directory only supports ipv4.

$ curl -I https://plc.directory 
HTTP/2 302

$ curl -6 -I https://plc.directory
curl: (6) Could not resolve host: plc.directory

oppi.li 2mo ago

we could allow switching to a different directory, i can check to see if there are any ipv6 directories available.

oppi.li 2mo ago

i've been told that https://plc.wtf has ipv6 support, so all that is really needed is to add support for configuring alternate directories in our id resolver.

jmml.tngl.sh (author) 2mo ago

Thanks. For now I've used dnsmasq&NAT64 to work around it. While doing that I also found tngl.sh is ipv4 only.

Labels

good-first-issue

area

appview

knot

spindle

assignee

None yet.

Participants 2

AT URI

at://did:plc:7mrh6ioxcrywejc4fthk2oqy/sh.tangled.repo.issue/3m2s7nc4vpj22