Reverse proxy error

[fahadshery]

This fixed all my web issues but I can’t make it work on the iOS.
Getting NSURLErrorDomain - 1003 error when tried to connect via the App on an iPhone

[fschade (Floor)]

Weird, if have read everything, and configured it properly, but i still get ERR_CONNECTION_REFUSED.

All other reverse proxy rules are working. So it must be something with HA.

[mwav3 (Tim)]

Home Assistant relies on websockets, which basically are a “stay open” type of connection, and requires extra configuration on the reverse proxy side to allow websockets to work. Which proxy are you trying to use?

To rule out the block issue on the Home Assistant side, you can TEMPORARILY add this to your config:

http:
    use_x_forwarded_for: true
    trusted_proxies:
      - 0.0.0.0/0 

This will completely open the Home Assistant block and allow any reverse proxy to go through. If this works then the issues is not specifying the right IP for the trusted proxy. If it still doesn’t work even after allowing all IPs, the issue is on your reverse proxy configs and likely not on the Home Assistant side (likely not configuring websockets properly). I say Temporarily set this only for testing because leaving it like this overrides the security and leaves your system vulnerable to attacks, which is the reason specifying this IP was added as a requirement last year.

Update:
Took another look at your post and possibly its just a YAML formatting issue. Move the IP to another line and indent it with a dash instead of putting it right after the colon. Try this instead of what you have:

http:
    use_x_forwarded_for: true
    trusted_proxies:
      - 192.168.178.whatever

[fschade (Floor)]

@mwav3 , thanks for helping out. With this setup i have the same result:

Same issue with these settings:

these are the reverse proxy settings:

[mwav3 (Tim)]

That appears you are using the NGINX proxy manager - if so checkout this post. You need to go to advanced settings and specify additional info. This user was able to get it working successfully with the config they posted

Nginx Reverse Proxy Set Up Guide – Docker

Below are some screenshots on how to get to the Advanced section I was referring to. (I don’t post much so pardon this messy post if it doesn’t come through right, ha). [image] [image] [image] You may notice I commented out the resolver line, I’m not sure that was necessary but I think it prevented the proxy from coming back online in my particular case. The final screenshot doesnt show all the text in that advanced box but my previous post has all the text that I put in there. Hope this…

[fschade (Floor)]

@mwav3 , thanks again. i don’t use a NGINX reverse proxy. I use the standard build in reverse proxy from synology.

All the setting they are talking about are not in here or in a different location.
What do you use as a reverse proxy?

[mwav3 (Tim)]

I’m not too familiar with synology, but I know it’s more locked down then just running on a Linux os like Ubuntu or debian.

I use the SWAG docker container, which sets up nginx and some other tools like ssl and fail2ban. I’m running it on Ubuntu.

GitHub - linuxserver/docker-swag: Nginx webserver and reverse proxy with php...

The thread I linked in the last post contains a comprehensive setup guide. Pretty sure you can run docker containers on synology, but it might be a little different from the guide. Guide is in the top post (linked below)

Nginx Reverse Proxy Set Up Guide – Docker

In light of the recent “hacking” stories, last week I set myself the goal of implementing Nginx. I read most related posts in this forum and elsewhere, but was unable to find a step by step guide for “enthusiasts” with limited it skills. Therefore I proceeded to do it the hard way: read, trial and error. Regretfully the forum was of no use as some of the individuals with “apparent subject matter experience” chose to offer condescending advice with no real benefit or substance. I do, however, w…

[fschade (Floor)]

@mwav3 thanks again. i will check this setup, but it seems a bit of big change for something that should work with the syno reverse proxy. But many thanks for your help!

[aldihome (Leon)]

I have HA in a docker container on a raspberry pi.
I use remote.it to proxy my network, since I could not edit port forwarding of the router.
SSH works flawless, but I am having problems accessing the web interface.

I added

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.0.0.1

to my config, but now I am getting Received X-Forwarded-For header from an untrusted proxy 127.0.0.1

I saw in this thread, that deleting proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; is the only solution (but with security risk?). But where can I edit my nginx, since I am using remote.it?

This is my config there:

EDIT: Guess it was just a typo. Thanks @w35l3y

[w35l3y]

@aldihome

172.0.0.1

172 or 127 ?

[dhruv (Dhruv Pandey)]

Worked for me as well. Thanks!

[moweME (Finn)]

In order to get my external access working, I had to set the password of the user account again.
Same password, same settings. HomeAssistant just needed propagate the password again(?)

[puche (Charles)]

Además, hay que agregar en nginx proxy manager, la opción websockets

[Moonbase59 (Matthias C. Hormann)]

Running HassOS 13.2 and HA Core 2024.11.1 and the Nginx Proxy Manager Addon, I found that my Dockers use the 172.30.32/23 network, so I could use either

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.4  # NPM Docker; Docker Network is 172.30.32/23

(the machine, more safe)

—or—

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.32.0/23  # Docker Network; NPM is 172.30.33.4

(the Docker network, less safe)

Thanks to all that have found out things in this long thread!