What does this error mean?

My log is absolutely loaded with "20-08-25 07:32:33 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session ". I’m sure it means something, but my searches have come up empty. Is this something I can fix?

1 Like

You probably used your browser to navigate to an addon webpage that the ingress session had expired for. e.g. closing your browser then opening it again and going to the browser history list and selecting the addon webpage would be one way of generating this warning.

It is not an error. It’s a warning. Nothing to fix.

3 Likes

Thanks for the speedy and most helpful reply. I have several Wink Relays displaying Home Panel. Closed the webpage and poof! Error gone.

I think something else is going on here. My supervisor log is being filled with these, regardless of whether a browser is connected or not:

20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:11 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:19 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:19 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:28 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:28 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:34 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
20-09-03 02:35:40 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session 057ad19beb8cd74180680fc7a37eccec2c7830922226b99697f444e03ad42404a82b9edb8036db31663e5cd0204aa3c68fe9f22088bad5ce2ff29e43b72853c7
2 Likes

Gee, whatever it is, it looks like the same single item all the time. Perhaps there is something you’ve got going that is using the HTTP protocol? Mine was related to Home Panel…it was trying to log in with expired creds. I have seen some instances (after hours of Googlin’) where Firefox was a problem. There was also a lot of “clear your cache” suggestions that seemed to work for lots of people.

Up your logging level to debug and it might reveal what is responsible.

1 Like

Thanks, but this is happening regardless of any browsers being connected.

Can you point me in the right direction on how to up the debug level on the supervisor? All I’m finding is how to enable ssh to get the same logs.

It’s not the supervisor. It’s the logger. Use the developer tools service menu to call this service:

https://www.home-assistant.io/integrations/logger/#services

1 Like

Thanks, this helped me track the problem to a system that I didn’t realize was still on.

2 Likes

Just in case anyone else runs into this issue, I had the same recurring error.

Turned out to be the Amazon Alexa integration requiring reauthorisation using 2FA.

Once I did that - no more error.

1 Like

Does anyone know the root cause of such error?

Logger: aiohttp.server
Source: components/hassio/ingress.py:86

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
    resp = await self._request_handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 56, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 129, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/hassio/ingress.py", line 54, in _handle
    return await self._handle_websocket(request, token, path)
  File "/usr/src/homeassistant/homeassistant/components/hassio/ingress.py", line 86, in _handle_websocket
    await ws_server.prepare(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 135, in prepare
    payload_writer = await super().prepare(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_response.py", line 378, in prepare
    return await self._start(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_response.py", line 386, in _start
    await self._write_headers()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_response.py", line 458, in _write_headers
    await writer.write_headers(status_line, self._headers)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/http_writer.py", line 119, in write_headers
    self._write(buf)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/http_writer.py", line 67, in _write
    raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport

2 Likes

Got the same error, could you get rid of it in the meantime?

1 Like

No, did not found the root cause. I think its caused by ingress - Introducing Hass.io Ingress - Home Assistant

There is list of plugins that use this authentication. Theck if you have this plugins and try to uninstall or update them. Also try to remember if any of the plugins was recently updated.

For myself I decided 1) do not even click on any plugins page on prod environment; 2) all experiments started after backup or on test environment.

HA development is very active and its really great, but from time to time integration conflicts happen. I’ve setup nightly backups of the instance and keep last 7 days backups ready to roll back. I think this is the only way to survive here - if something wrong then rollback immediately. . :))))

2 Likes

I am getting this error and it runs constantly every second, forever.

21-10-07 07:43:42 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:43 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:45 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:46 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:47 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:48 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:49 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca
21-10-07 07:43:51 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session c971f6cb69041720ebdad2d489a2f85f27f17f8ab3039960015621a3b7477fa1744adc262fcdc5cf59c087d30b184e5a830993828b84a37686f03894a0cb54ca

I already set

logger:
  default: debug

but I see no additional information.

I rebooted, tried to disable each pluggin one by one and nothing,

What else ca I do?

Same here, I put in debug and not a single bit of extra data helps point me the way to resolving the core problem.

I was told that:

Which I found was true. I had several Wink Relays running a HA dashboard [Home Panel] via a link in the Relay’s browser. When I dumped the Relays [and the dashboard,] the problem went away.