poescp

Members
  • Content Count

    12
  • Joined

  • Last visited

About poescp

  • Rank
    Member

Recent Profile Visitors

414 profile views
  1. Thanks, which files exactly should I send to the support system? You only mention paths.
  2. None of the above show up, only following ... will PM you with the dump [20160224 00:17:18.724] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b4f3a08, tunnels: 0 [20160224 00:17:19.234] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:19.234] PeerTLSEH[0x3bc6beb0]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:19.235] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:19.235] PeerTLSEH[0x3ae0edb8]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:43.202] LF[8A8B]: LicenseFolder::IsActive(user): return FALSE, id is not in active list, total ids = 1 [20160224 00:17:43.202] LF[3A89]: LicenseFolder::IsActive(trial): return FALSE, license expired [20160224 00:17:47.061] SyncSocket[0x3bac4150]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.062] PD[64D4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3bac4150, tunnels: 0 [20160224 00:17:47.062] PD[64D4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:47.063] PeerTLSEH[0x3b485f98]: hello packet { share:E9314AB25C848C29D921B31E43F34154A404211F } has been sent [20160224 00:17:47.741] SyncSocket[0x3aeea3e8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b8303d8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] PD[62E7] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3aeea3e8, tunnels: 0 [20160224 00:17:47.742] SyncSocket[0x3b5eb5b0]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3aef7398]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b5c7f68]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b81bed8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b6fc600]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b3feeb8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b898928]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] PD[62E7] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b8303d8, tunnels: 0 [20160224 00:17:47.742] PD[64D4] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b5eb5b0, tunnels: 0 [20160224 00:17:47.743] PD[63C0] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3aef7398, tunnels: 0 [20160224 00:17:47.743] PD[63C0] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b5c7f68, tunnels: 0 [20160224 00:17:47.743] PD[9209] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b81bed8, tunnels: 0 [20160224 00:17:47.743] PD[9209] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b6fc600, tunnels: 0 [20160224 00:17:47.743] PD[C73C] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b3feeb8, tunnels: 0 [20160224 00:17:47.743] PD[C73C] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b898928, tunnels: 0 [20160224 00:17:48.251] PD[64D4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.252] PeerTLSEH[0x3b567558]: hello packet { share:E9314AB25C848C29D921B31E43F34154A404211F } has been sent [20160224 00:17:48.287] PD[63C0] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.287] PeerTLSEH[0x3b593088]: hello packet { share:6B14A88C904FEB4F03A074F93D746872B2495A30 } has been sent [20160224 00:17:48.288] PD[63C0] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.288] PeerTLSEH[0x3bd295b8]: hello packet { share:6B14A88C904FEB4F03A074F93D746872B2495A30 } has been sent [20160224 00:17:48.289] PD[9209] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.289] PeerTLSEH[0x3b4f3a08]: hello packet { share:1A3844245205DDCD73573C8FBE9061662043383C } has been sent [20160224 00:17:48.289] PD[9209] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.289] PeerTLSEH[0x3bd9cca0]: hello packet { share:1A3844245205DDCD73573C8FBE9061662043383C } has been sent [20160224 00:17:48.290] PD[C73C] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.290] PeerTLSEH[0x3bac4150]: hello packet { share:89598492886EE7A58248C2D7AF0A2637E45C3FF7 } has been sent [20160224 00:17:48.291] PD[C73C] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.291] PeerTLSEH[0x3b34d218]: hello packet { share:89598492886EE7A58248C2D7AF0A2637E45C3FF7 } has been sent [20160224 00:17:48.292] PD[62E7] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.292] PeerTLSEH[0x3bb0c348]: hello packet { share:1B90BB1D3968AD63DFA7BAC47FAF8EDEDFF82DF4 } has been sent [20160224 00:17:48.292] PD[62E7] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.292] PeerTLSEH[0x3bc34480]: hello packet { share:1B90BB1D3968AD63DFA7BAC47FAF8EDEDFF82DF4 } has been sent [20160224 00:17:48.741] SyncSocket[0x3bc6beb0]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:48.741] SyncSocket[0x3ae0edb8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:48.742] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3bc6beb0, tunnels: 0 [20160224 00:17:48.742] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3ae0edb8, tunnels: 0 [20160224 00:17:49.252] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:49.252] PeerTLSEH[0x3b6cfb50]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:49.253] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:49.253] PeerTLSEH[0x3b3feeb8]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:18:08.070] UPnP: Could not map UPnP Port on this pass, retrying. [20160224 00:18:10.160] Requesting folder config from config.getsync.com
  3. Hi, Very interesting case ... BTSync on my NAS Synology DS 715 automatically stopps running and is deactivated, without myself having done anything. Every few days I have to manually restart BTSync. I have 2.3 as a version. Any ideas what this could be? Phil
  4. Would be great to have the update for 2.1.3 as there have been major changes ...
  5. Hi, I have BTSync installed on a NAS and everthing works well at first. But after relogging I only get an empty page, well more the known grey row, but without the icons and no folders. Synology NAS. I empty the Browser Cache and restart and I am asked for password/user and login works, but no folders, no menu, only the grey background of the known icons. Anyone got an idea? Phil
  6. Same issue with me. Ubutunu server with a Synology NAS 214se. 20 GB and 150000 files. BTSync syncs every few our a few files. After 24 hours only 1 % synced. There mus be a bug here. Sync 2 on both.
  7. Hi, I am BTSync 2 installed on my Ubuntu Server and on my NAS. I connect both devices starting to add a folder from the Server and then pasting the code into NAS. Sofar all OK. Then I see "Pennding Approval" on the NAS, but not Accept on the Ubuntu Server. Further: Also tried the option to deactivate ask for Approval, but still "Pending Approval" was shown on the NAS. The server/NAS time are in sync. Any ideas? Phil
  8. Currently having problems with trying to sync my laptop with the Server Version GUI of BTSync. When I select a folder (chmod 0770, btsync:btsync) on the server (linnux) I get following error: "Confirmation - Folders not found - Do you want to create a new one?". However I cannot create a folder or sync into the current folder. Found nothing on the issue in the Internet. Any ideas?
  9. Hi, I have a Synology NAS and BTSync by large video files (20 x 300 MB files) between my laptop and the NAS. I only changed the folders, meaning copied the files into a subfolder that I newly created and now all files are being synced newly even though they were already on the NAS. So basically the files are newly synced between both devices via LAN (1 Gbit connection and Gbit switch between). I though only the information of the folder change would be synced not all files. Please could you help.