18
How to access self hosted SearXNG?
(self.selfhosted)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Aug 2023
18 points (100.0% liked)
Selfhosted
40677 readers
312 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
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?
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 piholeTo launch the container i used
sudo docker-compose up -dAnd there really isn't an error as i just don't know how to actually access it
Are you accessing this via 127.0.0.1?
If not you need to change it to
8080:8080instead of127.0.0.1:8080:8080Okay show me the docker-compose file
Where is this running on? If this is your own computer, http://127.0.0.1:8080 is how you access it. If it is another computer, remote or not, you need to change how you start the container to be able to access it.