mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #891] [QUESTION] <No image thumbnails after upgrading to 0.8 version> #552
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#552
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 @brackhap on GitHub (Nov 27, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/891
After upgrading my private instance to 0.8 version, No images are shown in images search results (see this screenshot). I am using portainer to deploy whoogle on my vps.
Any ideas?
@benbusby commented on GitHub (Nov 28, 2022):
Could you repeat the request with the network tab in the browser console open, and see if the image requests are failing? If they are, what's the status code returned by each request?
My guess is that there's an issue with decrypting the image path. It might help to clear all cookies associated with your instance, since decryption was previously tied to a session ID stored in the cookie.
@brackhap commented on GitHub (Nov 28, 2022):
After checking the network tab, all images returned a 302 status code, and the request url is weired:
https://mydomain.xyz/https, https://mydomain.xyz/element?url=gAAAAABjhS86fmEPgJbgxZJQUC-nH0x7SCy4nYriFtjKcwfmzQL2ysAPPHsPZn7r3PYPrvfLYVbu67YRY3biIANEr9xfEirVSbcFshemZZXSz7RE7GowyyyYmds8FyzDQ6bzJ3HCf2T9h9xeXFTxMKUZwd4g5iODJn5pSyksmhPzFFbdbo8Vtj2wApbzCBltaiN0rYUUHG96DkHHCFJh8u0pTd2EMvb2gkqUl5pihk5kDQYgUZVMbCM=&type=image/pngI've cleared all the cookies and used different new browsers but the issue persists.
@benbusby commented on GitHub (Dec 5, 2022):
I believe this should be fixed as of
0310f0f542(available on thelatesttag if you're using Docker) but let me know if it persists.