Yes it is. See HTTP - Home Assistant
See basic_auth (Caddyfile directive) — Caddy Documentation
Probably best to do a redir instead of a rewrite here. This will redirect the entire page instead of just rewriting the request internally.
Yes it is. See HTTP - Home Assistant
See basic_auth (Caddyfile directive) — Caddy Documentation
Probably best to do a redir instead of a rewrite here. This will redirect the entire page instead of just rewriting the request internally.
alrighty then the home assistant confioguration.yaml file is this :
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
http:
trusted_proxies:
- 192.168.1.40
should I also add my subnet mask ? and with /24 at the end ?
When I restart HA, and try to access with the hass. domain .com, the page gives :
400: Bad Request
I’ll take care of the auth and redir over the week end
Yup I did sorry, so with this for the HA yaml :
http:
use_x_forwarded_for: true
trusted_proxies:
- 192.168.1.40
- 250.250.250.0/24
it still doesn’t work :s 400 : bad request
and for the redir i’ve got that (cannot try yet, i’ll update it on the NAS tuesday):
# Resume subdomain
resume. domain. com {
root * /usr/local/www/resume
redir * resume. domain. com/resume.html
file_server
}