-
Notifications
You must be signed in to change notification settings - Fork 1
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
HTTP integration is not set-up for reverse proxies #9
Comments
Hi @gatonero this is not about a regular proxy device that you'd use in your LAN to protect your access the internet. A 'reverse-proxy' means a service 'inside a server' that takes incoming HTTP requests and does some filtering, before handing them to another service that actually handles those HTTP requests.
so from you Browser client, on a different device, you don't but localhost but you need to put the hostname or address of the device running Home Assistant Docker Other than that, it is quite possible that your Home Assistant settings for http integration have some missing settings. Home Assistant has moved on lots since the version I last tested with this, and you may need some additional 'configuration.yaml' style settings. See the example in https://community.home-assistant.io/t/http-integration-is-not-set-up-for-reverse-proxies/313284/5 (although this uses a plugin that you may not have). Guten glück |
Thanks a lot. I will continue to fiddle around and take your steps as a template. |
Sure, @gatonero , you can fork the project then change what you need in your own fork and keep only the useful bits from here. Enjoy! |
Thank you! 🙂 |
@artmg Thanks, your commit worked for me. |
Vielen Dank für diese Anleitung!
Bei dem ersten Aufruf von http://localhost erhalte ich "400: Bad Request" und finde in den Logs folgenden Eintrag:
`Running as 1000:1000
Initializing venv in /var/tmp/venv
Starting homeassistant
2023-02-09 12:36:57.382 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 172.26.0.2, but your HTTP integration is not set-up for reverse proxies`
In meinem LAN befindet sich ein reverse proxy. Aber der sollte bei einem Zugriff auf localhost doch keine Rolle spielen?
The text was updated successfully, but these errors were encountered: