Still working?

[ranehal]

?

[ComputerSquab]

Its not working for me at all. Tried installing MegaCMD 1.4.1 but that just locks up MegaKeep after the first account.

[andiardii]

Yes, its still working

[ComputerSquab]

Its not working for me. Ran it multiple times in a row and I'm still getting the 'we miss you' emails. Mega obviously changed something.

[andiardii]

Hmm, I received email like that after not using this app for few weeks. I think its just notice from mega

[ComputerSquab]

That email means your account is halfway to being considered inactive and MegaKeep should reset the countdown timer. But I ran MegaKeep like 20+ times even repeating my accounts multiple times in the credentials file and nothing I tried reset the countdown timer. The log consistently said "Login Successful" and yet I kept getting the inactivity emails.

The last MegaKeep release was on Jan 19, 2021. Mega clearly changed something about MegaCMD or how they determine inactivity over the past 1,163 days that broke it.

And even when it did used to work, I had to run it a minimum of like 3-6 times in a row or else Mega wouldn't reset the inactivity timer. Since there isn't a native Arch Linux binary of MegaKeep, I have no way of running MegaKeep outside of my Windows 11 kernel virtual machine to check if that works.

And since I'm sure someone will say something, I already know about the MegaKeepsh repo, but all that did was get me sent 'Suspicious login activity' emails without resetting the inactivity timer.

[EROs-eX]

The reason for your issue is really simple after some investigation. You either must update MegaCMD to its latest version and hope this is just it or if that does not work you must change your password string to possibly every account as it is too complex for MegaKeep to understand. If you've added apostrophe's, comma's, forward and backward slashes, hyphens, colons and so forth alongside capitals and small letters of the alphabet and numbers altogether the passwords maybe too complex for MegaKeep. I had the same issue as you all did and how I solved it.

While it would show on MegaKeep's UI logs that login was successful it did not reflect that in the Mega account itself more specifically the login logs. These logs will show if you've logged in using Desktop, MegaSync, MegaCMD and so on.

So to fix this issue you will have to do what I did (get ready for the big sigh) and that is log into each of your account, one by one, and check if MegaCMD logged in successfully or not. You should also see a login by your Desktop or whatever device you're using in conjunction. If it does not show up you must change your password to something less complicated for MegaKeep. I still added some comman's, colon's and so forth but it was less this time. Do also note that you are extremely careful and not zoning out when changing your password. Backup your original password on a different txt, type or paste in the new password, logout, run the program, log into your account again and recheck the logs doing this to every account you have.

When you're completely done toss this backup as I lost some accounts after doing so many accounts, one right after another, zoning out. If this happens take a break or do something else unless you're going to lose those accounts because you were either lazy or read this post and are running out of time. Another note on changing the password it seems to do the best with just capitalized and small letters and numbers. I didn't do this all the time choosing to add a little bit more complexity. Only when MegaKeep would refuse to accept it did I just settle with making it easier.

This entire thing took me several days to complete.

Another thing I want to add. I also noticed MegaKeep would get some errors or get stuck. If you resolved changing the password and time has passed since the last update to MegaCMD see if that resolves the issue. If not, then try this other solution. Split up your account passwords into two or more txt files. There seems to be a limit per file now. Before I could put all the accounts into one file but seems now I have to do two files after some update on Mega's end which conflicted with MegaKeep in some way. I do not want to elaborate the exact amount as to not to expose myself but thankfully the program still works nonetheless. Split them up, run the program, check if it's logging in and out then leave it on and comeback later. Once the logs show it is finished in the UI check the actual logs and spot if all logins were successful. Then run it again with the second txt file and repeat.

There shouldn't be any issues. I did everything on a normal PC running Windows 11. I did lose some accounts changing my password and not backing it up or changing it into something else while I was zoning out doing all this after awhile, so be careful. Peace.