Update: No not the same config. After another check of the shellscript I noticed a difference in the volume-mapping and the path didn’t exist, causing probably the mentioned errormessage.
I’m seeing this when updating my Docker container with the latest stable version. If I update it with the latest version (getting a dev-version of HA) then it works fine. Same config.
Hmm, same here. Seems to happen when I try to do a backup snapshot. Using HTTP, not HTTPS (only local network access) so HTTP: is empty in my config
Running HASSIO on a pi4
Anyone with a clue?
22-11-02 00:53:42 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 122, in sentry_app_handle
reraise(*_capture_exception(hub))
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/_compat.py", line 56, in reraise
raise value
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 112, in sentry_app_handle
response = await old_handle(self, request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 138, in system_validation
return await handler(request)
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 156, in token_validation
return await handler(request)
File "/usr/src/supervisor/supervisor/api/proxy.py", line 169, in websocket
await server.prepare(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_ws.py", line 137, in prepare
protocol, writer = self._pre_start(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_ws.py", line 239, in _pre_start
assert transport is not None
AssertionError
Thank you for the tip!
Had the same issue, after a couple of tries, I found out that I had linked my Netatmo to HASS.
Just logged in onto Netatmo account and deleted the linkage - and now it works!
Removed DuckDNS, reinstalled… Still exists…
Added NGINX still exists.
Replaced SQL Lite DB with Maria DB… Still exists…
Added all config http: changes noted above… still exists.
Removed all apples devices… still exists.
Checked fire wall port forward rules (reboot router over and over and over) still exists.
Improved cooling solutions and new Pi power adapter… Still exists.
The only clue was these errors were being generated randomly throughout the day (and night)… when people were home and when they were away. The system did seem to get lots of them around sunrise and sunset. Often to a point of causing the system to crash.
Then I noticed that the web-hooks that MotionEye automatically generate contained a malformed IP address… I don’t use those web-hooks so I turned them off and set the MotionEye Integration configuration to NOT automatically created web hooks and
Ta Da… no more “aiohttp.server Error” at least for 48 hrs… which is a record.
I will know in a week or so… But I suspect when all of my security cameras would switch from “day mode” to IR dark mode. MotionEye would spam HA with a bunch of malformed web-hooks.
