Selfhosted

46672 readers

432 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

[email protected]

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

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

[–] 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".