-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems making relay connections, invalid peer certificate: UnknownIssuer #2257
Comments
The server uses a Let's Encrypt TLS certificate. This error suggests your system's configuration does not trust Let's Encrypt certificates. |
Good observation. When trying to debug further, I tried to |
I caught it in the act of working then not working:
|
I'd assume it's related to https://letsencrypt.org/2024/04/12/changes-to-issuance-chains My best current guess is that depending on request you still get routed to different intermediates and the switch is not finished yet. |
Ok, after a bunch more testing, I'm still very confused about what's happening, but I feel like the problem must be on my end somehow. Most of the time, things are working, but not 100% of the time. I'm not sure what you can do about this, so probably the best thing to do is close this issue |
Thanks for taking the time to report @eminence! I'm going to close this for now, but we can re-open should you need. |
On a RHEL 8.6 system, I am trying to run
doctor connect q22mj7s2phuhfgv5uo3egakw6hj4v32owu7mv3tuxsbzqxz2ayha --relay-url https://use1-1.relay.iroh.network./
and I'm getting these errors:click for full logs (truncated arbitrarily due to github comment lenght limitations)
I'm running 6fbf4a9 on both sides of the doctor connection.
The text was updated successfully, but these errors were encountered: