aiohttp.server message="Bad status line 'Invalid method encountered'" #73885
Comments
|
I have the same issue after upgrading my containerized HA from 2022.5.2 to 2022.6.7 Error I'm seeing: This happens upon startup since the upgrade. Using old container fortunately worked okay |
|
Not an issue in my case. After searching on the internet I came to conclusion that one of my devices in LAN is trying to connect to :8123 port using HTTPS. I've reviewed all phones and tablets and turned out it was my sons device. This was coincidence that it happened after upgrade. |
|
Having the same error and occors 18 times, but not every day: Logger: aiohttp.server Error handling request Running on RPI4 - core-2022.7.3 - Home Assistant OS 8.4 |
|
I see the same error accompanied by another one before it. I have changed IP address of my HA instance to test the possibility of the reason tomhash2 gave that some device is trying to connect to HA instance using HTTPS and port 8123. Since I still this these errors, the HTTPS and port 8123 is not the reason in my case. |
UPDATE: grep result: I opened config/.storage/auth file, went to this auth entry, found the device ID and searched for that again in the config directory. It was from my Galaxy watch. I have removed the auth token now. Might be helpful for people to search for devices using HTTPS for port 8123 to reach HA instance. BUT, in my case, I didn't change the IP address on my watch after I changed my HA IP. So, the watch couldn't have pinged my new IP with HTTPS and port 8123. So the aiohttp errors I got today morning (posted in the quoted message) are definitely not from my watch pinging 8123 using HTTPS. I will report back if I see the errors again. |
Saw the same error messages again. So what I did above didn't solve it. |
|
Any progress on this issue? I´ve got the error more than once (see above). Is there I could do to present more details? |
|
I'm facing same issue. Please help
|
|
Same issue here, any updates on this? I have a feeling it relates back to Nginx, which I'm using to reverse-proxy to my HA instance. I don't have any issues (I don't think) from the app on iOS, but when using Firefox on my laptop it can take ages to load HA through the reverse proxy and I see the same errors others are reporting... |
|
Hi. I have similar error in my case after update HA 2022.12. This is the log: In log have 9 occurrences Thanks |
|
Same issue here for me! |
|
Same issue: HA 2023.01.1 Logger: aiohttp.server Traceback (most recent call last): |
|
Same here: |
|
Similar here, message is different: Traceback (most recent call last): |
|
Same here: Traceback (most recent call last): |
|
|
Getting the same issues, and have isolated it down to my iOS home companion app remote accessing the HA instance, via external URL. Accessing the HA instance via internal URL has no issues. In my case, I am accessing it remotely via http (unsecured) via duckdns, and with my router port forwarding 8123 to the HA device. |
|
In my case, I am accessing it remotely via https (secured) via duckdns, and with my router port forwarding 8123 to the HA device |
|
To add on, I get the same error as long I’m using external URL functionality. Used an internal IP on the external URL section, via wifi. |
|
Double-check the URL you're using in your request. Make sure it's correctly formatted and that there are no extra characters or spaces. Ensure the URL scheme (http/https) is correct for the API you're using. I had a similar problem, I specified the port to a URL, but it was not necessary. |
|
I found out that such errors occur when the https://about.censys.io/ service sends requests like: |
But I don't have censys service !!! |
|
Same here, using |
|
Same Problem here |
|
I did a fresh install of HAOS 10.3 with 2023.6 and then immediately installed the Let's Encrypt add-on and issued a wildcard SSL cert. When I restart HA and attempt to access HA via HTTPS it fails, and I see the error in this thread in the log. |
|
guys, have a same problem
the ip 172.28.0.1 is my docker network. I just added this net to trusted proxy and it all work fine now. My nginx.conf with reverse proxy on itserver { server { |
|
This may be related to this issue: aio-libs/aiohttp#7208 Basically, if the request does not set content-length, aiohttp server returns 400 with |
If you have a Home Assistant instance that doesn't integrate the SSL certificate in the main configuration and you (or an integration, plugin, etc.) are trying to access the encrypted version of the API / dashboard, this error is going to appear. Check the http configuration. I use Home Assistant like this without trouble, over TLS / SSL. |
A couple of questions The DDNS_URL is my DuckDNS domain, right? and Why am I allowing google? EDIT This did not solve the error for me... Still getting the error |
I got this exact same log in my home assistant aswell. My home assistant frontend crashes very often now. Anyone know what this is? Is there a miner on my device or are there just someone trying to make sim random api call to my server where this line is included? |
|
I had this issue. It happened because HA was working in HTTP mode and the proxy tried to access it in HTTPS mode. A proper HA configuration to work in HTTPS mode solved this issue. |
|
Any link/tip on how you converted HA into HTTPS mode? |
|
Exactly. If some person, device, service or scanner accidentally or intentionally tries to access your HA with a different HTTP(S) protocol than expected, you will get this kind of error in log anyway. |
I use DuckDNS to get a certficate and external domain. But no proxy. I tried your config change and it made no change to my errors. |
|
Don't know much about DuckDNS integration, but it might act like a reverse proxy. Try with other DNS provider with standalone tools for updating the IP, like NO-IP and get a certificate with certbot. |
|
@ur7x you can stay on DuckDDNS and just test your HA with wget or curl using different HTTP(S) method to trigger this error and confirm that it happens because of this... |
and how to do this? you can help? thanks |
Thanks I tried that... Then it tried with the same address, just http this time. Then I tried http with my duckdns domain name... Then I tried https with my duckdns domain name.. all surprising results. Even more surprising NONE of the four wget commands triggered the aiohttp error. |
|
Certificate error is correct as the certificate is issued by domain name, so you can't use it for LAN connection without ignoring some security policies. |
Understood. But that test also produced ZERO aiohttp errors... so something else is causing them . |
|
You can ignore SSL errors with wget https://redfern.me/skipping-certificate-checks-with-wget/ |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
The topic is still present. In my case I have meanwhile the feeling that it comes from IOS mobile app. I get this type of message 1-2 times a day. |
|
me too |
|
There should be an option to disable SSL verification when establishing connections to the server. I am using it through Wireguard, which ensures that all my data remains encrypted, even when transmitted over HTTP. It would be beneficial to include an advanced configuration setting that allows experienced users to override security settings. Since I operate a k8s cluster where certificates are generated automatically, it's impractical to update the container configuration files with a new certificate each time one is generated. |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
Topic shall not be closed as it is still present. |
|
not stale |
and others
The problem
After upgrade to newest 2022.6.7 i see this error at logs
What version of Home Assistant Core has the issue?
2022.6.7
What was the last working version of Home Assistant Core?
i dont remember
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: aiohttp.server Source: /usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py:405 First occurred: 03:36:42 (3 occurrences) Last logged: 08:20:30 Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 334, in data_received messages, upgraded, tail = self._request_parser.feed_data(data) File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"Additional information
No response
The text was updated successfully, but these errors were encountered: