search

moson-mo / pacseek

A terminal user interface for searching and installing Arch Linux packages
MIT License
349 stars 9 forks source link

Error while searching for AUR packages #24

Closed zer0exia closed 1 year ago

zer0exia commented 1 year ago

Didn't have any problem searching packages using yay or paru, but searches used with pacseek produce error and empty result ;

Error : Get https://server.moson.rocks/rpc?v=5&type=seach&by=name&arg=pacseek" : context deadline exceeded (Client.Timeout exceeded while awaiting headers)

moson-mo commented 1 year ago

Can't reproduce that issue. Maybe a network hiccup or so.

zer0exia commented 1 year ago

Found the problem, it happens if I am connected to Cloudflare Warp. Yay or paru isn't affected, so I'm not entirely sure if this problem is on warp side. Any logs or debug output that I should provide?

moson-mo commented 1 year ago

Cloudflare Warp

Don't know how that works.
What's your "AUR timeout" setting? Try to increase it a bit.

zer0exia commented 1 year ago

Warp is just a Cloudflare service I used to bypass ISP restriction, kinda similar to a vpn connection.

Changing the timeout doesn't solve it. Instead, it's solved after I tried changing the 'AurRpcUrl'

https://server.moson.rocks/rpc to https://aur.archlinux.org/rpc

Is there any particular reason I should be using this specific domain server instead of official aur address?

moson-mo commented 1 year ago

Hmm. No clue why they would block that one.
I host an own instance instance of /rpc for pacseek so there is less requests on the AUR itself. (It's fine if you change that though).

zer0exia commented 1 year ago

Okay I figured as much. I think we can close this one as this issue isn't on pacseek. Though I wanna ask, if I'm using the official aur address, would there be a risk of something like Pamac ddos incident to occur? Using an own instance like you did in this case probably already mitigate it

moson-mo commented 1 year ago

would there be a risk of something like Pamac ddos incident to occur?

No, don't worry. The AUR handles over a million requests per day. A couple more shouldn't harm :wink:

somepaulo commented 11 months ago

t's solved after I tried changing the 'AurRpcUrl'

Saved me!

somepaulo commented 11 months ago

I host an own instance

Your host might be blocking connections from Surfshark IPs. Happens occasionally with different hosts and different Surfshark locations.