Afternoon friends, I’ve finally got all my backups and checks scheduled properly, and it worked properly for the first 48 hours or so (initial backup + scheduled backup the following night), and all checks also completed without errors/all chunks found.
But with last night’s schedule, everything failed with this message:
Running backup command from X:/TEMP/Duplicacy Cache/localhost/1 to back up X:/Yyy
Options: [-log backup -storage [name] -threads 10 -stats]
2023-02-18 02:00:01.489 INFO REPOSITORY_SET Repository set to [x]
2023-02-18 02:00:01.490 INFO STORAGE_SET Storage set to [y]
2023-02-18 02:00:02.381 INFO BACKBLAZE_URL download URL is: [URL]
2023-02-18 02:08:43.735 ERROR STORAGE_CONFIG Failed to download the configuration file from the storage: Head "B2 URL": tls: first record does not look like a TLS handshake
Failed to download the configuration file from the storage: Head "B2 Bucket URL": tls: first record does not look like a TLS handshake
I am unable to execute any of the 15 odd backups now, either with schedule or manually; all logs return the same error. I am also obviously unable to perform any restore operations as well.
All the schedules were set up with the Web-UI.
My master PW is not stored in a keyring.
No files/credentials/keys were moved from any folders.
Each of the three storages involved utilize the B2 master ID/key, and are all encrypted with the same PW (non-RSA, just standard pw upon initialization of storage).
Duplicacy Web and main app were closed, reopened, master pw re-entered, and all operations/connections still fail.
Rebooting the machine doesn’t help.
What is going on here? Why would everything work well for 2 days but suddenly stop working in this fashion?
All help is appreciated!
Thanks,
John
P.S. Forgot to mention – It is possible I was connected to a VPN when I performed the initial backups of these files. Would this cause any potential issues? If so what would be the solution?