mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #1053] [BUG] Before u continue to Google #646
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#646
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @anoo2niem on GitHub (Aug 16, 2023).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1053
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
@inittux111 commented on GitHub (Aug 16, 2023):
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?
@rickykresslein commented on GitHub (Aug 16, 2023):
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.
Also, in the other post it seems this was an EU-only issue, and I am in the EU.
@anoo2niem commented on GitHub (Aug 16, 2023):
Yeah the cause is surely on google's end. Probably it was/is a EU-only issue because of GDPR.
Hopefully this can be bypassed in some way.
@seirdotexe commented on GitHub (Aug 16, 2023):
Getting the same thing
@fatihkoy commented on GitHub (Aug 16, 2023):
same here
@cpu2910 commented on GitHub (Aug 16, 2023):
+1
Ubuntu Server 22.04 , Whoogle Docker v0.8.2
@anoo2niem commented on GitHub (Aug 16, 2023):
Current workaround; i've got my whoogle working again by routing it through a non EU vpn.
@helsingi commented on GitHub (Aug 16, 2023):
same issue
@NoCodeFromMe commented on GitHub (Aug 16, 2023):
Same, also located in the EU.
Debian 11, Pip, Whoogle Search v0.8.2
@imTHAI commented on GitHub (Aug 16, 2023):
Same here, from France
@chocology commented on GitHub (Aug 16, 2023):
same here from Bern
@JiriVitner commented on GitHub (Aug 16, 2023):
I can confirm same issue from Brno (Czech)
@Procuria commented on GitHub (Aug 16, 2023):
Can confirm too from Germany
@imTHAI commented on GitHub (Aug 16, 2023):
Indeed. Thanks, it It will do the job in the meantime.
@fabi321 commented on GitHub (Aug 16, 2023):
github.com/benbusby/whoogle-search@18fc14dc5b/app/request.py (L310)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, toCAISHAgBEhJnd3NfMjAyMzA4MTAtMF9SQzIaAmRlIAEaBgiAo_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)@cpu2910 commented on GitHub (Aug 16, 2023):
May I ask how and where to do this ?
My whoogle runs in a docker container on a ubuntu server nginx reverse proxy...
@anoo2niem commented on GitHub (Aug 16, 2023):
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.
@anoo2niem commented on GitHub (Aug 16, 2023):
Would u mind explaining how to set these?
I want to try it aswell but i'm not sure how to modify that line.
@Imaskiller commented on GitHub (Aug 16, 2023):
Replacing
with
fixes the problem.
edit fix typo
@anoo2niem commented on GitHub (Aug 16, 2023):
Thanks, seems to have solved it indeed.
@C8opmBM commented on GitHub (Aug 16, 2023):
hopefully an update will be pushed soon. I have no idea how to edit those cookies lines :)
@jniggemann commented on GitHub (Aug 17, 2023):
I confirm.
@bjornberfelo commented on GitHub (Aug 17, 2023):
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
@mztiq commented on GitHub (Aug 17, 2023):
Can confirm.
@LANTaverne2 commented on GitHub (Aug 17, 2023):
Hi, same error. I fix it with the workaround to modiy the request.py
Thanks
@Sebastix commented on GitHub (Aug 17, 2023):
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.
@Tubeman-cell commented on GitHub (Aug 17, 2023):
Getting the same thing
@C8opmBM commented on GitHub (Aug 17, 2023):
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
@cpu2910 commented on GitHub (Aug 17, 2023):
You may edit your running container:
docker exec -it <container_id> /bin/sh
edit the 'cookies'-line in ./app/request.py
exit the container and restart with 'docker restart <container_id>
That fixed the problem for me.
@bjornberfelo commented on GitHub (Aug 17, 2023):
Anyone who what's a temp image to use :-)
blivius92/temp-whoogle:latest
@cemkur commented on GitHub (Aug 17, 2023):
you need to remove the fourth line on the replacing block which is just a )
than it works.
@nagyrobi commented on GitHub (Aug 17, 2023):
And how about the rest of us who installed by
pip?@heinxyze commented on GitHub (Aug 17, 2023):
Same behaviour
latest Whoogle docker image running on QNAP NAS, Germany
@be-root commented on GitHub (Aug 17, 2023):
nano /usr/local/lib/python3.11/dist-packages/app/request.py
Line 297:
297 cookies = {
298 'CONSENT': 'PENDING+987',
299 'SOCS': 'CAESHAgBEhJnd3NfMjAyMzA4MTAtMF9SQzIaAmRlIAEaBgiAo_CmBg'
300 }
@imTHAI commented on GitHub (Aug 17, 2023):
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 ?
@fabi321 commented on GitHub (Aug 17, 2023):
@imTHAI I already created #1054, it's just waiting to be merged
@fusrohdan commented on GitHub (Aug 18, 2023):
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.
Thanks!
@JiriVitner commented on GitHub (Aug 18, 2023):
In the container is available "vi", not "vim"
@baerenmarke90 commented on GitHub (Aug 18, 2023):
Workaround works, thank you!
@fusrohdan commented on GitHub (Aug 18, 2023):
Thank you, I have edited the cookies line now but the container won't start. I will troubleshoot later after work
@GusGus68 commented on GitHub (Aug 18, 2023):
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
docker exec -it <container_id> /bin/sh
cd app
vi request.py
then replace
cookies = {
'CONSENT': 'YES+cb.{:d}{:02d}{:02d}-17-p0.de+F+678'.format(
now.year, now.month, now.day
)
with the following
cookies = {
'CONSENT': 'PENDING+987',
'SOCS': 'CAESHAgBEhJnd3NfMjAyMzA4MTAtMF9SQzIaAmRlIAEaBgiAo_CmBg'
note the last bracket is removed
Then exit and restart container with
docker restart <container_id>
@imTHAI commented on GitHub (Aug 18, 2023):
It works for me too
@IvanVojtko commented on GitHub (Aug 18, 2023):
Not the nicest one, but for my fellow kubernetes folks out there, update your deployment with
@Luxumbra27 commented on GitHub (Aug 18, 2023):
Little correction:
@Drallas commented on GitHub (Aug 18, 2023):
I run a LXC with Whoogle and struggled a bit, with whoogle.service service not starting.
This is how I did it.
systemctl stop whoogle.servicevi /usr/local/lib/python3.11/dist-packages/app/request.pyThen replaced the complete 'cookies block' for:
systemctl start whoogle.servicesystemctl status whoogle.service@inittux111 commented on GitHub (Aug 19, 2023):
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.
@malyyigor34 commented on GitHub (Aug 20, 2023):
Confirm issue, I am from Poland
@HeavyTobi commented on GitHub (Aug 21, 2023):
same issue for me,
Germany
Whoogle v0.8.2
Server: Docker @ Ubuntu LTS
Clients tested: Firefox on macOS and Safari on iOS
@hs6666 commented on GitHub (Aug 21, 2023):
same issue here....
@Deedikjupijn commented on GitHub (Aug 21, 2023):
Same issue here,
Just installed whoogle,
Server: Docker debian 11
@DrMatschhirn commented on GitHub (Aug 21, 2023):
Same Issue with latest Docker Image.
@peternrdstrm commented on GitHub (Aug 21, 2023):
I have the same issue but with Heroku. Can somebody help me do the workaround?
@martyn-meister commented on GitHub (Aug 22, 2023):
Latest docker image works for me. Remember to do a docker pull, or in k8s
ImagePullPolicy: Alwaysor you won't get the newest.@sorcer1122 commented on GitHub (Sep 13, 2023):
Had the same problem in Amsterdam. The following fixed it:
docker pull benbusby/whoogle-search
docker stop [container_id]
docker rm [container_id]
docker run --publish 5000:5000 --detach --name whoogle-search benbusby/whoogle-search:latest