starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-25 20:25:51 +03:00

[GH-ISSUE #1234] [BUG] Favicon no longer available #734

New issue

Closed

opened 2026-02-25 20:36:26 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 20:36:26 +03:00

Owner

Originally created by @billkewl on GitHub (Jul 13, 2025).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1234

Describe the bug
Favicons are no longer available on result page

To Reproduce
Steps to reproduce the behavior:

Open self hosted whoogle instance
Search anything
No favicons on result page

Deployment Method

Heroku (one-click deploy)
Docker
run executable
pip/pipx
Other: [describe setup]

Version of Whoogle Search

Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Version [version number]
Not sure

Desktop (please complete the following information):

OS: [e.g. iOS] Windows 11
Browser [e.g. chrome, safari] Firefox
Version [e.g. 22] 140

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Here's my environment

% docker compose run whoogle-search env
WARN[0000] /home/[redacted]/whoogle-search/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=[redacted]
TERM=xterm
WHOOGLE_CONFIG_NEW_TAB=1
WHOOGLE_RESULTS_PER_PAGE=20
WHOOGLE_CONFIG_PREFERENCES_KEY=[redacted]
WHOOGLE_SHOW_FAVICONS=1
WHOOGLE_CONFIG_VIEW_IMAGE=1
WHOOGLE_CONFIG_SAFE=0
WHOOGLE_AUTOCOMPLETE=1
WHOOGLE_CONFIG_PREFERENCES_ENCRYPTED=1
WHOOGLE_CONFIG_ANON_VIEW=1
LANG=C.UTF-8
GPG_KEY=[redacted]
PYTHON_VERSION=3.12.6
CONFIG_VOLUME=/config
WHOOGLE_URL_PREFIX=
WHOOGLE_USER=
WHOOGLE_PASS=
WHOOGLE_PROXY_USER=
WHOOGLE_PROXY_PASS=
WHOOGLE_PROXY_TYPE=
WHOOGLE_PROXY_LOC=
WHOOGLE_DOTENV=
HTTPS_ONLY=
EXPOSE_PORT=5190
WHOOGLE_ALT_TW=farside.link/nitter
WHOOGLE_ALT_YT=farside.link/invidious
WHOOGLE_ALT_RD=farside.link/libreddit
WHOOGLE_ALT_MD=farside.link/scribe
WHOOGLE_ALT_TL=farside.link/lingva
WHOOGLE_ALT_IMG=farside.link/rimgo
WHOOGLE_ALT_WIKI=farside.link/wikiless
WHOOGLE_ALT_IMDB=farside.link/libremdb
WHOOGLE_ALT_QUORA=farside.link/quetre
WHOOGLE_ALT_SO=farside.link/anonymousoverflow
HOME=/home/whoogle

It seems that WHOOGLE_SHOW_FAVICONS is no longer working

Originally created by @billkewl on GitHub (Jul 13, 2025). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1234 **Describe the bug** Favicons are no longer available on result page **To Reproduce** Steps to reproduce the behavior: 1. Open self hosted whoogle instance 2. Search anything 3. No favicons on result page **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure **Desktop (please complete the following information):** - OS: [e.g. iOS] Windows 11 - Browser [e.g. chrome, safari] Firefox - Version [e.g. 22] 140 **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Here's my environment ``` % docker compose run whoogle-search env WARN[0000] /home/[redacted]/whoogle-search/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=[redacted] TERM=xterm WHOOGLE_CONFIG_NEW_TAB=1 WHOOGLE_RESULTS_PER_PAGE=20 WHOOGLE_CONFIG_PREFERENCES_KEY=[redacted] WHOOGLE_SHOW_FAVICONS=1 WHOOGLE_CONFIG_VIEW_IMAGE=1 WHOOGLE_CONFIG_SAFE=0 WHOOGLE_AUTOCOMPLETE=1 WHOOGLE_CONFIG_PREFERENCES_ENCRYPTED=1 WHOOGLE_CONFIG_ANON_VIEW=1 LANG=C.UTF-8 GPG_KEY=[redacted] PYTHON_VERSION=3.12.6 CONFIG_VOLUME=/config WHOOGLE_URL_PREFIX= WHOOGLE_USER= WHOOGLE_PASS= WHOOGLE_PROXY_USER= WHOOGLE_PROXY_PASS= WHOOGLE_PROXY_TYPE= WHOOGLE_PROXY_LOC= WHOOGLE_DOTENV= HTTPS_ONLY= EXPOSE_PORT=5190 WHOOGLE_ALT_TW=farside.link/nitter WHOOGLE_ALT_YT=farside.link/invidious WHOOGLE_ALT_RD=farside.link/libreddit WHOOGLE_ALT_MD=farside.link/scribe WHOOGLE_ALT_TL=farside.link/lingva WHOOGLE_ALT_IMG=farside.link/rimgo WHOOGLE_ALT_WIKI=farside.link/wikiless WHOOGLE_ALT_IMDB=farside.link/libremdb WHOOGLE_ALT_QUORA=farside.link/quetre WHOOGLE_ALT_SO=farside.link/anonymousoverflow HOME=/home/whoogle ``` It seems that `WHOOGLE_SHOW_FAVICONS` is no longer working

kerem

2026-02-25 20:36:26 +03:00

closed this issue
added the
unfortunate
label

kerem commented

2026-02-25 20:36:26 +03:00

Author

Owner

@billkewl commented on GitHub (Jul 13, 2025):

WHOOGLE_CONFIG_VIEW_IMAGE is somehow not working either

@billkewl commented on GitHub (Jul 13, 2025): `WHOOGLE_CONFIG_VIEW_IMAGE` is somehow not working either

kerem commented

2026-02-25 20:36:26 +03:00

Author

Owner

@dot-file commented on GitHub (Aug 23, 2025):

Same with my instance. Searxng pulls favicons from Google just fine though so it's probably not a policy change or smth like that

@dot-file commented on GitHub (Aug 23, 2025): Same with my instance. Searxng pulls favicons from Google just fine though so it's probably not a policy change or smth like that

kerem commented

2026-02-25 20:36:26 +03:00

Author

Owner

@Don-Swanson commented on GitHub (Sep 14, 2025):

This is unfortunately a side effect of the User Agents being used. When certain user agents are utilized the results provided by google may or may not have result favicons. If we are able to find a way to utilize modern User Agents again, this should auto resolve, or if you can find an unblocked UA it should resolve as well.

With that said, I will close this as Not a Bug since the root cause is that Google doesn't provide them with specific UA Strings.

@Don-Swanson commented on GitHub (Sep 14, 2025): This is unfortunately a side effect of the User Agents being used. When certain user agents are utilized the results provided by google may or may not have result favicons. If we are able to find a way to utilize modern User Agents again, this should auto resolve, or if you can find an unblocked UA it should resolve as well. With that said, I will close this as Not a Bug since the root cause is that Google doesn't provide them with specific UA Strings.

kerem commented

2026-02-25 20:36:26 +03:00

Author

Owner

@billkewl commented on GitHub (Sep 15, 2025):

Maybe it's asking too much but is it possible to retrieve favicon from duckduckgo instead?

@billkewl commented on GitHub (Sep 15, 2025): Maybe it's asking too much but is it possible to retrieve favicon from duckduckgo instead?

kerem commented

2026-02-25 20:36:26 +03:00

Author

Owner

@Don-Swanson commented on GitHub (Sep 15, 2025):

Unfortunately, yes, because the search results won’t match, so there would be a lot of additional overhead to pull all the icons on our own.

@Don-Swanson commented on GitHub (Sep 15, 2025): Unfortunately, yes, because the search results won’t match, so there would be a lot of additional overhead to pull all the icons on our own.

kerem referenced this issue

2026-02-25 20:37:13 +03:00

[PR #734] [MERGED] Remove "/" before endpoints & tags #957

kerem referenced this issue

2026-02-25 20:37:15 +03:00

[PR #762] [MERGED] Fix image view #967