18-06-05 21:12:10 ERROR (SyncWorker_15) [hassio.docker] Can’t create container from addon_a0d7b954_appdaemon3: 409 Client Error: Conflict (“Conflict. The container name “/addon_a0d7b954_appdaemon3” is already in use by container “9f4f226c54c73f503dbb3b8c1a34847f28fa595fdc992bbbc2e0170d49c9a842”. You have to remove (or rename) that container to be able to reuse that name.”)
I can’t figure out how to fix it. Have tried uninstall and reinstall but get the same message.
I run hass.io 0.70.1
And supervisor 105
This is an Hassio issue, not an add-on issue, maybe try the Discord chat, there are probably people around that can help you fix that. (I’ve seen it in the chat before).
i have been searching and found nothing on this. Also tried several backup restores with wipe, but still it wont start. cant seem to figure this one out…
Since this morning it stopped working, not sure what it is. Not sure when stopped working, was working fine few days ago (not sure if only before updating to 1.2 or not)
I do have HASSIO 0.71, on a UBUNTU-NUC, in my HASSIO ADDON 1.2.0, when I click START it does not start, and nothing in the log (“Error grabbing logs: EOF”).
I also deleted my backup folder (contained many big files), thinking was a space problem, but no
I’m running Hass.io on top of resinOS and everything was working great. Last night I tried upgrading Hass from 0.73.2 to 0.75.2 and AppDaemon stopped working. So I downgraded to 0.73.2 and kept getting the same errors. I even restored a snapshot of a working system and it’s still broken.
Here is the Supervisor log:
18-08-09 14:50:51 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<WebSocketWriter.ping() done, defined at /usr/local/lib/python3.7/site-packages/aiohttp/http_websocket.py:617> exception=RuntimeError('unable to perform operation on <TCPTransport closed=True reading=False 0x7197a030>; the handler is closed')>
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/http_websocket.py", line 621, in ping
return await self._send_frame(message, WSMsgType.PING)
File "/usr/local/lib/python3.7/site-packages/aiohttp/http_websocket.py", line 603, in _send_frame
self.transport.write(header + message)
File "uvloop/handles/stream.pyx", line 671, in uvloop.loop.UVStream.write
File "uvloop/handles/handle.pyx", line 159, in uvloop.loop.UVHandle._ensure_alive
RuntimeError: unable to perform operation on <TCPTransport closed=True reading=False 0x7197a030>; the handler is closed
18-08-09 14:50:51 INFO (MainThread) [hassio.api.proxy] Home-Assistant Websocket API request initialze
18-08-09 14:50:51 INFO (MainThread) [hassio.api.proxy] Websocket access from a0d7b954_appdaemon3
18-08-09 14:50:52 ERROR (MainThread) [hassio.homeassistant] Can't update HomeAssistant access token!
18-08-09 14:50:52 ERROR (MainThread) [hassio.api.proxy] Failed authentication to HomeAssistant websocket
did you change to the new user password authentication?
that isnt supported by AD yet.
but if i am correct you can change back to the old authentication way
Further checking shows that connections from my proxy machine into the Hass machine are being rejected by the Hass machine, so none of the reverse proxy authentication is working. I’m trying to figure out if resinOS (or Hass.io) has some kind of automatic IP blocking that would lock out my proxy machine. This is so strange. I’m about to nuke and pave, but I already did that about three weeks ago in response to problems I had with HassOS and Hass 0.74, so I’m not anxious to waste more time.
sorry i cant help you with that part.
i just wanted to make sure that you knew that the new authentication isnt supported by AD.(yet)
i never have worked with hassio, so i am not familiar with the problems that come with that.
i hope you find out what the problem is.
Release v1.2.0