meganz
ERROR reading output (state change): The sever problably exited. 231 Error.
CMD has started to behave very strangely in the last few days. Rebooted it and still, the problem remains in the inviting of other users to the folder. https://disk.yandex.com/i/naqYbefECZWMpg https://disk.yandex.com/i/-1UodTwH-hdSgA HELP ME!
Reinstalled the software. The story has changed. Errors are gone, but the invitations are not sent. And if it is sent, it is "unencrypted folders". And users can not see the material. https://disk.yandex.com/i/KPgjJS8eHkW9-g
I decided to check and see for myself. Yes, the problem is observed. How to fix it? https://disk.yandex.com/i/vTgqV0jMQtSxJQ
As of MEGAcmd 1.6.0, and with the aim of increasing your security, in order for shares to work you need to:
- Ensure you have upgraded your account security.
You should have seen a message like this:
-----------------------------------------------------------------------------
| Your account's security needs upgrading. |
| Please execute: "confirm --security". |
| This only needs to be done once. If you have seen this message for |
| this account before, please exit MEGAcmd. |
-----------------------------------------------------------------------------
In order to upgrade your accounts security, do as it say: confirm --security.
- You need to verify your contacts (and they need to verify you).
Instructions on users --help-verify.
In short, use users --help-verify contact@email to get verifying credentials and ensure that your contact is is who he says he is (by sharing the credentials through another secure channel). Then users --verify contact@email to verify him. He would need to do the same with you in order for shares to work.
@polmr It's unreasonable. It's important to be more mobile these days. For the average person, when this cloud is new. We'll have to make some extra moves, in addition to access. And it does not affect security.
I got a lot of errors since the update to 1.6.0 Reverting to 1.5.1 "resolves" the issue. Not the ideal solution, but I even can't connect to my account with the new version...
Very inadequate decisions made by the developers. Authentication, which is on the security side, is in fact just a button. This is from the area of "Are you 18 years old?", a 13 year old growing up presses "Yes". Lol.
@polmr Why do my clients now have problems with "unencrypted folders". Authenticity is confirmed through the browser. As a result, a lot of time is spent on correspondence and problem solving with each client. So much time has been invested in organizing all the folders. And three months later, you've ruined everything. Give it all back!
This measure has been implemented in order to strengthen the security of our customers and the protection of their data. We are working in improving UX experience in that regards and will soon release newer versions in that regards. Thanks for your feedback and apologies for any inconvenience.
@polmr You have lost your mind on this security. And slowed down the performance of the cloud by more than 50%. For security on the client side, a password + 2AF is enough. Security is about keeping intruders off your servers. It's not about writing "Confirm" in the console. Lol.
@polmr Hi, I ran the command and got this error log, do you know why? Thanks
mega-confirm --security
---------------------------------------------------------------------------------------------------------------------
| Your account's security needs upgrading. |
| Please execute: "confirm --security". |
| This only needs to be done once. If you have seen this message for |
| this account before, please exit MEGAcmd. |
---------------------------------------------------------------------------------------------------------------------
[err: 05:28:55] Failed to confirm security upgrade: Temporarily not available
This error still occurs off and on when making large file transfers over WebDAV. And also Failed to access server: 231.
MEGAcmd version: 1.7.0.0
