Restore failing on 3 seperate servers on B2

All three decrypt here (and to the same content all ways according to md5 sums) whether I use AES Crypt or SharpAESCrypt.exe on Windows 10, or SharpAESCrypt.exe on Linux Mint 18.1.Surprisingly I don’t need to even say mono before the .exe path. It’s possible to configure that, but I didn’t know mine’s set by default.

$ mono --version
Mono JIT compiler version 5.18.1.0 (tarball Fri Mar 15 20:45:47 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	Interpreter:   yes
	LLVM:          yes(600)
	Suspend:       preemptive
	GC:            sgen (concurrent by default)
$ 

and this worries me a bit because 5.18 has a bug. Duplicati does not start up #3572. Ugh, mine’s broken. Possibly picked up the too-new mono inadvertently when I recently had Update Manager update software.

$ /usr/lib/duplicati/SharpAESCrypt.exe d Duplicati duplicati-20190410T145933Z.dlist.zip.aes duplicati-20190410T145933Z.dlist.sharp.zip
$ /usr/lib/duplicati/SharpAESCrypt.exe d Duplicati duplicati-bb6c7345f5ef44a2495c646ccc897a34f.dblock.zip.aes duplicati-bb6c7345f5ef44a2495c646ccc897a34f.dblock.sharp.zip
$ /usr/lib/duplicati/SharpAESCrypt.exe d Duplicati duplicati-i2784feb77d794b89b82b5fedb57b03f1.dindex.zip.aes duplicati-i2784feb77d794b89b82b5fedb57b03f1.dindex.sharp.zip
$ file /usr/lib/duplicati/SharpAESCrypt.exe
/usr/lib/duplicati/SharpAESCrypt.exe: PE32 executable (console) Intel 80386 Mono/.Net assembly, for MS Windows
$ 

What I was hoping for was a failure that I could look at from just the non-decryptable files, but they decrypt. Trying direct restore on Windows with 2.0.4.5 beta gives me dates and contents, and the .jpg restores fine.

Don’t have 2.0.4.16 anywhere, but might have put it on Linux if mono hadn’t hit me. Need to try downgrade. Meanwhile, you have several versions, so might test if direct local file restore from those three destination files only fails on 2.0.4.16 for you (if that’s not the sort of restore you tried already). That’ll narrow it down…

Trying the export and run from command line would also be possible. Syntax needs adjusting from export format which is for backup into what restore expects. Possibly just adjust paths, and pick a –restore-path.