Google no longer supports javascript-free search requests #1211
Comments
|
I'm having the same issues, but I'm being rate limited as per my docker logs : ERROR:app:503 (CAPTCHA) |
|
Not seeing any rate limitations mentioned in my logs. |
|
Not directly related to this project, but I've been getting these same redirects for the past couple weeks (on my browser with JS disabled). I've been able to "bypass" it by just simply re-querying, but as of today, they've become more persistent. After enabling Javascript, I'm redirected to the usual "google.com/sorry/index" captcha page that used to regularly happen to me on VPNs. Relevant HN discussion from today ("Google.com search now refusing to search for FF esr 128 without JavaScript"): https://news.ycombinator.com/item?id=42719865 |
|
Getting this as well, temporarily redirecting my engine to searxng but would love to get this resolved as it's too cluttered :D was putting off making an issue while i verified it on a new install.... |
|
Also experiencing this behavior, started happening a few days ago and has entirely stopped working today. |
|
I am too having exactly the same issue |
|
+1 |
|
I am also having the same issue, on latest. |
|
Same here -was able to refresh but now no-worky. Running in docker on Unraid |
|
Same on Umbrel OS but only in the "ALL" option. |
|
+1 News, Images, etc. works for me as well. I tried to use by disabling tor through environment variable, but that didn't change anything. |
|
+1 here as well |
|
+1 same issue |
|
Same here since this morning. Relieved for a moment that it's not on my end, but that's actually more concerning... |
|
+1 |
|
+1 for me, Docker or Debian |
|
Same issue here. No change from my side at the docker compose.
Getting this page instead: |
|
+1 truenas docker container. only recently occured, empty results. |
|
+1 for me, Docker. Same as everyone. I get the 503 captcha in the docker log but blank results, Images/News etc. work fine. |
|
same here on docker. search results is blank, images/videos/news/maps works |
|
+1 |
|
The +1 comments are pretty useless, please there is a |
|
maybe would be good to add backup search engine? |
|
@bruvv the +1 is not about subscribing it's more for showcasing how many people are affected by this issue. |
|
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Vivaldi/7.0.3495.29" @benbusby - Vivaldi UA works - I use Vivaldi. |
This one isn't working for me. I've tested several of the others and they all return results but this one doesn't. |
|
Maybe because I am using vivaldi??? The above is my docker-compose.yml snipped. |
|
Looks like this is not an accident: |
|
Any pointers on how to implement this fix? I'm afraid I'm clueless! I installed in proxmox as an LXC and that was about the extent of my technical input! |
I'm assuming you used the Proxmox VE Helper-Scripts? Just re-run their install command and it will pull the update via pip. |
I am in a similar situation. I just tried the in-built "update" command, as well as then deleting the LXC and spinning up a fresh new one with the install script, and neither worked. The issue remains the same. The "all" tab is empty. The other tabs all populate results. Perhaps when the community script is ran, it pulls a cached copy of Whoogle to install and not a fresh one? |
No didnt work for me - also tried "update" - nothing - same results as VenomousRage |
|
I did try to search for the modified file so I could just overwrite it but there are multiple versions and I didnt know which to replace - this is via "filebrowser" - also installed as a proxmox script into the LXC whoogle lives in. |
@calderjh if the update worked you should have a user agent drop down option in the config on the whoogle landing page and it should default to lynx which works. if you dont have that drop down then the update didnt work. |
OK that's not there and version still showing as v0.9.1 (current) - from what I can see, just one file has been updated, do you know where this is located exaclty? I could just drag-drop the new one over? |
try running |
Gives me this: Last login: Sat Jan 18 00:58:20 GMT 2025 on tty1 But still not working |
|
For what it's worth, "pip install whoogle-search --upgrade" also doesn't seem to be pulling any updates for me, still at 0.9.1. I also usually get the latest requirements and update them. It did get some new cssutils. But I did get it working by manually adding the user agent to the environment: whoogle/lib/python3.11/site-packages |
Thanks so much but I can't find site-packages for the life of me. In that location I have sitecusomize.py but not sure i should be meddling with this if its the wrong one! |
|
New install using docker-compose and the user agent env variables, I get an error on creating the container. Docker compose yaml |
|
site-packages is a directory. I should have added the filename.
You might need to add the file. But your setup might be different, too. I'm still not sure why it's not pulling any update. |
|
Totally different set-up I think as nothing resembling this exists. The version number has not been incremented so i would assume that the old version is still being dished out? But I am ignorant of how GitHub works so could be wrong. |
Looking at the current main branch on github the active version is '0.9.1'
|
|
0.91 was released on 24th October last year. Which, I guess, is why we have no fix in that version - I just wasn't sure if the code was a "living entity" as such whereby any requests to download automatically fed from an updated version. Seems not. |
|
Programmatically decode and decipher the code provided by Google to determine if JavaScript is enabled, and then save this code in cookies or local storage as requested. |
|
For all of those using Whoogle LXC container by Proxmox VE Helper-Scripts, I've updated requirements as @dave0003 suggests:
Then, adding environment variables was quite different. I achieved it by editing the service using
Then restart the service issuing |
|
That makes sense. In my whoogle.service file I've got:
I think that tells it to use the whoogle.env file, but it looks like you can add them all there, too. I use it to set some other settings, too, so it's handy. |
|
You're right, it can also be done with a dedicated file for environment variables, but as the service needs to be edited for both types of configuration, I prefered to put all of them in the same place 😉 |
|
I've been experiencing the same issue! I've also configured Maybe a configuration to change the backend search engine could be helpful. |
This worked great though now I'm seeing mention of TOR in the logs. I don't believe that was there before. |
and others
Describe the bug
As of late, I'm starting to get empty search results when searching for something.
Screenshot:
It actually appears the HTML returned from Whoogle contains a fragment of an error message from Google (I presume):
To Reproduce
Steps to reproduce the behavior:
Deployment Method
runexecutableVersion of Whoogle Search
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: