this post was submitted on 02 Aug 2023
15 points (94.1% liked)

Selfhosted

40149 readers
665 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
15
How to access self hosted SearXNG? (lemmy.blahaj.zone)
submitted 1 year ago by Barrymore@lemmy.blahaj.zone to c/selfhosted@lemmy.world
6 comments fedilink hide all child comments
 

I followed the steps laid out in this guide and have a docker container for all services needed up and running, with the searxng container running on port 8080. I, however, am not sure how to actually access the search engine. I tried going to the server address in my web browser, including the port, but nothing shows up. I have another container running pihole, so i know i can access other containers web interfaces. Any help would be appreciated. Thanks in advance!

top 6 comments
sorted by: hot top controversial new old
[–] eskuero@lemmy.fromshado.ws 2 points 1 year ago

Run docker ps and check what port the container claims to have been mapped on the host.

[–] MaggiWuerze@feddit.de 1 points 1 year ago* (last edited 1 year ago)

Looking at the compose and .env file you have to just call the hostname of your machine on port 80:

SEARXNG_HOSTNAME=${SEARXNG_HOSTNAME:-http://localhost:80}

Since that is probably already taken you might have caddie not starting properly

[–] ArbiterXero@lemmy.world 0 points 1 year ago (1 children)

What port did you expose it on through docker?

Within docker, the server port is internal to docker (like a vm) and then there’s an external port that you map it to on the host…

Can you give me the command you use to launch it?

What is the error you get in the browser? Timeout? 500?

[–] Barrymore@lemmy.blahaj.zone 0 points 1 year ago (2 children)

Thanks so much for a quick reply, you're awesome! I believe still 8080, i didn't set a custom port anywhere, here is my docker ps

nathan@pop-os /usr/local/searxng-docker$ sudo docker ps 1 ↵ CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 122541a0442e redis:alpine "docker-entrypoint.s…" 26 minutes ago Up 26 minutes 6379/tcp redis 8031ada30eea searxng/searxng:latest "/sbin/tini -- /usr/…" 26 minutes ago Up 26 minutes 127.0.0.1:8080->8080/tcp searxng cdf75064d7c7 pihole/pihole:latest "/s6-init" 17 hours ago Up 11 hours (healthy) 0.0.0.0:53->53/udp, :::53->53/udp, 0.0.0.0:53->53/tcp, :::53->53/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:67->67/udp, :::80->80/tcp, :::67->67/udp pihole

To launch the container i used

sudo docker-compose up -d

And there really isn't an error as i just don't know how to actually access it

[–] MangoPenguin@lemmy.blahaj.zone 3 points 1 year ago

Are you accessing this via 127.0.0.1?

If not you need to change it to 8080:8080 instead of 127.0.0.1:8080:8080

[–] ArbiterXero@lemmy.world 1 points 1 year ago

Okay show me the docker-compose file