-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Forward Traffic to Home Assistant VM via Nginx Proxy Manager on TrueNAS Scale #4219
Comments
Hi, I am not familiar with TrueNAS Scale or use Home Assistant, but willing to give it a go... What kind of error is returned, if any, when you try to connect to that proxy host? From your description, I understood you have included the Home Assistant IP (or its FQDN, which would be resolvable by DNS inside that subnet) as the "Forward Hostname / IP" inside that NPM proxy host, plus the protocol (http or https) Home Assistant is listening with and the corresponding TCP port for that. |
Discussed in #4213
Originally posted by rrterrorr December 8, 2024
Hello,
I am currently running a TrueNAS Scale server with several Docker apps, including Nginx Proxy Manager (NPM). All of my Docker apps are working fine with NPM, and I can access them without issues. However, I also have a Home Assistant VM on the server (on a different IP but within the same subnet), and I am unable to forward traffic to it via NPM.
The network configuration on TrueNAS is set to BR1, and all apps and VMs, including the Home Assistant VM, are running on this network. My goal is to forward traffic to the Home Assistant VM so that I can eventually stop using Nabu Casa for remote access.
I’ve tried setting up the proxy for Home Assistant in NPM, but the forwarding doesn’t seem to work. I’m looking for advice on how to set up the correct routing or port forwarding for this VM through NPM.
Has anyone encountered this issue or can provide guidance on how to achieve this setup?
Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: