Can't access with outside URL

HomeAssistant Core on Proxmox WM and it was all ok for a year. Now suddenly i get “Unable to connect to Home Assistant.”

I checked the logs and i have this;

2021-02-04 10:22:59 ERROR (MainThread) [aiohttp.server] Unhandled exception
Traceback (most recent call last):
File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1152, in _sendfile_fallback
read = await self.run_in_executor(None, file.readinto, view)
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 485, in start
resp, reset = await task
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 440, in _handle_request
reset = await self.finish_response(request, resp, start_time)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 591, in finish_response
await prepare_meth(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_fileresponse.py", line 241, in prepare
return await self._sendfile(request, fobj, offset, count)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_fileresponse.py", line 96, in _sendfile
await loop.sendfile(transport, fobj, offset, count)
File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1131, in sendfile
return await self._sendfile_fallback(transport, file,
File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1161, in _sendfile_fallback
await proto.restore()
File "/usr/local/lib/python3.8/asyncio/base_events.py", line 263, in restore
self._transport.resume_reading()
File "/usr/local/lib/python3.8/asyncio/sslproto.py", line 344, in resume_reading
self._ssl_protocol._transport.resume_reading()
AttributeError: 'NoneType' object has no attribute 'resume_reading'

Any ideas?

I am running into the same issue. Any help would be appreciated.

I’m presuming you have any casa ?
I had similar a few weeks back where the remote access toggle kept turning itself off and whilst I was out I had to log in to nabu casa to reconnect but it still kept doing it.
What I think worked is actually getting my son who was home at the time to open HA and turn the toggle on from there and it’s been ok since.

No i don’t have casa but thinking about it.

So how are you trying to connect ? Just with your IP have your opened ports.

Using duckdns dynamic dns service and it was working nicely until i upgrade my core to the latest version. :confused:

Ok found the problem. It was the ssl certificates expired and let’s encrypt didn’t refreshed them automatically. :man_mechanic: :love_you_gesture:

2 Likes

How did you fix it?

I’m having this same error now. Everything working well with DuckDNS for months until upgrading. It also appeared that my SSL certificates were not refreshed automatically. Then I uninstalled DuckDNS, deleted the certificates and reinstalled, and got new certificates. All good, and I was then able to access it via DuckDNS externally. But I can’t use the DuckDNS URL for internal access any more.

There’s a GitHub issue for this.

Having same issue. It’s NOT the ssl certificate.

1 Like