mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #164] [BUG] pictures not displayed anymore #117
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#117
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 @somebody-somewhere-over-the-rainbow on GitHub (Jan 12, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/164
Describe the bug
With the latest docker version, I started to not see images (pictures) anymore since yesterday. I normally run whoogle via a reverse proxy (nginx) but the issue persists if I access it directly via the port 5000 . It is really just images - youtube preview in the main search page and in the videos tab are displayed.
To Reproduce
Steps to reproduce the behavior:
Deployment Method
Version of Whoogle Search
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Server has access to the web with outgoing ports 80 & 443 open - all others closed.
Location is Germany.
@benbusby commented on GitHub (Jan 12, 2021):
Hmmm, I'm not seeing this issue on my end...
Are you able to see if the image requests are being logged successfully on your end? Anything hitting
/elementshould be relevant here. If you're not seeing any/elementrequests, then it could be a configuration issue. Otherwise it could be an issue related to decrypting the request, which I'd need to look into some more.The thumbnails for the videos are retrieved using the same endpoint though, so I'm skeptical that it could be an issue there, but worth checking.
@somebody-somewhere-over-the-rainbow commented on GitHub (Jan 12, 2021):
just checked the nginx logs. Looks fine.
@somebody-somewhere-over-the-rainbow commented on GitHub (Jan 12, 2021):
Looking at the docker logs however, I saw this:
Could this be related?
@benbusby commented on GitHub (Jan 12, 2021):
No, those are generally benign (although a bit annoying) errors from the Tor socket handler.
The 43 byte transfer for each of those
/elementrequests indicates that it's returning the blank base64 placeholder image, which typically means that the decrypted link for the actual content is invalid or is otherwise returning an invalid response.I'll look into this a bit more and let you know if I figure anything out. In the meantime, you could try the
betatag on Docker Hub and see if that helps at all. Thelatesttag is getting a bit stale at this point -- I'll likely be releasing a new version anyways using the current contents of thebetatag in the next week or so.@somebody-somewhere-over-the-rainbow commented on GitHub (Jan 12, 2021):
this actually from the beta tag - I also tried experimental ;-)
@somebody-somewhere-over-the-rainbow commented on GitHub (Jan 12, 2021):
I forgot: thanks for the effort - I really, really appreciate whoogle and what you are doing!
@benbusby commented on GitHub (Jan 12, 2021):
Gotcha, I misunderstood your original comment.
My pleasure!
@benbusby commented on GitHub (Jan 13, 2021):
I've tried a few different configurations and still can't get this reproduced on my end...I'm drawing a blank on what to try next.
Could you try adding a couple debug print statements to see if the link being decrypted is just a bad link, or if the contents are invalid in some way? Namely here:
github.com/benbusby/whoogle-search@7e39b4e7a0/app/routes.py (L299-L319)Validating
src_url,src_type, andfile_data(forfile_datajust validating that it isn't empty should be fine) would be helpful to narrow down what could be going wrong.@somebody-somewhere-over-the-rainbow commented on GitHub (Jan 13, 2021):
sorry for keeping you busy. I ran the container through a VPN last night and had the issue disappeared. It is some strange filtering on the network that I have to figure out. Again sorry for having you run circles around this...
@benbusby commented on GitHub (Jan 13, 2021):
Oh no worries at all, it was no trouble. I'm glad it's somewhat fixed now for you!