homelab

6773 readers

44 users here now

founded 4 years ago

MODERATORS

[email protected]

Issue setting SearXNG as Default Browser in Firefox (self.homelab)

submitted 13 hours ago* (last edited 9 hours ago) by root to c/[email protected]

4 comments fedilink hide all child comments

I recently setup SearXNG to take the place of Whoogle (since Google broke it by disabling JS free query results). I am following the same steps I've always done in adding a new default search engine.

Navigate to the address bar, right click "Add SearXNG" then go into settings and make it my default. After doing this, rather than using the local IP the instance is running at, Firefox uses https://localhost/search for some reason. I don't see a way to edit this in the settings section of Firefox. Anyone else experienced this?

Update: After updating the .env file with my IP address and bring docker down/ up, all is working as expected (able to use SearXNG via Caddy using the https:// address)

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 9 hours ago (1 children)

Benbusby pushed an update for whoogle last night to change the user agent to one that still operates fine, with a few css bugs.

[–] root 1 points 9 hours ago

He's a saint. I saw the commit last night and was waiting for an update. I have SearXNG working now but also left up my Whoogle VM. I'll try the update and keep using that until the lights go out :')

[–] [email protected] 3 points 11 hours ago* (last edited 9 hours ago) (1 children)

Could you give more information?

Is it running in the same machine you want to search from?

Is it running in a container (and which network mode)?

Have you changed the configuration of SearXNG? I think the default URL was localhost in some settings (like the hostname or base_url variables in both settings.yml and docker-compose.yml).

Also, it's been a while since I made SearXNG my default search engine, I used to use an extension since the Firefox way is less customizable.

[–] root 2 points 10 hours ago

Bingo! I missed a spot in the hidden .env file. After that I'm able to hit it and Caddy is able to generate the cert for me (I am using docker).

Thanks again!