New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aiohttp.server] aiohttp.http_exceptions.BadStatusLine: invalid HTTP method #13172
Comments
Same to me... without update 0.64.3 |
Same with me Hassbian: 0.65.4 |
I hope, someone can help us |
Update lastest python to fix. This guild is python version 3.6.0 Change with this link |
Thanks |
It did not worked. still issue on python version 3.6.4 and HA version 0.65.5
|
I have the same problem...
|
Same issues here HASS 0.66.1 to be honest I have seen it for a while now. Previous research had pushed me towards an Nginx/hass issue and I ended up specifying my URL in the hass configuration but that has not made a difference. Is anyone else also using Nginx? |
I aslo run NGINX, I see this issue with my docker install but not on my VM. |
Same issue here with HASS0.72.1 with addons DUCKDNS, DNSMASQ, MQTT, SSH and NGINX. |
i was fixed this error with upgrade pip3 to newest version, then update HA to newest version. All work ok without error on log. |
@keitetran What commands did you use to update pip3? I want to try that as well. |
I see pip. Other component on HA need other heigher version, but pip3 version is low. That was not upgraded => some component not working fine. Note. Upgrade pip3 with hass user. Not user pi. Im used hassbian. |
Same issue here: Home Assistant 0.73.1
|
Same issue and error log as @Imperial-Guard; System: HassOS 1.7 |
Any update here? I know I am still seeing the issue even on the latest. |
Did some more digging and found this to be true. I still had other services (blue iris) pointed directly at the HASS IP address trying to use https. |
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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
Hi! I still have this issue: I only use http, no https.
|
Hello, I also still see the issue : System: Raspbian Full traceback: |
FWIW. I was having this issue getting while I'm still getting everything set up. I was using someone else's docker-compose.yml and just noticed the health check for home assistant hits an https URL. Changing that to HTTP (for now until I get https set up) fixed the issue. |
This comment has been minimized.
This comment has been minimized.
hi all - i fixed this by adding the full address of the site into the
|
Not using SSL and have full url in config but no longer seeing this issue in current ver 85.0b0 |
@Bodge-IT What makes you think that error has anything to do with the one this issue is about? |
I've already mentioned, this error is fixed for me, so I fail to see how your question furthers anything.
Sent from BlueMail
…-------- Original Message --------
From: Dustin Wyatt <notifications@github.com>
Sent: Tue Jan 22 19:54:53 GMT+00:00 2019
To: home-assistant/home-assistant <home-assistant@noreply.github.com>
Cc: Gary Barclay <badimba@gmail.com>, Mention <mention@noreply.github.com>
Subject: Re: [home-assistant/home-assistant] [aiohttp.server] Error handling request (#13172)
@Bodge-IT What makes you think that error has anything to do with the one this issue is about?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#13172 (comment)
|
@Bodge-IT Because this is not a technical support forum. While it's nice that you no longer have the problem, it is not really relevant here. This is an issue tracker for the developers. If you have other information that indicates that the error you posted is related to the error this issue is about, then it would be helpful to include that information so we can track down the source of this potential bug. |
I wasn't asking for technical support. The reason why I thought it was related was because it had the same error message. |
@Bodge-IT You have a recorder error. |
If I turn on debug logging for everything I do not get any more information from
@keitetran I recommend changing the title of this issue to something like "aiohttp.http_exceptions.BadStatusLine: invalid HTTP method" as that is the relevant line from the error. |
hitting this error when trying to access https://ip.address:8123 |
This comment has been minimized.
This comment has been minimized.
Still an issue |
Just upgraded to 0.95 and I'm now seeing this error, but did not see (or notice it) previously. Currently shows this error hitting 85 times since my upgrade.
|
This usually means that if you’re using SSL, someone is connecting to Home Assistant using |
If you're experiencing this issue after enabling SSL/TLS in your configuration.yaml file, and these errors are being generated when you attempt to visit your HA via HTTPS://URL:8123. I would look at your configuration.yaml and make sure spacing is correct. 3 ticks after http for the SSL data. [space] = Space Bar http: |
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. |
Home Assistant release (
hass --version
):0.64.1 => 0.65.4
Python release (
python3 --version
):3.5.x
Component/platform:
aiohttp.server
Description of problem:
[aiohttp.server] Error handling request
Expected:
NO
Traceback (if applicable):
The text was updated successfully, but these errors were encountered: