Selfhosted

39260 readers

189 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Pi-Hole and Searxng Question (lemmy.one)

submitted 11 months ago by Grenfur@lemmy.one to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

Hey all,

I'm relatively new to self hosting. I set up a SearxNG on my local network and then recently set up Pi-Hole. Searx is running in a docker container and Pi-Hole is not. However, after setting up Pi-hole the IP I use to connect to Searx now directs to the default the default placeholder page. So my Pi-hole runs on 192.168.0.19/admin and Searx used to run just on 192.168.0.19. I'm guessing there's a config somewhere that I can change to make both work at once I'm just not sure where. Google was less than helpful (or maybe I'm an idiot lol) so I was hoping someone here may have run into a similar issue.

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

[–] Boring@lemmy.ml 3 points 11 months ago* (last edited 11 months ago) (1 children)

/admin isnt a port it is just a subdirectory of lighttpd, the webpage pihole uses to display itself. If you don't specify a port, your browser defaults to port 80 for http, and 443 on https.

You can use the netstat -a while the webpage is open on your terminal to find what port is in use.

In docker you can find this and change it in the yaml file if you deployed that way, otherwise you may need to kill the container and remake it and choose a different port when specifying the "p" in docker.

If you didn't use docker for pihole you will have to navigate to /etc/lighttpd/lighttpd.conf and modify the port number there.

Edit: if you want to add a reverse proxy to this equation with a an actual domain name and real SSL certs check out this video: https://www.youtube.com/watch?v=qlcVx-k-02E

[–] Grenfur@lemmy.one 2 points 11 months ago

Eyy! That got it! I think I'm still going to set up nginx to make it easier as I add more self hosts so I'm not trying to memorize everything's port. Thank you kindly for your time!