core: error with SniTun server (0 bytes read on a total of 32 expected bytes) when starting Home Assistant

The problem

Since Home Assistant 2021.12, when I start I have the following error: ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)

What version of Home Assistant Core has the issue?

2021.12

What was the last working version of Home Assistant Core?

2021.11.5

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Cloud

Link to integration documentation on our website

https://www.home-assistant.io/integrations/cloud

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-12-15 18:30:43 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
2021-12-15 18:30:43 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server

Additional information

I don’t know if it is related to #41420 as the message about 0 bytes read on a total of 32 expected bytes is not specified on this issue. I have no message before or after and in configuration Home Assistant cloud is connected. Google Assistant is also working.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 24 (8 by maintainers)

Most upvoted comments

On my side I have no Tuya integration set up at all. So Tuya should not be the cause, the Home Assistant Cloud by Nabucasa throws the specified error in the log.

Running the latest 2023.2.0 on a NUC running HAOS 9.5, no tuya, I am nubacasa connected. Occurs on Restart.

023-02-01 13:45:49.663 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
2023-02-01 13:45:49.668 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server

This issue seems related to:

#41420

#41420 Was closed and solution was to change HDD to SSD.

I have the same error and I’m using SSD.