Issues with Nginx Reverse Proxy

Configuration
,
1

Hey Guys -

I’m trying to get HomeAssistant to work behind my nginx reverse proxy to go to https://mydomain.com/homeassistant as I’ve configured numerous other apps to, but cannot get it to work. I couldn’t find configs which weren’t only for the base domain online, so am sure that’s my issue. Below are the configs I’ve tried as well as a few other notes. Any help would be appreciated!

configuration.yaml (Appended everything below “scene:…” line - 192.168.0.35 is ip of nginx)

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
http:
  # For extra security set this to only accept connections on localhost if NGINX is on the same machine
  # Uncommenting this will mean that you can only reach Home Assistant using the proxy, not directly via IP from other clients.
  # server_host: 127.0.0.1
  use_x_forwarded_for: true
  # You must set the trusted proxy IP address so that Home Assistant will properly accept connections
  # Set this to your NGINX machine IP, or localhost if hosted on the same machine.
  trusted_proxies: 192.168.0.35

nginx Config Attempt #1

location /homeassistant/ {
proxy_pass http://192.168.0.212:8123/;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}

location /homeassistant/api/websocket/ {
proxy_pass http://192.168.0.212/api/websocket/;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

nginx Config Attempt #2

	location /homeassistant/ {
		proxy_http_version 1.1;
		proxy_set_header Connection "";
		proxy_pass http://192.168.0.212:8123/;
	}
	location /homeassistant/api/websocket/ {
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "upgrade";
		proxy_http_version 1.1;
		proxy_pass http://192.168.0.212:8123/api/websocket/;
	}

Notes

  • When browsing to either path above (https://mydomain.com/ha/), it only partially loads the interface showing a black page with a grey bar at the very top
  • All reverse proxy settings for my nginx server are within the nginx.conf file
  • nginx is running on Windows @ 192.168.0.35
  • nginx applies 3rd party signed SSL

Any suggestions? Thanks!

2

Can’t be done. There’s a long technical explanation on the forums somewhere as to why, but you need to do

https://xxxxxxxxx.yourdomain.com

This is not possible for homeassistant…

https://yourdomain.com/xxxxxxxxx
1 Like
3

following as this is my next goal…

4

Is there any good documentation how to make this - I tried with the ngix proxy manger but faild now I wanted to try with the ngix reverse proxy but failing again :frowning:

I want to have HA on https://mystuff.duckdns.org/HA and https://mystuff.duckdns.org/BW for Bitwarden … or I can do https://ha.mystuff.duckdns.org and https://bw.mystuff.duckdns.og
-> if I do https://ha.mystuff.duckdns.org to I have to register the “ha” with duckdns.org - or is it enough that I have mystuff.duckdns.org

5

As I said above, that can’t be done.

Just the mystuff.duckdns.org is all you need to register with duckdns, and if you’re using nginx proxy manager it will automatically generate a separate certificate for each of your subdomains. That’s how I currently have multiple services set up.

1 Like
6

Thx for the repley - I tried this with the nginx proxy manager (npm) but I allway got errors creating the certificates -
I clould easily create the certificates for mystuff.duckdns.org -> but this was with the duckdns adon - any Ideas what I could try next ?
what is your http config in “configuration.yaml” ?

7

What’s the error in nginx proxy manager?

My http section is

http:
  ip_ban_enabled: true
  login_attempts_threshold: 3
  use_x_forwarded_for: true 
  trusted_proxies: !secret trusted_proxies
8

Hi!
I’am a studid f$%k! - I changed to router config - but forgot that I have a second rounter from the ISP!!! (I have 2 locations and made the first config at the other location) witch had no portforwarding :frowning: I now configured the second router to the DMZ …
this has cost me hours!

I’m sorry that it now also cost you time too!

so what is my learning: Please check the ports - the error Messages are not very good!

1 Like
9

Glad you have it sorted.
Once it’s working it’s great and simple.

1 Like
10

Hi!

again, you said you have bitwarden also running -
how did you get the certificates to bitwarden config - cause the proxymanger made new certificates for bw.mystuff.duckdns.org
thx and cheers

11

I don’t understand the question. The reverse proxy manages the certificates, bitwarden never needs to know about them.

12

Make sure SSL is set to false in bitwarden config

1 Like