Alternative relays to iroh provided infra #12

New Issue

2026-06-29T13:05:42Z

cblgh commented

2026-06-29 13:05:42 +00:00

I've been working on a thing using iroh-go (more details forthcoming Soon) and have been pretty rapidly running a command, doing some tweaks, then running the command again and so on and so forth. And in so doing I think I might've been rate-limited by iroh's relays? 😅 At least, when the client is trying to connect to the server endpoint I now run into this:

panic: No addressing information available
        Caused by: 
            All address lookup services failed or produced no results
            Service 'dns' failed: no calls succeeded: [Failed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT record]

tldr time to run some own relays? a friend did this and it was supposedly easy once one has iroh-relay checked out

update: only get this on my laptop though and not my server (which is on the same local network). hmmmm

I've been working on a thing using iroh-go (more details forthcoming Soon) and have been pretty rapidly running a command, doing some tweaks, then running the command again and so on and so forth. And in so doing I think I might've been rate-limited by iroh's relays? 😅 At least, when the client is trying to connect to the server endpoint I now run into this: ``` panic: No addressing information available Caused by: All address lookup services failed or produced no results Service 'dns' failed: no calls succeeded: [Failed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT recordFailed to resolve TXT record] ``` tldr time to run some own relays? a friend did this and it was supposedly easy once one has [`iroh-relay`](https://github.com/n0-computer/iroh/tree/main/iroh-relay) checked out update: only get this on my laptop though and not my server (which is on the same local network). hmmmm

👀 1

cblgh commented

2026-06-29 13:11:18 +00:00

Also just mentioning this here as a future todo for myself / documenting having run into the above issue! Running community-funded & -governed alternative Iroh relay infra that has an explicit goal of supporting connecting to iroh@1.0 and providing long-longterm infra stability guarantees for 1.0 has been on my mind for y-e-a-r-s

🚀 1

decentral1se commented

2026-06-29 14:09:18 +00:00

@cblgh I guess you might be missing a call to endpoint.Online() (docs)?

https://github.com/n0-computer/iroh/issues/3713#issuecomment-3591500868

If not, this search might help but the other stuff didn't look helpful.

@cblgh I guess you might be missing a call to `endpoint.Online()` ([docs](https://godocs.io/git.coopcloud.tech/decentral1se/iroh-go#Endpoint.Online))? > https://github.com/n0-computer/iroh/issues/3713#issuecomment-3591500868 If not, [this search](https://github.com/search?q=repo%3An0-computer%2Firoh+%22No+addressing+information+available%22&type=issues) might help but the other stuff didn't look helpful.

decentral1se commented

2026-06-29 14:12:06 +00:00

It would certainly be nice to document thoroughly how to do this:

How to build iroh-relay with the Rust toolchain
Any deployment gotchas other than "put binary on vps with ipv4"
How to configure the code to use the relay (adapting this)

It would certainly be nice to document thoroughly how to do this: * How to build `iroh-relay` with the Rust toolchain * Any deployment gotchas other than "put binary on vps with ipv4" * How to configure the code to use the relay (adapting [this](https://docs.iroh.computer/add-a-relay))

cblgh commented

2026-06-29 14:19:14 +00:00

@decentral1se tysm! flub's answer is really nice for understanding more of the context. fwiw i did have endpoint.Online on both server and client (tho from flub's answer seems only servers needs to call .Online).

it works now but not really sure what a sustainable solution is going forward :) what i was doing was starting a server with the same secret key. that way i could keep connecting to the same endpoint; made iterating way easier. what ended up resolving the dns paniik was that i setting a new secret key (=> new endpoint addy). after doing that suddenly the DNS error disappeared. i wonder if my issue has something to do with DNS caching?

@decentral1se tysm! flub's answer is really nice for understanding more of the context. fwiw i did have `endpoint.Online` on both server and client (tho from flub's answer seems only servers needs to call `.Online`). it works now but not really sure what a sustainable solution is going forward :) what i was doing was starting a server with the same secret key. that way i could keep connecting to the same endpoint; made iterating way easier. what ended up resolving the dns paniik was that i setting a new secret key (=> new endpoint addy). after doing that suddenly the DNS error disappeared. i wonder if my issue has something to do with DNS caching?

👀 1

cblgh closed this issue

2026-06-29 14:19:14 +00:00

decentral1se referenced this issue

2026-06-29 14:26:15 +00:00

Document self-hosted relay approach #13

decentral1se commented

2026-06-29 14:28:35 +00:00

Oh right, I didn't quite understand then myself 🙃 Hope the error stays away 🙏 I would hope that progress on https://github.com/n0-computer/iroh-ffi/pull/240 would help us in this regard by simplying doing everything on the local network. It seems they're still working out how to arrange this... https://github.com/n0-computer/iroh-ffi/issues/255

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: decentral1se/iroh-go#12