Selfhosted
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!
view the rest of the comments
If the other services are exposed on local ports, you can have NPM forward to those.
By exposed you basically mean that I can reach them using my browser? I can reach my homeassistant web ui on port 8123 but when I try to forward to that port with the servers IP I get a 400 Bad Request error. I'm not sure if this is caused by nginx being unable to forward or by homeassistant not accepting the connection somehow
If you have any kind of firewall on your network, you might make sure it's not blocking that port with a rule. Here's a couple screenshots from my setup in case that helps.
The config in NPM
The config in HA's configuration.yaml
Try adding just the NPM IP and HA IP first, then add the docker internal network as well if you still have issues.
Thanks for the configuration example. Unfortunately it doesn't seem to work for me. I've replied to someone above with screenshots of what my configuration now looks like. The
base_url
option you use there wasn't available to me because it apparently has been deprecated and replaced withinternal_url
andexternal_url
.For homeassistant I had to add this in configuration.yaml
Where 172.21.0.2 is my NPM docker IP
Edit: its NPM IP and not HA like I wrote first time
Thanks. I tried it like this and still get a 400 Bad Request error.
Someone below mentioned adding some more IPs to the trusted_proxies list so I tried that as well without result. The IP I used for the reverse-proxy is the IP listed in portainer under the network for the proxy container. Just to reiterate, the container is running on a different device than homeassistant (technically same device but different VM but that shouldn't make a difference).
My NPM window looks the same as yours. Im not sure mate, I would try disabling firewall just to see is that the problem. Im not expert in that area and nothing else comes to my mind sorry. Im also running everything under one host
This. Also, make sure the proxy is proxying websocket traffic as well. I do it with pure nginx like this: