[GH-ISSUE #754] [BUG] Wrong serch result at second page of result of search #477

Closed
opened 2026-02-25 20:35:51 +03:00 by kerem · 6 comments
Owner

Originally created by @navhawk80 on GitHub (May 11, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/754

Hello. On firefox if I right click highlighted text and hit "Search Whoogle for ..." all goes well and I have a page with result of search but it adds '&cookies_disabled=1' into address bar 'https://<whogle.example.com>/search?cookies_disabled=1'. If I push the 'second page' at the bottom of the search page with resulf of search it will redirect to page 'https://<whogle.example.com>/search?q=gAAAAABiez8uMkjVi7T6kSFVm5WCBrWbP8IJDJfcjbUWK2WvI9FvL5K8J0rGCoiuAb7U0oK3sqVyzGqnn8yNq4-cqvLBV2xWIQ==&start=10' and 'no results were found for gAAAAABiez8uMkjVi7T6kSFVm5WCBrWbP8IJDJfcjbUWK2WvI9FvL5K8J0rGCoiuAb7U0oK3sqVyzGqnn8yNq4-cqvLBV2xWIQ==&start=10' as an example.
I use docker latest at the moment version 0.7.2 on xpenology behind reverse proxy with Let'sencrypt sertificate. Problem came since 0.7.0 version.
whoogle serach
Update: just checked in google chrome. The same issue.

Originally created by @navhawk80 on GitHub (May 11, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/754 Hello. On firefox if I right click highlighted text and hit "Search Whoogle for ..." all goes well and I have a page with result of search but it adds '&cookies_disabled=1' into address bar 'https://<whogle.example.com>/search?cookies_disabled=1'. If I push the 'second page' at the bottom of the search page with resulf of search it will redirect to page 'https://<whogle.example.com>/search?q=gAAAAABiez8uMkjVi7T6kSFVm5WCBrWbP8IJDJfcjbUWK2WvI9FvL5K8J0rGCoiuAb7U0oK3sqVyzGqnn8yNq4-cqvLBV2xWIQ==&start=10' and 'no results were found for gAAAAABiez8uMkjVi7T6kSFVm5WCBrWbP8IJDJfcjbUWK2WvI9FvL5K8J0rGCoiuAb7U0oK3sqVyzGqnn8yNq4-cqvLBV2xWIQ==&start=10' as an example. I use docker latest at the moment version 0.7.2 on xpenology behind reverse proxy with Let'sencrypt sertificate. Problem came since 0.7.0 version. ![whoogle serach](https://user-images.githubusercontent.com/73139535/167774857-bcd7c32f-8e82-4f72-aab3-99c8f1b89f00.jpg) Update: just checked in google chrome. The same issue.
kerem 2026-02-25 20:35:51 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@DUOLabs333 commented on GitHub (May 11, 2022):

Yeah, it seems to be an error with cryptography decrypting. If you go back to the first page and reload, it usually works.

<!-- gh-comment-id:1123832422 --> @DUOLabs333 commented on GitHub (May 11, 2022): Yeah, it seems to be an error with cryptography decrypting. If you go back to the first page and reload, it usually works.
Author
Owner

@navhawk80 commented on GitHub (May 14, 2022):

For me it doesn't work. If I go to the first page and reload it will show me clean start page of whoogle. Continue to use 0.6.0 at the moment where all works well.

<!-- gh-comment-id:1126671073 --> @navhawk80 commented on GitHub (May 14, 2022): For me it doesn't work. If I go to the first page and reload it will show me clean start page of whoogle. Continue to use 0.6.0 at the moment where all works well.
Author
Owner

@DUOLabs333 commented on GitHub (May 14, 2022):

Just ancedotal --- once I pulled from git, I never had a problem.

<!-- gh-comment-id:1126722798 --> @DUOLabs333 commented on GitHub (May 14, 2022): Just ancedotal --- once I pulled from git, I never had a problem.
Author
Owner

@navhawk80 commented on GitHub (Jun 5, 2022):

Just ancedotal --- once I pulled from git, I never had a problem.

Which version do you use? On latest 0.7.3 I still have this issue.

<!-- gh-comment-id:1146861944 --> @navhawk80 commented on GitHub (Jun 5, 2022): > Just ancedotal --- once I pulled from git, I never had a problem. Which version do you use? On latest 0.7.3 I still have this issue.
Author
Owner

@DUOLabs333 commented on GitHub (Jun 5, 2022):

Interesting

<!-- gh-comment-id:1146869372 --> @DUOLabs333 commented on GitHub (Jun 5, 2022): Interesting
Author
Owner

@navhawk80 commented on GitHub (Jun 24, 2022):

The issue was solved when I added "GET Requests Only" into the docker container and re-add the search engine. https://github.com/benbusby/whoogle-search#using-with-firefox-containers Now all works well.

<!-- gh-comment-id:1165836242 --> @navhawk80 commented on GitHub (Jun 24, 2022): The issue was solved when I added "GET Requests Only" into the docker container and re-add the search engine. https://github.com/benbusby/whoogle-search#using-with-firefox-containers Now all works well.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/whoogle-search#477
No description provided.