I am unable to perform a search on Qwant (https://www.qwant.com) on the Librem 5 using either the Firefox browser (128.13.0esr) or the Epiphany browser.
When I access the site, I have to solve a captcha. However, even if I solve it correctly, the following message appears:
You have been blocked. There are several possible reasons for this:
You are browsing at superhuman speed.
Something is blocking JavaScript from working on your computer.
There is a robot on the same network as you.
Other search engines such as Ecosia and DuckDuckGo work fine.
Do you have a VPN connection running? I get those captchas/blocks on Startpage with my VPN. Changing the VPN server usually helps avoid the gatekeeping for a while.
Up to date as per the PureOS repos perhaps but not up to date as per the real world. Firefox 128 is quite old and is likely why this is happening. Byzantium has a very old version of Gnome Browser so same reason.
Try the official gnome flatpak , or the Firefox flatpak, to see if there is any difference
Maybe the message you get from the search provider is true and there is a bot on your network? If you do not use a VPN, then NAT or CGNAT may have hundreds of people on the same public IPv4 address possibly including a rotten apple. Have you tried using a VPN to change your public IPv4 address?
Or you could go to a friend’s house, check if your IP is different and try again.
For clarity, are you using this web site when the phone is able to access the internet via WiFi or via the mobile network or via both? The question applies both when you were at your house and when you were at your friend’s house.
In particular, if actually accessing the web site via the mobile network in both cases then, depending on whether and how your mobile service provider has implemented CGNAT, there could be little to no difference in IP address (and the trip to your friend’s house didn’t really achieve much).
On the other hand, if actually accessing the web site via WiFi in both cases and the WiFi ultimately leads to internet connections using completely different technologies (and potentially via different internet service providers) then that is a much more solid test. (So the solid test would probably involve using the kill switch to turn off the mobile network temporarily.)
Bottom line though is that I think noone so far understands why this problem is occurring.