Skip to content
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

Closed
pfr-dev opened this issue Sep 28, 2020 · 8 comments
Closed

Getting "No route to host (os error 65)" #19

pfr-dev opened this issue Sep 28, 2020 · 8 comments

Comments

@pfr-dev
Copy link

pfr-dev commented Sep 28, 2020

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.

09-28-2020-11-29

09-28-2020-11-17

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"

@xvxx
Copy link
Owner

xvxx commented Sep 28, 2020

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?

@pfr-dev
Copy link
Author

pfr-dev commented Sep 29, 2020

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.
The strange thing is this error came out of nowhere. I was able to access this host from my NetBSD machine just fine until all of a sudden I couldn't.
I reached out to the sysadmin for g.nixers.net and they informed me they had recently configured ipv6 stack on the server, adding a AAAA record for g.nixers.net. But seeing as I can access this host using Lynx from my NetBSD system it doesn't appear to be an issue with ipv6.

I don't get this error for any other hosts afaik.

@pfr-dev
Copy link
Author

pfr-dev commented Oct 2, 2020

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 phetch does not try to connect to other IP's if the first one fails.

Could this functionality possible be added at some point?

@xvxx
Copy link
Owner

xvxx commented Oct 2, 2020

I have to apologize, I don't know much about IPv6 at all. But wise rvp's words ring true -- the socket_addrs() call phetch makes does indeed return a list that I'm not properly caring for.

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 master and try it out?

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.

@ghost
Copy link

ghost commented Oct 2, 2020

@xvxx Cool that you are working on getting NetBSD running :)
But you don't need to do it for this issue. I've just did a git-master package of phetch to test and its working now.
Check back at the forum thread for a screenshot ;)

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.
Cheers for your collaborative spirit and feel free to close this issue.

@xvxx
Copy link
Owner

xvxx commented Oct 3, 2020

@voidpin Awesome, thank you so much! I've just pushed out v1.0.7 with this fix. Appreciate the help, everyone!

@xvxx xvxx closed this as completed Oct 3, 2020
@ghost
Copy link

ghost commented Oct 3, 2020

@pfr-dev
Copy link
Author

pfr-dev commented Oct 3, 2020

@xvxx & @voidpin thank you both very much 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants