![]() MEGA does limit your session creations if your account is starting too many. This tool is not developed or authorised by MEGA and therefore not recommended. Our database shows that your account has created many sessions with rclone which is an unauthorised third party tool. anyone has experience or knowledge of what speeds can i expect from MEGA?Īnyone has a noob friendly source for MEGAcmd? the ones i found are the opposite of noob friendly :) NOTE: I am talking based on the info I have that cloud sync is based on rclone, so please do correct me if I'm wrongģ. Since I'm not sure about the updates coming to TrueNAS core, I don't want to submit something that is already being fixed or already submitted at least and most importantly, they (MEGA) recommended I submit a bug report to add session cashing to rclone/cloud sync, as far as my research got me, rclone has a way of cashing sessions, not sure how is it implemented, or if it's after a certain version, but since I've never submitted a bug report, is this something worth it? (currently trying MEGAsync on my windows PC over a shared drive, hope this is a better option, so far it keeps crashing, and when it works, I'm getting lower speeds, but ill keep you posted)Ģ. ![]() Me being a noob I was worried that I will inevitably do something stupid, and the data will be deleted from the NAS (i want to destroy the volume and rebuild it), so i cannot really afford to do something stupid. will find a way, I was thinking of running some flavor of Linux in a VM (or even bare-metal), learn MEGAcmd, and do it. Now this is the main issue, I have huge experience with CLI tools, and by that I mean I can and that's about it (excuse the lame joke, I'm a CLI noob)ġ. I contacted the support, I got a reply stating that I am creating a crapload of close sessions, which I shouldn't, instead, I can use MEGAcmd. I am only getting around 1~2 MBps (8~16Mbps) I had some data that I wanted to keep online for now, and decided to use MEGA.nz and the built-in cloud sync (FreeNAS 11.3-U5) ![]()
0 Comments
Leave a Reply. |