Unicode is not supported #96
however this sounds like it was fixed in library 1.6.3. If you have Duplicati 126.96.36.199, I think you already have it, however if you’re on the previous beta 188.8.131.52 you don’t. And it might not be this same problem in any case.
Supplies the password used to connect to the server.
The password used to connect to the server. This may also be supplied as the environment variable AUTH_PASSWORD.
Supplies the username used to connect to the server.
The username used to connect to the server. This may also be supplied as the environment variable AUTH_USERNAME.
I don’t have or know Mega, but it looks like it uses username and password (not OAUTH), but maybe those are the same as what you would get by supplying the Username and Password fields in the GUI. You could test, for example using the GUI Commandline option for your job to see if your Target URL contains those.
There has been some question for OneDrive about whether authentication information should be attached onto the URL or supplied separately or both, and how they interact. Possibly Mega can have similar issues.
As for the 2FA question, Duplicati is subject to what the library can do, and I see you’ve already asked them. but the answer sounded to me like it’s not there yet. I doubt they can answer the question about Duplicati… MegaApiClient’s documentation, and maybe you can spot another interpretation for those settings. I did not.