-
Notifications
You must be signed in to change notification settings - Fork 5
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
Getting "No route to host (os error 65)" #19
Comments
Hi there, sorry about this. Does this error message only appear for that specific host, or does it happen trying to use phetch at all? |
Yes, it is only for this particular host, using phetch on NetBSD. I have another laptop running Pop!_OS LInux and am able to access this host with no errors. I don't get this error for any other hosts afaik. |
Just an update. I asked about this in another forum and it appears that the issue is around accessing ipv6. As user rpv suggests in that thread, it would appear that Could this functionality possible be added at some point? |
I have to apologize, I don't know much about IPv6 at all. But wise rvp's words ring true -- the I've just updated the code to go through the list and try each entry instead of aborting entirely if the first one fails. Is it possible for you to build from If not that's fine, I'm working on getting a NetBSD instance going on EC2 and should be able to use that for testing in the near future. Sorry about this bug! And thanks for pointing me to the forum thread, it's very helpful. |
@xvxx Cool that you are working on getting NetBSD running :) This is nothing I can import into the main repo, though. Only stable releases are allowed by default but, at least I know it will be fixed by the next one. |
@voidpin Awesome, thank you so much! I've just pushed out v1.0.7 with this fix. Appreciate the help, everyone! |
@xvxx & @voidpin thank you both very much 😊 |
Getting "No route to host (os error 65)" when trying to visit gopher://g.nixers.net either from bookmarks or direct from the command line.
I am able to access this particular gopherhole using Lynx so the issue seems to be with phetch. Any idea what's going on here?
I'm on NetBSD in case the error relates to the "OS"
The text was updated successfully, but these errors were encountered: