Hi @nix, welcome to the forum! (And sorry for taking so long to get back to you.)
This sounds like more of a parameter formatting issue than a problem with SIA. Can you use the Duplicati job menu to “Export as Command-line” and paste it here (with any person stuff like passwords and email addresses removed) so we can check for possible formatting problems?
In the Duplicati config for the Sia backup job, instead of filling in “127.0.0.1:9980”, try just “localhost” (with no port specified). This is what I had to do to get mine working. My exported config therefore ends up looking similar to yours with a subtle difference:
Also I think you should make your dblock size something smaller than 2GB for Sia. In early tests I did on Sia backups I found that sia transfers could fail fairly often and cause duplicati to hang and become confused; my more recent tests went a lot better and I had no issues with 500MB dblocks, but even those are probably on the high end of what I’d advise (to be safe I’d honestly recommend around 100 - 200 MB).
Thanks! I’ll look into the size issue when I get there.
Both give the same error: “Input string was not in a correct format.”
My (working) Sia backup job, when exported to command line, populates with 2 forward slashes like this as well, so i’m guessing it’s not an accident (the GUI configuration doesn’t even let you touch these of course).
Weirdly, even if I type something wrong in “Server”, I can’t reproduce the error message you’re getting. Can you also try creating a brand new backup job (just as a test), set all the same options, and try it again?