still *headdesks* | Home Assistant | Page 1

warped robin Jun 18, 2024, 10:56 AM

#

stop the container, see if you can still reach HA

covert arch Jun 18, 2024, 10:58 AM

#

stop HA's container?

warped robin Jun 18, 2024, 10:58 AM

#

Yes

covert arch Jun 18, 2024, 10:59 AM

#

'site can't be reached'

warped robin Jun 18, 2024, 10:59 AM

#

Then we know it is that container

covert arch Jun 18, 2024, 10:59 AM

#

that's if i go ip. if I go by domain name, i get the 502 error

warped robin Jun 18, 2024, 11:00 AM

#

Now to check that it's the config that you think you're editing that's mapped

covert arch Jun 18, 2024, 11:01 AM

#

suggesting there's a second configuration.yaml file?

warped robin Jun 18, 2024, 11:01 AM

#

Maybe

covert arch Jun 18, 2024, 11:05 AM

#

*facepalms

#

i'm a dumbass

#

yep

#

so, when I first made the docker container, I mistyped where the config folder was on the host system. Tried to copy everything to the right place and change the links in the docker compose. For some reason it acted like it was a new install, so I reversed that change in the compose file

#

Forgot I did that and have been editing the dead copy of the config all this time

#

I'm so sorry

#

copied the config to the real folder, restarted and immediately pulled up the login screen

#

it's spinning it's wheels loading data, but I at least have the start

#

that might be related to internal vs external network, since my phone on cell data is working just fine

#

everything was HTTP Status 200 on the main page except for manifest.json and lovelace, which both did an http 502

#

and that was an error in the proxy manager

warped robin Jun 18, 2024, 11:19 AM

#

Do you still get the untrusted proxy error in HA?

covert arch Jun 18, 2024, 11:19 AM

#

mostly. I'm still having a websocket issue now

#

no, not that error. I have something else new and exciting

#

2024-06-18T11:17:52.515655253Z Traceback (most recent call last):
2024-06-18T11:17:52.515671681Z   File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
2024-06-18T11:17:52.515688495Z     messages, upgraded, tail = self._request_parser.feed_data(data)
2024-06-18T11:17:52.515696499Z                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-06-18T11:17:52.515704874Z   File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
2024-06-18T11:17:52.515713333Z aiohttp.http_exceptions.BadStatusLine: 400, message:
2024-06-18T11:17:52.515720876Z   Invalid method encountered:
2024-06-18T11:17:52.515728223Z 
2024-06-18T11:17:52.515735390Z     b'\x16\x03\x01'
2024-06-18T11:17:52.515743329Z       ^```

warped robin Jun 18, 2024, 11:20 AM

#

That's something you can probably ignore for now

#

I'd suggest you check the forum for guides on nginx and HA

raven quailBOT Jun 18, 2024, 11:21 AM

#

You can find the community forum here

covert arch Jun 18, 2024, 11:21 AM

#

yeah, I'm thinking the websocket in NPM may not be -quite- doing what it's supposed to

covert arch Jun 18, 2024, 11:46 AM

#

that said, it's only an issue using the fqdn while on the same network, which I can work around. Mobile app has the feature to use a local address when on the local wifi, and as I'm likely the only one who will be using a laptop to access it, I can just make sure I only use ip when here

#still *headdesks*

#still headdesks