Closed cob94440 closed 1 year ago
Failed to to call /addons/6b64d821_tydom2mqtt/stats - 404 Client Error for http+docker://localhost/v1.41/containers/addon_6b64d821_tydom2mqtt/json: Not Found ("No such container: addon_6b64d821_tydom2mqtt") J'ai cette erreur dans le log ha pourtant le container est bien présent
Enfin des logs dans l'addon :
Traceback (most recent call last): File "/app/main.py", line 226, in <module> loop_task() File "/app/main.py", line 148, in loop_task loop.run_until_complete(listen_tydom_forever(tydom_client)) File "/usr/local/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete return future.result() File "/app/main.py", line 160, in listen_tydom_forever await tydom_client.connect() File "/app/tydomConnector.py", line 109, in connect conn.request( File "/usr/local/lib/python3.10/http/client.py", line 1282, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1328, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1277, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1037, in _send_output self.send(msg) File "/usr/local/lib/python3.10/http/client.py", line 975, in send self.connect() File "/usr/local/lib/python3.10/http/client.py", line 1454, in connect self.sock = self._context.wrap_socket(self.sock, File "/usr/local/lib/python3.10/ssl.py", line 513, in wrap_socket return self.sslsocket_class._create( File "/usr/local/lib/python3.10/ssl.py", line 1071, in _create self.do_handshake() File "/usr/local/lib/python3.10/ssl.py", line 1342, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:997)
malgré suppression et réinstallation le problème persistait. J'ai du mettre l'adresse mediation au lieu de mon IP. Et c'est reparti
malgré suppression et réinstallation le problème persistait. J'ai du mettre l'adresse mediation au lieu de mon IP. Et c'est reparti
idem le module ne veut pas démarrer. Qu'appel tu adresse mediation?
C'est l'adresse qui est noté dans le champ adresse du tydom
Le mer. 30 nov. 2022, 22:23, everlink033 @.***> a écrit :
malgré suppression et réinstallation le problème persistait. J'ai du mettre l'adresse mediation au lieu de mon IP. Et c'est reparti
idem le module ne veut pas démarrer. Qu'appel tu adresse mediation?
— Reply to this email directly, view it on GitHub https://github.com/fmartinou/tydom2mqtt/issues/62#issuecomment-1332750611, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4YD27CGRPKU5WZTBTQXYTWK7ATTANCNFSM6AAAAAASQARKYE . You are receiving this because you authored the thread.Message ID: @.***>
I can reproduce your issue but I don't know yet what causes the regression.
The commits between the 2.6.4
and the 2.6.5
are unlikely the cause of the regression on SSL 🤔
The python image used to run the code has been updated 21 hours ago.
It may have an impact
The python image has probably be updated 21 hours ago from alpine 3.16 to alpine 3.17
I'll try to downgrade it to see if it fixes the issue.
Downgrading to alpine 3.16
fixes the issue: see https://github.com/fmartinou/tydom2mqtt/commit/df1839e627b1758c7b9624f775bc339e6d1f36c5
I presume that some old unsecured SSL ciphers have been removed/disabled from the new Alpine version whereas Tydom is still using it for local communication.
Fixed version 2.6.6
is available.
Let me know if you still encounter issues. ++
C'est ok pour moi mêm eavec l'ip du tydom
L'addon ne démarre plus. le journal ne s'affiche pas. Comment revenir a la version précédente?