Firefox

20340 readers

158 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

Firefox search is resolving to IP instead of hostname (lemmy.world)

submitted 5 months ago by root@lemmy.world to c/firefox@lemmy.ml

6 comments fedilink hide all child comments

I have a SearXNG instance running locally, and I have a proxy entry for this (search.home). When I go to https://search.home/ in Firefox, it works as expected and brings me to SearXNG, however if I try adding this as my default search, it instead resolves to the IP and not the hostname, which fails because the IP does not have a cert on it and it tries to hit it with https (as would work with the hostname).

This works in Firefox mobile, and every other web browser I've tried on desktop, just not Firefox for some reason. I've tried various about:config changes but so far no luck. Anyone else have a workaround for this? It would be nice if Firefox showed you what it actually has saved for the url/hostname/IP of the search engine in the Search section of the Settings, but sadly it just has the name and shortcut listed.

you are viewing a single comment's thread
view the rest of the comments

[–] cypherpunks@lemmy.ml 2 points 5 months ago* (last edited 5 months ago)

I see. What a mess.

The instructions at https://docs.searxng.org/admin/installation-docker.html mention that the docker image (which that page tells you to just pull and run) has its "sources hosted at" https://github.com/searxng/searxng-docker and has instructions for running it the image without docker-compose.

But, the Dockerfile source for the image is actually in the main repo at https://github.com/searxng/searxng/blob/master/Dockerfile and the searxng-docker repo actually contains a docker-compose.yaml and different instructions for running it under compose instead.

Anyway, in the docker-compose deployment, SEARXNG_BASE_URL (yet another name for this... neither SEARXNG_URL or BASE_URL, but apparently it sets base_url from it) is constructed from SEARXNG_HOSTNAME on line 58 here: https://github.com/searxng/searxng-docker/blob/a899b72a507074d8618d32d82f5355e23ecbe477/docker-compose.yaml#L58

If I had a github account associated with this pseudonym I might open an issue or PR about this, but I don't and it isn't easy to make one anymore 😢