Setting Searx as default search engine in Android Chromium based

[theQureshi]

Hi awesome fellas!

I just installed Searx on a VPS and everything is working perfectly fine except OpenSearch on Android Chromium based browsers.

I have tried going through GitHub issues but I couldn't find anything. Can anybody help?

• Installation followed: Manual (not Docker)
• Installation path: sub.domain.com/searx
• base_url in settings.yml: "https://sub.domain.com/searx"
• Search method: Default is POST but I have tried GET
• Browser: Brave (Chromium based)
• More info:
  -- This seems like a known issue: Chromium-based browsers (Android) don't detect searx #1666, base_url setting doesn't force domain when adding searx instance to address bar #2317, and others.
  -- Seems like it was fixed in [fix] opensearch on chromium for android #2132

Thanks :)

[unixfox]

Did you install Searx from the master branch?

[return42]

base_url in settings.yml: "https://sub.domain.com/searx"

Chromium does not like path names in the URL. On my intro page at https://darmarit.org/ I added the following line:

<link title="searx" type="application/opensearchdescription+xml" rel="search" href="/searx/opensearch.xml">

When I want to add my engine to a chromium browser I navigate to the root URL and then I open the preferences in Chromium, where I now can find a entry of my search-engine ..

This was the only robust solution I found.

[theQureshi]

Thank you for your input.

Where did you add the above-mentioned line of code? Could you please direct me to the file name?

[return42]

In the intro page .. when your root URL is https://sub.domain.com .. the (HTML) page that is shown under this URL has to include the line.

On my host a apache is listening at the public URL https://darmarit.org/ and in my apache configuration the DocumentRoot is:

DocumentRoot /srv/http
<Directory /srv/http>
    AllowOverride None
    Require all granted
</Directory>

With, the intro page is located at /srv/http/index.html. This is typical for archlinux, but you might have a complete different setup .. do you use nginx? ..

Ask yourself, which page is behind your "https://sub.domain.com"? This is the intro page, the DocumentRoot.

[theQureshi]

Thanks, I will look into this.