mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 20:25:51 +03:00
[GH-ISSUE #532] [BUG] Tor searches fail without message #341
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#341
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 @thunderclap82 on GitHub (Nov 11, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/532
Describe the bug
I have Whoogle running in an Unraid container and the main GUI comes up fine, but whenever I search for something it gets stuck and never finds anything. I saw there was a recent update to the container so I did that but it didn't fix the problem.
Deployment Method
runexecutableVersion of Whoogle Search
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
@Coolykoen commented on GitHub (Nov 12, 2021):
For me, it looks stuck aswell, and like you, i do see the main search bar and whoogle logo, but once i type in something and press enter, it gets stuck.... or so i thought, for me, after about a full 2 minutes it does come through sometimes... other times it times out and i get internal server error 500
@eddydc commented on GitHub (Nov 12, 2021):
I don't get anything else than server 500 error. Restarting the container doesn't work either. This makes that whoogle doesn't work at all anymore.
@Coolykoen commented on GitHub (Nov 12, 2021):
To be fair, there was a big google server problem hours ago, maybe that had to do something with it...
@thunderclap82 commented on GitHub (Nov 12, 2021):
Google itself works, though. I’m wondering if they made a change to the API that breaks how Whoogle works?
@benbusby commented on GitHub (Nov 12, 2021):
Not able to reproduce on Heroku, VPS, or local instances. Can you confirm if it's still happening for you? If it is, can you clarify the geographic region your instance is running in?
@thunderclap82 commented on GitHub (Nov 12, 2021):
It still is happening but it's a little different now. It tries searching for a little over a minute and then the search box clears out and that's it. No results.
I'm in Illinois, US.
@eddydc commented on GitHub (Nov 12, 2021):
It seems to work over here (Belgium, Europe). Whatever the reason might be, Whoogle shouldn't return an internal server error when something is going wrong on the Google side.
@benbusby commented on GitHub (Nov 12, 2021):
Issue was privately determined to be caused by "Tor mode" in Whoogle. There's a failure with parsing the result when Google blocks the exit node from performing a search.