I am trying to configure a Backup with Google Drive as the destination. The strange thing is that I have successfully (and without any issues) created similar backups on 3 other computers. The problem is that when I ‘test connection’ it always reports ‘Folder does not exist’. I have tried creating the folder on drive and removing the folder on drive. I have tried using just the destination folder (like I did with the other three computer backups) and prepending googledrive://. Nothing seems to change the behavior. The version of Duplicati on the system that is failing is 2.2.0.0_stable_2025-10-23 on debian. The other versions are 2.1.0.5_stable_2025-03-04 on Windows 11 and 2.2.0.0_stable_2025-10-23 on docker.
Just now, with Duplicati versions stated? Are AuthID the same?
Google Drive Destination talks about Access Levels. Google Drive is somewhat unique in its security which limits apps without special permission to only access data created by the app.
If done as you, it won’t help a “limited login” which is generally what they’re pushing apps to. Painful workaround does exist, but basically, expect a limited login to see its data, not yours.
Having said that, the old UI offers to make the folder. The new UI just complains. Likely a bug, however continuing on with backup job creation and run will make the folder then you can test.
Because this is kind of the wrong order, I’d prefer if the new UI worked like old. Did you try old?
There is an additional change in 2.2.0.0 which is that it has a better test (if you can get it to go). Previously, all that was done was a file listing, without regard to the list of files seen. Very basic.
Newer test does more, I think verifying reading and writing to the folder, thus it needs the folder.
The Drive access level (limited vs full) is tied to AuthID, so same value gets same access level. AuthID is getting better hidden, but the GUI Commandline should show it near end of the URL.
Or maybe after more info comes back, it will be something else. Developer may also have idea.
I ignored the Test Connection and created the job. Running it seems to be working (although I haven’t seen the files showing up on Google Drive yet). Seems broken that testing the connection now fails where in the past it not only did a valid test, but also offered to create the folder for me…
But sincerely, thanks for the reply and the suggestion to just proceed.