@ben.turner I am also getting this error. I connected to Google Drive and get the same error message when attempting to back up. I lost my first draft of the website. 
Obviously, I’m very keen to avoid this happening again and need to get the backup working!!
I’m not sure how to post the library log as I get an error message stating that new users cannot post more than 10 links in a log!
You should be able to navigate to the “Support” tab in Local and click the “Download Local Log” button. This will give you a zip file that you can upload here for us to take a look at!
Thanks for that Local log @Chris9 !
When I look at the errors within the local-lightning.log file, I’m seeing errors that look like this:
{"thread":"main","class":"BackupAddonBackupService","level":"error","stack":"Error: Error: Command failed: \"%%userDataPath%%\\addons\\@getflywheel-local-addon-backups\\vendor\\win32\\restic.exe\" --repo rclone::drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35 -o rclone.program=\"../../AppData/Roaming/Local/addons/@getflywheel-local-addon-backups/vendor/win32/rclone.exe\" init --json\nrclone: 2021/12/13 22:42:18 NOTICE: Config file \"C:\\\\Users\\\\Warren\\\\.config\\\\rclone\\\\rclone.conf\" not found - using defaults\nrclone: 2021/12/13 22:42:18 Failed to create file system for \":drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35\": couldn't find root directory ID: googleapi: Error 403: Insufficient Permission: Request had insufficient authentication scopes., insufficientPermissions\nFatal: create repository at rclone::drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35 failed: error talking HTTP to rclone: Get \"http://localhost/file-5577006791947779410\": unexpected EOF\n\n\n at Object.<anonymous> (%%userDataPath%%\\addons\\@getflywheel-local-addon-backups\\lib\\main.js:720:19)\n at Generator.throw (<anonymous>)\n at rejected (%%userDataPath%%\\addons\\@getflywheel-local-addon-backups\\lib\\main.js:536:65)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (internal/process/task_queues.js:93:5)","message":"Error: Command failed: \"%%userDataPath%%\\addons\\@getflywheel-local-addon-backups\\vendor\\win32\\restic.exe\" --repo rclone::drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35 -o rclone.program=\"../../AppData/Roaming/Local/addons/@getflywheel-local-addon-backups/vendor/win32/rclone.exe\" init --json\nrclone: 2021/12/13 22:42:18 NOTICE: Config file \"C:\\\\Users\\\\Warren\\\\.config\\\\rclone\\\\rclone.conf\" not found - using defaults\nrclone: 2021/12/13 22:42:18 Failed to create file system for \":drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35\": couldn't find root directory ID: googleapi: Error 403: Insufficient Permission: Request had insufficient authentication scopes., insufficientPermissions\nFatal: create repository at rclone::drive:LocalBackups/46b12782-af3f-4a98-b4e9-60b45e112c35 failed: error talking HTTP to rclone: Get \"http://localhost/file-5577006791947779410\": unexpected EOF\n\n","timestamp":"2021-12-13T14:42:18.769Z"}
The main part that’s important to note is the part coming from Google Drive:
couldn't find root directory ID: googleapi: Error 403: Insufficient Permission: Request had insufficient authentication scopes., insufficientPermissions
It looks like for some reason, GoogleDrive can’t find the root directory ID.
When you look within your Google Drive account, do you have a LocalBackups folder? Does it also have a unique hash for the folder that contains the backups?
Hi Ben,
I now cannot even backup at all (Screenshot attached). Google Drive connected fine before and I saw the file being backed up… it just failed on the last step of actually sending it through to Google Drive.
I cannot change the backup folder and I have no folder called LocalBackups,
I did manage to export a copy though, so that’s a positive step.
Kind regards,
Christin
Since the previous error seemed to be related to permissions, is there anything out of the ordinary about how you connect to the internet?
For example, is this a work Wifi network? Or maybe a VPN is being used? I wonder if there’s something stripping out the authorization token used to communicate with Google’s API?
