this post was submitted on 22 Jun 2023
4 points (83.3% liked)

Selfhosted

46672 readers
618 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 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
4
Home Assistant with proxy (bridge network to host network connection) (tslemmy.duckdns.org)
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
8 comments fedilink hide all child comments
 

This is more of a docker question than a selfhosted question, but i think that most of people here should be familiar with docker.

HA runs with network-mode : host (in order for autodiscovery to work) when my Nginx Proxy Manager is running on a bridge network (and in a different docker-compose.yml file), which makes them not see each other as far as I know. Could I maybe add an additional network to the HA like this:

networks:
  default:
    driver: host
  nginxnetwork:
     external: true
top 5 comments
sorted by: hot top controversial new old
[–] b1g_bake 1 points 2 years ago

I don't have it setup this way myself. I just have nginx point to http://1.2.3.4:8123 where 1.2.3.4 is the LAN IP of your docker host.

I know there are ways to connect containers with the backend docker network and I think that is what you are trying to do. I've seen examples for Caddy and Traefik doing it this way to make setup "easier".

[–] [email protected] 0 points 2 years ago (1 children)

Ill jump in while you are waiting on answer from more experienced user. My HA runs on host network and most of other containers are on their default network including NPM. NPM can manage them all, but I think you have to enable access from additional reverse proxy address in HA config

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (2 children)

I have this in my configuration.yaml

http: use_x_forwarded_for: true trusted_proxies: - 10.0.0.200

10.0.0.200 should be your npm docker IP

[–] [email protected] 1 points 2 years ago

I dont know how to use code block in jerboa lol.

[–] [email protected] 1 points 2 years ago

I do have this setup, but i don't think that npm can reach the HA, i have tried through direct IP and 127.0.0.1 and none of them seemed to work.

load more comments
view more: next ›