core: Challenge/Response error with SniTun server
The problem
After updating to 0.116.0, I have the below SniTun errors in the long. These have potentially been there prior to 0.116.0, I didn’t really take note. I do use NabuCasa if that’s of any relevance.
Environment
- Home Assistant Core release with the issue: 0.116.0
- Last working Home Assistant Core release (if known):
- Operating environment (OS/Container/Supervised/Core): hassio
- Integration causing this issue: cloud
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/cloud/
Problem-relevant configuration.yaml
default_config:
Traceback/Error logs
2020-10-07 19:25:58 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server
2020-10-07 19:25:58 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 215
- Comments: 128 (16 by maintainers)
We are aware of this issue. Please refrain from posting “same” or similar to avoid sending notifications to everyone in this issue. Just add a 👍 as a reaction to the first post.
Home Assistant automatically recovers when it has such errors. We’re working on a patch to make them go away completely.
For the love of God, please read the last message from @balloob and stop saying me too. Thanks you!
A few weeks back the NubaCasa servers were updated/upgraded. Since then I’ve noticed the following two errors in the HA Logs following every server restart.
and
These errors only appear once, immediately following a server restart. HA is running on an HA Blue.
Robert Blackwell
Nothing? Really? Seems like this needs more bumping. Same errors as everyone else of course.
I’m here for the same reason
Logger: hass_nabucasa.remote Source: /usr/local/lib/python3.8/site-packages/hass_nabucasa/remote.py:299 First occurred: 1:21:10 PM (1 occurrences) Last logged: 1:21:10 PM
Connection problem to snitun server
Developers are aware. Please refer to the following link.
https://github.com/home-assistant/core/issues/41420#issuecomment-932320010
When is the patch gonna be released? The problem still exists.
Yes, here too. Still exist. HA is updated to latest version(s) .
i have the same issue as well
Logger: snitun.client.client_peer Source: /usr/local/lib/python3.9/site-packages/snitun/client/client_peer.py:104 First occurred: 3:17:27 PM (1 occurrences) Last logged: 3:17:27 PM
Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
This is not completed as no progress has been done on it and the error persists in logs since 3 years ago.
Please reopen for another 3 years /s
This is their reply about this problem.
What PR fixed it?
Same issue
Hi, has there been any progress? I migrated from running in docker on raspberry pi 4 to a running in a docker on x64 ubuntu vm while updating to 2021.10.5 and I noticed I do not get this error anymore.
Is it because I no longer use the ARM image? Did you fix it? Any update? Thanks!
edit: nvm it came back after few reboots so it’s not tied to architecture
i also have errors below upon restart HA, it takes a while to connect, normally if i restart HA, i can almost connect instantly to HA with nabucasa url, now it takes a while… i see this for 2 days now
is this related to this issue?
most of the time, i only see the timeout issue, sometimes all 3 below
Same for me. Running OS on Proxmox. Issue doesn’t appear to have any detrimental impacts, remote is working without issue - it is just the error messages on restart.
There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
“Connection problem to snitun server” still for me:
Home Assistant 2022.10.1 Supervisor 2022.09.1 Operating System 9.0 Frontend 20221006.0 - latest
Same here, found them in the logs - which I like to have clean as well - and no issues with Nabu Casa connection. WOuld be nice to have them disappear. Only logged after restart.
Logger: snitun.client.client_peer Source: /usr/local/lib/python3.9/site-packages/snitun/client/client_peer.py:104 First occurred: 11:11:09 (4 occurrences) Last logged: 11:11:48
Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
and
Logger: hass_nabucasa.remote Source: /usr/local/lib/python3.9/site-packages/hass_nabucasa/remote.py:333 First occurred: 11:11:09 (4 occurrences) Last logged: 11:11:48
Connection problem to snitun server
I´m also having this problem. I don´t know with it´s related or not, but my connection betwenn HA and Alexa using Nabu casa just drops after few minutes. I can control the devices trough alexa but after few minutes, less than five, I just get the “device not responding” answer from alexa. Does anyone facing the same issue? Can someone please help me?!
That is the image i’m using
I originally posted it went away with a update on 17th Oct too, but then edited the post with how it came back later @ https://github.com/home-assistant/core/issues/41420#issuecomment-945067123
The Issue is fixed for me at least with homeassistant version 2021.11.5 . Nabu Casa integration works as expected and the error “Challenge/Response error with SniTun server” is gone.
Same issue
@cogneato I am using latest stable HA image running in a docker on RPI4. I have opened the ticket at nabu casa support, thanks for the suggestion!
The remote connection will not freeze your Home Assistant installation.
Is it an idea (and possible) to list all of the endpoints used by core HomeAssistant and NabuCasa so that people can add them to the relevant whitelists if they are using any DNS filtering / WAP’s etc? Or are they already listed somewhere?
That should make it more robust 👍 . We’re still looking into why for some people the connection stalls.
@mcburnside Network unreachable sounds like your local internet/ipv6 has issues. We have some troubleshooting tips here https://www.nabucasa.com/config/troubleshooting/
same issue as the others in this thread. Just want to mention that I have been a nabu casa subscriber for a year or two, and this is a very new issue for me. No changes in my HA setup, nor my network. I got an alert a few hours ago saying my Cloud instance was down suddenly, and checked my local logs to see
and
I had this happen one other time this week, and a simple restart fixed it.
Who also runs Pi Hole and or Unifi Intrusion Protection System?