-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing consistently since 1.5.0 with Request (ADD_SYNC) finished with error: Invalid argument #623
Comments
any way I can help debug this? |
Hi @haelix888 , Btw, that snipped of log shows that you are using a proxy. The returned response is well formed, so that is not likely to be the case. But just in case, you might want to try again without it if feasible. |
Pasting a larger extract of the log. No proxy this time. I'm using 2-factor auth. All start from clean (empty cache and configuration folder). The exact same thing works with megacmd 1.4.x.
Then:
I believe everything looks good until the ADD_SYNC request. |
@polmr thanks and lemme know how to help. |
Hi @haelix888 , thanks for posting that out.
Please, let us know any particularities on your operating system, so that we can try to find a general fix, just in case, other users are affected |
That was it, thanks. I was running megacmd inside a recent linux Docker container where A more correct way to generate that file is:
After which the file contents is something like
A normal Linux machine (at least those with a desktop environment) will have that file, so I'm not sure if you need to do anything. Much appreciate the hint. |
Thanks for reporting back @haelix888 ! |
I'm using MEGAcmd in termux and I don't have permission to write |
The text was updated successfully, but these errors were encountered: