The same thing has happened to me. My HA died and am currently trying to restore but I get the same error.
One work-around is to just download the backup file from Google Drive, copy it to the HA backups folder via Samba and restore the snapshot from the local file
I am trying to install this addon but I have 401 Not authorized.
Tried to reinstall addon and reboot.
Any help please.
For everyone seeing the “401 Not Authorized” error when you try to connect the addon to Google Drive:
If copy the URL in that window to a new tab and open it again, it should work.
Whats happening (warning: technical)?
It looks like the browser cookie that authenticates your browser with Home Assistant isn’t getting included when it redirects from Google Drive -> habackup.io -> Your local addon. This explanation has background explaining why the addon has to do this if you’re curious. Opening the URL in a new tab seems to make it send the expected authentication cookies.
I haven’t released a new version, this isn’t related to a supervisor upgrade, and its happening on every browser I try. I’m unsure why this just suddenly stopped working.
4 Likes
I’ve been testing around with different browser configurations, and I’m pretty sure this “401: Permission Denied” issue only affects users of Firefox who have it set to automatically delete cookies when the browser closes.
I don’t know why this would cause problems, but turning it on is the only thing I’ve found that reliably reproduces the problem. The error message is actually the Home Assistant Supervisor claiming that your browser isn’t presenting the cookie that verifies you’re logged in to Home Assistant.
I’ve created a github issue to track the problem. If you’re seeing the problem outside of using firefox with that option enabled, please post there to let me know to widen my search.
Thanks for the work around. Which URL do we copy to a new tab?
And I am using Microsoft Edge as my browser.
Copy the URL on the page that shows the “401” error.
Make sure you copy the whole thing (its long) and then open it in a new tab. If that doesn’t work, try authenticating the addon in Chrome or Chromium instead.
The url will be different for each of you.
1 Like
I’m hearing from a bunch of people that its failing sometimes with Chrome, Edge, etc. I really have no idea why this just suddenly started happening.
1 Like
I can’t choose (change) the folder in Google Drive where the backups should be located, when trying to, I end up here and when pushing the button nothing happens:
Give it another try, it should be in good shape now.
Thanks that worked in MS Edge .
PI-Hole users: Don’t use PI-Hole as your DNS server otherwise you’ll get the 401 in any browser.
I tried everything and eventually i removed the IP adres of the Pi-hole and then it authenticated right away
Hey
Dont know if you have same problem as me but my sensor.snapshot_state wont show up after restart.
Is this a known problem or something new.
I have removed the setting for it and saved. And re-entered the setting for it again and saved. but no sensor shows up.
Solution?
I see know that the sensor shows up after a significant time approx 1 hour. Why is this?
Home Assistant deletes the sensor when it restarts, and it won’t show up again until the addon syncs (which only happens once an hour unless a snapshot gets taken). The addon doesn’t get told when Home Assistant restarts, and unfortunately any strategy I can take to check it periodically would seriously spam the supervisor log (I get a lot of bugs like this one).
I’ve released a new version of the addon 0.101.3. This has a bunch of small fixes and features, but mainly:
- You can now choose to stop some addons while a snapshot is being taken since some addons don’t snapshot properly if they’re running, in particular MariaDB.
- I’ve provided a workaround for the “401: Unauthorized” that some are running into. when authorizing the addon With Google Drive you’re provided with an authorization string that you can copy back into the addon.
2 Likes
Okey. I can live with that. 
BTW great Addon!
Does the stop add-on feature work together with the new watchdog mechanism that restarts an add-on when it stops?
1 Like
have the same question…
Looks like the supervisor will attempt to restart the addon after it get stopped, defeating the feature. I’ll add a warning in the setting dialog in the next version if you try to configure a watchdog addon enabled addon to stop during snapshots.