[GH-ISSUE #824] [BUG - Android] Firefox Custom Search Engine - Error Connecting #520

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

Originally created by @tootbrute on GitHub (Aug 10, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/824

Describe the bug
I can't get Firefox Android to add Whoogle as a custom search engine. It says "Error connecting to Whoogle..." It works happily on my desktop Fedora 36 using Brave and Firefox though.

It gives me the error: "Error connecting to "Whoogle""

I tried http, https, and just the domain name but I got the same error.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Settings
  2. Click on 'Search'
  3. Click on + Add search egine
  4. Type ' blah.com/search?q=%s
  5. Shows error "Error connecting to blah..."

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] 0.7.4
  • Not sure

Smartphone (please complete the following information):

  • Device: Asus Zenfone Max M2 [X01AD]
  • OS: [e.g. iOS8.1]
  • Browser Firefox
  • Version 103.2.0
Originally created by @tootbrute on GitHub (Aug 10, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/824 **Describe the bug** I can't get Firefox Android to add Whoogle as a custom search engine. It says "Error connecting to Whoogle..." It works happily on my desktop Fedora 36 using Brave and Firefox though. It gives me the error: "Error connecting to "Whoogle"" I tried http, https, and just the domain name but I got the same error. **To Reproduce** Steps to reproduce the behavior: 1. Go to Settings 2. Click on 'Search' 3. Click on + Add search egine 4. Type ' blah.com/search?q=%s 5. Shows error "Error connecting to blah..." **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [ ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [x] Version [version number] 0.7.4 - [ ] Not sure **Smartphone (please complete the following information):** - Device: Asus Zenfone Max M2 [X01AD] - OS: [e.g. iOS8.1] - Browser Firefox - Version 103.2.0
kerem 2026-02-25 20:35:57 +03:00
  • closed this issue
  • added the
    bug
    Stale
    labels
Author
Owner

@pieslinger commented on GitHub (Aug 10, 2022):

Did you see #703?

<!-- gh-comment-id:1210127916 --> @pieslinger commented on GitHub (Aug 10, 2022): Did you see #703?
Author
Owner

@benbusby commented on GitHub (Aug 10, 2022):

Unfortunately I'm not able to replicate this with my Android device. The only Android device I have is an old tablet though, so it's not the best for testing this kind of stuff.

I'd recommend checking your server logs when you're attempting to add the engine and see if there's some endpoint it's attempting to reach when you add it. If there's something weird in there, I can help debug further that way, otherwise it'd likely be best for someone with an Android device to try and debug this.

<!-- gh-comment-id:1210892147 --> @benbusby commented on GitHub (Aug 10, 2022): Unfortunately I'm not able to replicate this with my Android device. The only Android device I have is an old tablet though, so it's not the best for testing this kind of stuff. I'd recommend checking your server logs when you're attempting to add the engine and see if there's some endpoint it's attempting to reach when you add it. If there's something weird in there, I can help debug further that way, otherwise it'd likely be best for someone with an Android device to try and debug this.
Author
Owner

@tootbrute commented on GitHub (Aug 11, 2022):

Logs from this whoogle container are pretty weird. Lots of TOR in here.

$ sudo docker ps
CONTAINER ID   IMAGE                                 COMMAND                  CREATED       STATUS                   PORTS                                                                                  NAMES
c5efb0cc6c32   benbusby/whoogle-search:latest        "/bin/sh -c 'misc/to…"   7 days ago    Up 7 minutes (healthy)   0.0.0.0:5000->5000/tcp, :::5000->5000/tcp                                              whoogle-search
$ sudo docker logs c5efb0cc6c32 --since 5m
Aug 11 08:25:06.000 [notice] New control connection opened from 127.0.0.1.
Aug 11 08:25:06.000 [notice] Heartbeat: Tor's uptime is 0:01 hours, with 1 circuits open. I've sent 318 kB and received 2.66 MB. I've received 14 connections on IPv4 and 0 on IPv6. I've made 5 connections with IPv4 and 0 with IPv6.
Aug 11 08:25:06.000 [notice] While bootstrapping, fetched this many bytes: 556367 (consensus network-status fetch); 13361 (authority cert fetch); 2031905 (microdescriptor fetch)
Aug 11 08:25:37.000 [notice] New control connection opened from 127.0.0.1.
Aug 11 08:25:37.000 [notice] Heartbeat: Tor's uptime is 0:01 hours, with 1 circuits open. I've sent 318 kB and received 2.66 MB. I've received 15 connections on IPv4 and 0 on IPv6. I've made 5 connections with IPv4 and 0 with IPv6.
Aug 11 08:25:37.000 [notice] While bootstrapping, fetched this many bytes: 556367 (consensus network-status fetch); 13361 (authority cert fetch); 2031905 (microdescriptor fetch)
Aug 11 08:25:55.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
Aug 11 08:25:56.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Aug 11 08:25:57.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Aug 11 08:25:57.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Aug 11 08:25:57.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Aug 11 08:25:59.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Aug 11 08:25:59.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Aug 11 08:26:00.000 [notice] Bootstrapped 100% (done): Done
Aug 11 08:26:07.000 [notice] New control connection opened from 127.0.0.1.

No info about trying to add it to firefox. Tried a few times and checked these logs unless there is a better way to get logs.

About issue #703 I did check that. I don't have authentication on my whoogle. Also I just restarted all of docker before taking these logs.

<!-- gh-comment-id:1211697189 --> @tootbrute commented on GitHub (Aug 11, 2022): Logs from this whoogle container are pretty weird. Lots of TOR in here. ``` $ sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c5efb0cc6c32 benbusby/whoogle-search:latest "/bin/sh -c 'misc/to…" 7 days ago Up 7 minutes (healthy) 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp whoogle-search ``` ``` $ sudo docker logs c5efb0cc6c32 --since 5m Aug 11 08:25:06.000 [notice] New control connection opened from 127.0.0.1. Aug 11 08:25:06.000 [notice] Heartbeat: Tor's uptime is 0:01 hours, with 1 circuits open. I've sent 318 kB and received 2.66 MB. I've received 14 connections on IPv4 and 0 on IPv6. I've made 5 connections with IPv4 and 0 with IPv6. Aug 11 08:25:06.000 [notice] While bootstrapping, fetched this many bytes: 556367 (consensus network-status fetch); 13361 (authority cert fetch); 2031905 (microdescriptor fetch) Aug 11 08:25:37.000 [notice] New control connection opened from 127.0.0.1. Aug 11 08:25:37.000 [notice] Heartbeat: Tor's uptime is 0:01 hours, with 1 circuits open. I've sent 318 kB and received 2.66 MB. I've received 15 connections on IPv4 and 0 on IPv6. I've made 5 connections with IPv4 and 0 with IPv6. Aug 11 08:25:37.000 [notice] While bootstrapping, fetched this many bytes: 556367 (consensus network-status fetch); 13361 (authority cert fetch); 2031905 (microdescriptor fetch) Aug 11 08:25:55.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors Aug 11 08:25:56.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Aug 11 08:25:57.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits Aug 11 08:25:57.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits Aug 11 08:25:57.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits Aug 11 08:25:59.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Aug 11 08:25:59.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Aug 11 08:26:00.000 [notice] Bootstrapped 100% (done): Done Aug 11 08:26:07.000 [notice] New control connection opened from 127.0.0.1. ``` No info about trying to add it to firefox. Tried a few times and checked these logs unless there is a better way to get logs. About issue #703 I did check that. I don't have authentication on my whoogle. Also I just restarted all of docker before taking these logs.
Author
Owner

@benbusby commented on GitHub (Aug 11, 2022):

Nothing weird about that -- the Tor service is started by default in the Whoogle container, so those startup logs are to be expected.

The default server that Whoogle uses doesn't actually report info about new requests, so I think I'll have to add a way of enabling debugging within the container. I'll try to get to that soon.

<!-- gh-comment-id:1212186766 --> @benbusby commented on GitHub (Aug 11, 2022): Nothing weird about that -- the Tor service is started by default in the Whoogle container, so those startup logs are to be expected. The default server that Whoogle uses doesn't actually report info about new requests, so I think I'll have to add a way of enabling debugging within the container. I'll try to get to that soon.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 15, 2025):

This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.

<!-- gh-comment-id:3292230100 --> @github-actions[bot] commented on GitHub (Sep 15, 2025): This issue has been automatically marked as stale due to inactivity. If it is still valid please comment within 7 days or it will be auto-closed.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2025):

Closing this issue due to prolonged inactivity.

<!-- gh-comment-id:3323438878 --> @github-actions[bot] commented on GitHub (Sep 23, 2025): Closing this issue due to prolonged inactivity.
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#520
No description provided.