Moving to 2.1.0.116 now, which has no documented ngclient changes from 2.1.0.115.
Backblaze B2 ngclient import from ngax export at least fixed the Path percent-encode
discovered as broken, with April 4 test case here. Extra leading / problem still remains:
Attempting to import my actual Backblaze B2 ngax config export shows a similar result:
I think it failed to import the credentials. They’re not seen, and Test destination says:
Test connection failed
error-id:B2MissingUserID, user-information:No B2 Cloud Storage Account ID given
FTP has path trouble all in ngclient. I set Path ftp 1, and Test destination claims:
Create folder
The remote destination folder does not exist, do you want to create it?
even though the folder exists. The suspicious part is Filezilla Server shows it saying
MLSD /:/ftp 1 and such, whereas ngax would not have the extra /: on the front.
Regardless, if I say Create folder, it does:
<Date/Time> Info [Type] Message
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Command] MKD /:
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Response] 550 Invalid file name or path
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Command] MKD /:/ftp 1
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Response] 550 Invalid file name or path
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Command] QUIT
<4/17/2025 9:48:07 PM> FTP Session 44 ::1 duplicati [Response] 221 Goodbye.
Folder created
The remote destination folder was created successfully.
OK
and when I click OK, it complains again, so basically loops.
Trying OneDrive all in ngclient, I make a job to Path ngclient that it made, and run it.
Export to file, Import, and Destination has a trailing extra slash in Path, and no AuthId:
(P.S. I later found that at least trailing slash part appeared without import, just do Edit)
I can’t Submit it, and the HTTP error is {"Error":"Missing passphrase","Code":400}, although looking at the HTTP more, this is actually a bug where it decided to enable AES encryption (which I never configured), and is upset at the blank password it’s sending in.
I figured that out after typing the Authorization code again, and Submit still refusing to go.
I can get the same sort of error without the export + import, trying to resubmit original job:
[
{
"Name": "encryption-module",
"Value": "aes"
},
{
"Name": "passphrase",
"Value": ""
},
{
"Name": "dblock-size",
"Value": "50MB"
},
{
"Name": "encryption-module",
"Value": "aes"
},
{
"Name": "compression-module",
"Value": "zip"
}
]
There’s no place visible on General screen 1 to fix encryption, so I guess this is the end.
Import backup has wrong encoding #151 was on the percent encode plus slash Path.
Improvement suggestions #129 has a section on encryption in General. Claimed fixed.
Both areas are still having trouble. Who’s going to test all of the uncommon destinations?