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
[BUG] Before u continue to Google #1053
Comments
I'm also getting the same with Whoogle running in a container, running the same version(v0.8.2 ). Earlier today this wasn't a problem so Google must have changed something? |
Same. This is a duplicate of #243, but that was from a couple of years ago. It seems this is a bug that keeps popping up when Google changes things. |
Yeah the cause is surely on google's end. Probably it was/is a EU-only issue because of GDPR. |
Getting the same thing |
same here |
+1 |
Current workaround; i've got my whoogle working again by routing it through a non EU vpn. |
same issue |
Same, also located in the EU. |
Same here, from France |
same here from Bern |
I can confirm same issue from Brno (Czech) |
Can confirm too from Germany |
Indeed. Thanks, it It will do the job in the meantime. |
Line 310 in 18fc14d
It looks like, the current style uses consent yes. However, If I try it out in a browser window, it always sets it to Pending+### , and also sets another cookie, SOCS , to CAISHAgBEhJnd3NfMjAyMzA4MTAtMF9SQzIaAmRlIAEaBgiAo_CmBg (this is consistent across private browser sessions) Setting both of these resolved the issue in my case. (replace # with any digits, using 900 all the time seems to do fine)
|
May I ask how and where to do this ? |
I have a separate container running wireguard, and i point my whoogle container it's gateway to the ip of the wireguard container. So set up a wireguard container and configure it according to your vpn provider, then make sure your iptables are set up right, so all network traffic comming in that container is forwarded properly. |
Would u mind explaining how to set these? |
Replacing
with
fixes the problem. edit fix typo |
Thanks, seems to have solved it indeed. |
hopefully an update will be pushed soon. I have no idea how to edit those cookies lines :) |
I confirm. |
Confirm that it solves the problem, but i needed to remove the ) on the end :-) otherwise i got a error: SyntaxError: closing parenthesis ')' does not match opening parenthesis '{' on line 309 |
Can confirm. |
Hi, same error. I fix it with the workaround to modiy the request.py
Thanks |
This change also fixed it for me and I've manually build the Docker image (see https://github.com/benbusby/whoogle-search#manual-docker) to start a new container with it. |
Getting the same thing |
Could you share your docker image until the official one is updated? I've never built an image and Im sure this will come handy for a lot of other users. In advance, thanks |
You may edit your running container: That fixed the problem for me. |
Anyone who what's a temp image to use :-) |
you need to remove the fourth line on the replacing block which is just a ) |
And how about the rest of us who installed by |
Same behaviour |
nano /usr/local/lib/python3.11/dist-packages/app/request.py Line 297: 297 cookies = { |
If it is confirmed that it solves the problem, why don't we apply the modification in the official branch ? Some extra tests must be performed ? |
Hey, thanks for your fix. I went to do this fix in my docker container, but there is no text editor available. I tried vim and nano. What text editor did you use? I tried to see if the container has a volume mounted so I can edit from host but that is not the case. |
In the container is available "vi", not "vim" |
Workaround works, thank you! |
Thank you, I have edited the cookies line now but the container won't start. I will troubleshoot later after work |
The reason it won't start is the last bracket. If you remove it it will work. For any other noobs like me, the way to do this in docker is as per the instructions above. ssh into your server. then type then replace with the following note the last bracket is removed Then exit and restart container with |
It works for me too |
Not the nicest one, but for my fellow kubernetes folks out there, update your deployment with
|
Little correction:
|
I run a LXC with Whoogle and struggled a bit, with whoogle.service service not starting. This is how I did it.
Then replaced the complete 'cookies block' for:
|
I just tried @bjornberfelo's temp image and it works, thank you! Which means that if you are running the official image and change the lines manually in your image that your container needs a restart which means you need to be using persistent storage for your container or else your container will revert to the image you are using when you restart your container. |
Confirm issue, I am from Poland |
same issue for me, Germany |
same issue here.... |
Same issue here, |
Same Issue with latest Docker Image. |
I have the same issue but with Heroku. Can somebody help me do the workaround? |
Latest docker image works for me. Remember to do a docker pull, or in k8s |
Had the same problem in Amsterdam. The following fixed it: |
Describe the bug
Just since now, i'm not able to use whoogle anymore. The google 'consent' page is popping up to allow or decline cookies.
To Reproduce
Steps to reproduce the behavior:
Search any keywoard
Deployment Method
Proxmox in lxc container
Version of Whoogle Search
8.2.0 (installed with script https://tteck.github.io/Proxmox/, which i guess uses pip, not sure)
Additional context
Tried changing vpn location where my instance is routed through
The text was updated successfully, but these errors were encountered: