search

meganz / MEGAsync

Easy automated syncing between your computers and your MEGA Cloud Drive
Other
1.63k stars 280 forks source link

MEGAsync conflicts with Synology Drive Client #369

Open GitatHub opened 4 years ago

GitatHub commented 4 years ago

In Windows 10, MEGAsync client conflicts with Synology client. If the two clients are both installed in Windows 10, the earlier installed one, e.g., MEGA, will not work. Who will fix this? I do not think Synology will.

mattw-mega commented 4 years ago

Hi, would you mind providing a few more details - what error message or symptom do you see with both installed? thanks

GitatHub commented 4 years ago

Sorry. I have uninstalled MEGA but I can roughly describe the phenomenon.

  1. Install MEGA, sync folder ABC 1.1 MEGA icon appear in the left navigation panel of Windows 10 Explorer
  2. Install Synology, also sync folder ABC 2.1 Synology icon overwrites MEGA icon and appears in the left navigation panel
  3. MEGA stop to sync folder ABC and the check box in the settings - sync panel is unchecked. Manual re-check the check-box is not applicable.
mattw-mega commented 4 years ago

Thanks very much for the details. There are only a few causes for a sync to become disabled by itself (so that the check box is not ticked anymore), and that happening would cause the mega entry to disappear from the left navigation panel in explorer. If you have a chance to try it again, you could collect a MEGAsync log when that happens (just start it with ctrl-shift held down, and it will write the log to the desktop). We can examine the log to see why the sync becomes disabled - possibly a loss of permissions on the synced folder, possibly Synology is changing those. thanks

GitatHub commented 4 years ago

I repeat this again. The problem is still there. Ctrl-Shift Down did not write a log here. Except the setting interface, I have no where else to get the log from MEGA.

mattw-mega commented 4 years ago

Alternatively you can find logs at "C:\Users\\AppData\Local\Mega Limited\MEGAsync\logs". If the Synology client software is interfering with MEGAsync, another way to interact with MEGA from your NAS is to install MEGAcmd - there is a Synology package for it in their app store equivalent. thanks

GitatHub commented 4 years ago

This should be the last log before I removed MEGA. Hope it be informative. ----------------------------- program start ----------------------------- 04/17-06:21:34.859730 5840 DBG cURL version: 7.59.0 [net.cpp:87] 04/17-06:21:34.859805 5840 DBG SSL version: OpenSSL/1.0.2q [net.cpp:92] 04/17-06:21:34.859809 5840 DBG libz version: 1.2.11 [net.cpp:116] 04/17-06:21:34.859814 5840 DBG IPv6 enabled: 1 [net.cpp:135] 04/17-06:21:34.903232 5840 DBG DNS servers: 159.226.8.6,1.1.1.1,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3 [net.cpp:343] 04/17-06:21:34.903237 5840 DBG Setting filtered DNS servers: 159.226.8.6,1.1.1.1,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3 [net.cpp:357] 04/17-06:21:34.908116 5840 INFO Pdfium loaded [qt.cpp:469] 04/17-06:21:34.913333 5840 DBG MediaInfo version: 1710 [mediafileattribute.cpp:72] 04/17-06:21:34.913416 5840 DBG User-Agent: MEGAsync/4.3.1.0 (Windows 10.0.18363) MegaClient/3.6.6 [megaclient.cpp:1221] 04/17-06:21:34.913418 5840 DBG Cryptopp version: 800 [megaclient.cpp:1222] 04/17-06:21:34.916270 3936 INFO Request (SEND_EVENT) starting [megaapi_impl.cpp:15636] 04/17-06:21:34.916300 3936 WARN Event 99504: eyJpdCI6MTU4NzEwMzgxMywiYWN0IjowLCJsdCI6MTU4NzEwMzg2Nn0 [megaclient.cpp:14118] 04/17-06:21:34.916547 3936 DBG Resolving IPv4 address for g.api.mega.co.nz [net.cpp:1798] 04/17-06:21:34.923896 3936 DBG c-ares info received [net.cpp:1008] 04/17-06:21:34.923908 3936 DBG Received a valid IP for g.api.mega.co.nz: 31.216.147.134 [net.cpp:1016] 04/17-06:21:34.923924 3936 DBG Name resolution finished [net.cpp:1174] 04/17-06:21:34.923948 3936 DBG cs POST target URL: https://g.api.mega.co.nz/cs?id=hodqisgmtj&ak=FhMgXbqb [net.cpp:1252] 04/17-06:21:34.923950 3936 DBG cs Sending: [{"a":"log","e":99504,"m":"eyJpdCI6MTU4NzEwMzgxMywiYWN0IjowLCJsdCI6MTU4NzEwMzg2Nn0"}] [net.cpp:1263] 04/17-06:21:34.923954 3936 DBG Using the IP of the hostname: 31.216.147.134 [net.cpp:1280] 04/17-06:21:34.923990 3936 DBG Set cURL timeout[2] to 1358 ms from 0 [net.cpp:2528] 04/17-06:21:34.924076 3936 DBG Disabling cURL timeout [net.cpp:621] 04/17-06:21:34.924274 3936 DTL cURL DEBUG: Trying 31.216.147.134... [net.cpp:1626] 04/17-06:21:34.924291 3936 DTL cURL DEBUG: TCP_NODELAY set [net.cpp:1626] 04/17-06:21:34.924706 3936 DBG Adding/setting curl socket 1268 to 2 [net.cpp:2454] 04/17-06:21:34.924722 3936 DBG Set cURL timeout[2] to 1360 ms from 200 [net.cpp:2528] 04/17-06:21:35.124798 3936 DBG Disabling cURL timeout [net.cpp:621] 04/17-06:21:35.124895 3936 DBG Set cURL timeout[2] to 1478 ms from 11797 [net.cpp:2528] 04/17-06:21:35.147368 3936 DTL cURL DEBUG: Connected to 31.216.147.134 (31.216.147.134) port 443 (#0) [net.cpp:1626] 04/17-06:21:35.147578 3936 DTL cURL DEBUG: ALPN, offering http/1.1 [net.cpp:1626] 04/17-06:21:35.147659 3936 DTL cURL DEBUG: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH [net.cpp:1626] 04/17-06:21:35.147854 3936 DTL cURL DEBUG: TLSv1.2 (OUT), TLS header, Certificate Status (22): [net.cpp:1626] 04/17-06:21:35.147859 3936 DTL cURL DEBUG: TLSv1.2 (OUT), TLS handshake, Client hello (1): [net.cpp:1626] 04/17-06:21:35.147870 3936 DBG Adding/setting curl socket 1268 to 1 [net.cpp:2454] 04/17-06:21:35.371039 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS handshake, Server hello (2): [net.cpp:1626] 04/17-06:21:35.593436 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS handshake, Certificate (11): [net.cpp:1626] 04/17-06:21:35.594177 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS handshake, Server key exchange (12): [net.cpp:1626] 04/17-06:21:35.594712 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS handshake, Server finished (14): [net.cpp:1626] 04/17-06:21:35.600185 3936 DTL cURL DEBUG: TLSv1.2 (OUT), TLS handshake, Client key exchange (16): [net.cpp:1626] 04/17-06:21:35.600193 3936 DTL cURL DEBUG: TLSv1.2 (OUT), TLS change cipher, Client hello (1): [net.cpp:1626] 04/17-06:21:35.600317 3936 DTL cURL DEBUG: TLSv1.2 (OUT), TLS handshake, Finished (20): [net.cpp:1626] 04/17-06:21:35.824387 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS change cipher, Client hello (1): [net.cpp:1626] 04/17-06:21:36.171821 3936 DTL cURL DEBUG: TLSv1.2 (IN), TLS handshake, Finished (20): [net.cpp:1626] 04/17-06:21:36.171840 3936 DTL cURL DEBUG: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 [net.cpp:1626] 04/17-06:21:36.171842 3936 DTL cURL DEBUG: ALPN, server did not agree to a protocol [net.cpp:1626] 04/17-06:21:36.171851 3936 DTL cURL DEBUG: Server certificate: [net.cpp:1626] 04/17-06:21:36.171895 3936 DTL cURL DEBUG: subject: C=NZ; postalCode=1010; ST=Auckland; L=Auckland; street=15, Pwc Tower, 188 Quay Street,; O=Mega Limited; OU=PremiumSSL Wildcard; CN=.api.mega.co.nz [net.cpp:1626] 04/17-06:21:36.171909 3936 DTL cURL DEBUG: start date: Dec 11 00:00:00 2017 GMT [net.cpp:1626] 04/17-06:21:36.171914 3936 DTL cURL DEBUG: expire date: Dec 10 23:59:59 2020 GMT [net.cpp:1626] 04/17-06:21:36.171942 3936 DTL cURL DEBUG: issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Organization Validation Secure Server CA [net.cpp:1626] 04/17-06:21:36.171951 3936 DTL cURL DEBUG: SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. [net.cpp:1626] 04/17-06:21:36.171981 3936 DTL cURL DEBUG: public key hash: sha256//XXXXXX= [net.cpp:1626] 04/17-06:21:36.172089 3936 DBG Adding/setting curl socket 1268 to 3 [net.cpp:2454] 04/17-06:21:36.172164 3936 DTL cURL DEBUG: We are completely uploaded and fine [net.cpp:1626] 04/17-06:21:36.172168 3936 DBG Adding/setting curl socket 1268 to 1 [net.cpp:2454] 04/17-06:21:36.394044 3936 DTL Header: HTTP/1.1 200 OK [net.cpp:2341] 04/17-06:21:36.394052 3936 DTL Header: Content-Type: application/json [net.cpp:2341] 04/17-06:21:36.394055 3936 DTL Header: Access-Control-Allow-Origin: [net.cpp:2341] 04/17-06:21:36.394057 3936 DTL Header: Access-Control-Allow-Headers: Content-Type, MEGA-Chrome-Antileak [net.cpp:2341] 04/17-06:21:36.394059 3936 DTL Header: Access-Control-Expose-Headers: Original-Content-Length [net.cpp:2341] 04/17-06:21:36.394062 3936 DTL Header: Access-Control-Max-Age: 86400 [net.cpp:2341] 04/17-06:21:36.394064 3936 DTL Header: Original-Content-Length: 3 [net.cpp:2341] 04/17-06:21:36.394081 3936 DTL Header: Content-Length: 3 [net.cpp:2341] 04/17-06:21:36.394084 3936 DTL Header: Connection: keep-alive [net.cpp:2341] 04/17-06:21:36.394107 3936 DTL cURL DEBUG: Connection #0 to host 31.216.147.134 left intact [net.cpp:1626] 04/17-06:21:36.394111 3936 DBG Removing socket 1268 [net.cpp:2440] 04/17-06:21:36.394126 3936 DBG CURLMSG_DONE with HTTP status: 200 from g.api.mega.co.nz - 31.216.147.134 [net.cpp:2030] 04/17-06:21:36.394128 3936 DBG cs Received: [0] [net.cpp:2059] 04/17-06:21:36.394135 3936 DBG Set cURL timeout[2] to -1 ms from -1 [net.cpp:2528] 04/17-06:21:36.394165 3936 INFO Request (SEND_EVENT) finished [megaapi_impl.cpp:15668]