#it does have an internal ip but nginx is
1 messages ยท Page 1 of 1 (latest)
XD 1 moment also I don't think it shows in the log file or I don't see it cause I'm blind
1 moment tho
lol can't paste images. and it does show the ip of the connecting proxy but I put that ip in. it's 192.168.1.127
for nginx ip
not for HA
yes MANY TIMES
my logs are full of errors rn cause I updated from a relatively old version
Those errors could be causing you issues with the YAML not being loaded
Oh, and you ran the config check command?
To check your configuration use the command for your install method:
idk how I should go about fixing those errors atm. and no what is the command
Work the errors one at a time, bringing your config up to date
I got testing configuration at /config and nothing else
well i guess I'll try to remove everything from the config/data directory except the config.yaml and see if that helps
cleared the directory. no more errors, same issue with proxy
@valid wraith
what is above use_x_forwarded_for in your config? That should be a part of http:
here is the full config since I don't think it's got any sensitive info:
# 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:
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1
- 192.168.1.127
- 172.16.0.0/12
- 192.168.1.0/24
- ::1
server_host: 0.0.0.0
server_port: 8123
I don't really see any issues so I don't know why it's failing
full error: 2023-10-10 15:09:59.012 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 192.168.1.127
Looks good. You're sure this is the config this HA session is using? ๐
idk what other config it would use. is there a way for me to test and or find the real config file?
if I just chuck random characters on a line would that throw an error?
I could check that way
You could comment out scene:, save, and then restart and see if scenes are gone
Yeah you could throw a random character too
2023-10-10 15:22:18.563 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: in "/config/configuration.yaml", line 10, column 13: Unable to read file /config/automations.yaml.. Activating safe mode
so yes
it is using that file
Hmm I don't know why it wouldn't take. Config looks good.
same
Hey @quartz blaze sorry about the ping but since no one else has any ideas since this is supposedly supposed to be working I thought a dev might have some more insight as to what is going wrong. Do you think you can give us/me some insight?
Nope
damn. wtf am I to do XD
Mostly because you pulled me into a conversation, which is kinda demanding
So, not really interested in jumping in because of that
I don't want stuff like that to work, ever.
so had to install nano on the container and then manually edit the configuration file from terminal since it was not applying properly from the mount. Container is alpine so apk update and apk install nano for those in the future