this post was submitted on 02 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

521 readers
6 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 2 years ago
MODERATORS
 

hey folks!

finally starting with my homelab and i have adguard and homer up and running! i am having a couple of issues however, and i haven't really found much that makes sense to me yet (sorry - super new!):

i'm on ubuntu server FWIW

initially, i could only access the adguard web interface via the ip with the port number - i.e. 10.0.0.1:3000; after i started up Homer, though, i could only access it without the port. not sure this is so much a problem, but i think it may have some impact on my actual problem, which is:

i want to configure domain names for the services on my intranet, so i initially tried to use adguard to do this. my first problem arose when i couldnt type port numbers in the DNS rewrite, so i couldn't access my homer via DNS because that IP only redirected to my adguard. due to this, i read that possibly setting up nginx proxy manager and creating a reverse proxy would be good practice so that the proxy could divvy up the domain names itself. so i spun that up in docker, but now i can't start adguard because port 443 is taken by nginx (which i thought could solve this port conflict issue?) - any idea how i can go about this to allow both adguard to run with nginx and help solve my domain name issue with nginx?

โ€‹

i'm just looking for some general direction to help my understanding - definitely don't want y'all to do homework for me haha; and apologies if these are dumb questions - genuinely just trying to skill up in linux b/c this is the first time i've seriously used it

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago

Dns only handles to domain but not the port. So if you have a client that normally just checks 80 or 443, that's what it'll assume you want, which is a pain.

There are two paths I'd say would be reasonable. The first is adding more IP addresses to the host so you can publish the docker port to a specific access. Then you don't need the port. You will have to specify specific addresses to listen on so services like nginx don't just listen on all IPs on the host.

The other thing would be to change your nginx config to have multiple server directives that looks for specific Host headers and point each server to what you want via upstream directives that can have the port specified. http://nginx.org/en/docs/http/ngx_http_upstream_module.html for details.

If you need more than that, let me know and I'll see if I can paint you in the right direction.