You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform version. In the case of Linux, please enter the Linux distribution you are using.
DSM 7.2.1-69057 Update 5
Steps
Create cloud sync in Synology to mega
Choose a folder to sync
The folder gets to around 99 gigs and stops syncing even though Cloud Sync says its syncing, folder size doesn't change. It has been like this for days.
Expected behavior
No response
Actual behaviour
I am using 1.7.0-0001 MEGA-CMD on my Synology NAS. When using cloud sync the folder I am syncing to Mega is around 150 gig. It gets to around 99 gigs in my mega drive and says it's syncing on my Synology but gets stuck in a loop and doesn't keep uploading. This is the second time I have tried and remove all the files from Mega and set up my wed dav cloud sync again.
Also what is the normal delay syncing back to mega from the NAS, cloud sync says it has synced but it takes some time to show up on the mega cloud drive.
Any help would be greatly appreciated.
Tim
The text was updated successfully, but these errors were encountered:
MEGAcmd version
1.7.0
Operating System/Platform
Synology
Platform version. In the case of Linux, please enter the Linux distribution you are using.
DSM 7.2.1-69057 Update 5
Steps
Expected behavior
No response
Actual behaviour
I am using 1.7.0-0001 MEGA-CMD on my Synology NAS. When using cloud sync the folder I am syncing to Mega is around 150 gig. It gets to around 99 gigs in my mega drive and says it's syncing on my Synology but gets stuck in a loop and doesn't keep uploading. This is the second time I have tried and remove all the files from Mega and set up my wed dav cloud sync again.
Also what is the normal delay syncing back to mega from the NAS, cloud sync says it has synced but it takes some time to show up on the mega cloud drive.
Any help would be greatly appreciated.
Tim
The text was updated successfully, but these errors were encountered: