The supplied option --auth-username is not supported and will be ignored

[Warning-Duplicati.Library.Main.Controller-UnsupportedOption]: The supplied option --auth-username is not supported and will be ignored

Backing up to Google Cloud Storage, I’m getting this warning. Have looked at the similar topics but haven’t been able to draw a conclusion as to whether it is something to be concerned about. It constantly turns the Duplicati icon yellow.


yes these options are not supported for your storage (if you use the proprietary API for Google storage that is). I don’t know how it’s possible that you have these options in your configuration, it should not happen. Maybe you upgraded from an older Duplicati version ? Whatever the reason, you should be able to edit your job and remove these options from the advanced options.

Fairly new to Duplicati (approx 1 month now). Nothing appearing in advanced options, however perhaps I should add something via advanced text to make it not use auth?

Hmm, there is however something prefilled here in passphrase (edited for screen shot). Is that what it’s talking about?

No, passphrase has nothing to do with auth options; passphrase is used to encrypt data before sending it to the backend, it’s at the sending phase that auth is used.
I don’t see how passphrases could not match, I don’t think that you can validate the job creation if they don’t.
To come back to the advanced options, try to export the job to file and open the resulting file with a text editor to see if you can find the offending options.

Another way to handle this is on Destination screen, use three-dot menu to far right of title.
Copy Destination URL to Clipboard and Import Destination URL can both edit URL.

The typical path is to change from a Storage Type that used a username to one that does not.
Seeing it might help recall. I think going back to prior type momentarily is also a delete chance.
The UI will probably keep your Google settings on return. If anything gets hurt, just don’t Save.

Changing backend type leaves invalid backend options #3082 is the general issue, but the key
word there is invalid. Sometimes there are other options that are still valid. Want those kept?
Regardless, suggest you see if you recall what you did, and take a look at the actual extra one.