@Domink: did you get my PMs?
Just stunning work! ![]()
@lukas_jolla2015 yeah, I Left some Message for you at the Weekend â will answer again to Point you to the Right direction
Now found it, through I get any kind of notification if a pm arrivesâŚ
UPDATE: Version 0.4 is now available on CHUM ![]()
The url-selection is much better this way. (In my case the folder name does not match the user-name, but that case is handled nicely)
Can I add more feature-requests? Like an override of the default âBackground syncâ interval and âAllowed networkâ settings per pair?
And multiple accounts? In case you want to synchronize with multiple accounts or services?
Why on Earth do you want it that complicated?![]()
![]()
![]()
- multiple accounts: at the very beginning i decided that it will make things a lot easier to Stick to one Account (and Most of the people do Sync to one cloud) only. If we would Like to Change this again we need to re-write Most of the Core componentsâ> so I would say: no
- Different Sync Intervals per pair And Different Network Rules per pair: also Not easy because the current âTimerâ is Set once and it will do a roundtrip around all Sync Pairs. If we want it configurable per pair would make Everything also a Lot more complicated - Setting up different Timers which run to different Times, checking different Network rules for each pair + make sure old Timers are killed successfully After you changes something + Error Handling for each Timer



I need to think about it, but for now itâs Not on the priority list
Waht do it means, too many changes? there is no one new file in that folders and sync is stopped with this error. scarryâŚ
thatâs the default error message - maybe i donât catched all possible scenarios.
Press long on the failed sync pair and check the detailed logs - i would be happy if you can forward the error message to me then i can map this to another better error message.
After you investigated and checked that everything is fine, you can long press again am continue the sync - should work then
I could have done that right away
Thanks for the tip. It just seems that the connection couldnât be established at this point. I think something like this could be ignored. Or maybe just a warning is enough. We should try again next time.
026/09/03 11:04:10 CRITICAL: Failed to create file system for "ferry:foldername": read metadata failed:
Propfind "https://xyz.de/remote.php/dav/files/user/foldername": read tcp 10.2.0.2:56790->5.253.247.2:443: read: connection reset by peer
Domain, user name and folder name are changed.