search

tldr-pages / tldr-python-client

:snake: Python command-line client for tldr pages 📚
https://pypi.org/project/tldr/
MIT License
599 stars 95 forks source link

Error fetching from tldr: <urlopen error [Errno 111] Connection refused> #159

Closed geosmart closed 3 years ago

geosmart commented 3 years ago

$ tldr tar [23:55:38] Error fetching from tldr: <urlopen error [Errno 111] Connection refused> FAIL: 1

marchersimon commented 3 years ago

Hey @geosmart ,

which client are you using?

bl-ue commented 3 years ago

That looks like the Python one (urlopen). Am I correct, @geosmart?

Waples commented 3 years ago

If its this one, then it works fine for me. Would have been nice to have the entire traceback next time

bl-ue commented 3 years ago

Hi @geosmart, I'm going to close this. If you're still having this error, reply here and we'll reopen this issue.

yanhanBazoooka commented 10 months ago

Also having the same error message, running on wsl Ubuntu. $ tldr tar Error fetching from tldr: <urlopen error [Errno 111] Connection refused>

kbdharun commented 10 months ago

@yanhanBazoooka Can you update the cache with tldr -u and try again?

Also, can you provide additional details on how you installed the Python client on WSL? (Snap? Pip?)

yanhanBazoooka commented 10 months ago

@kbdharun Thanks for the reply! cache update worked for me. Would you mind explain how is this related to cache update? I used snap to install tldr.

kbdharun commented 10 months ago

@kbdharun Thanks for the reply! cache update worked for me. Would you mind explain how is this related to cache update? I used snap to install tldr.

Sure, this issue was first reported at https://github.com/tldr-pages/tldr-python-client/issues/150, the Python client fetches the page directly from GitHub, which was later updated to use the cache first. This issue seems to crop up when there is an issue with the network when it is fetching the cache (and it can be fixed by manually updating it).

yanhanBazoooka commented 10 months ago

@kbdharun Thanks for the reply! cache update worked for me. Would you mind explain how is this related to cache update? I used snap to install tldr.

Sure, this issue was first reported at #150, the Python client fetches the page directly from GitHub, which was later updated to use the cache first. This issue seems to crop up when there is an issue with the network when it is fetching the cache (and it can be fixed by manually updating it).

Very educational, thanks!