Timbo

Members
  • Content Count

    106
  • Joined

  • Last visited

Everything posted by Timbo

  1. That's not a solution. That's not even an acceptable workaround. I'd rather the resources go into preventing and automatically resolving such an issue, not allow the worst band-aid, ever.
  2. - uninstall - Just delete the .db files No app needed, and if it was needed, these actions should never, ever have to be done. Resilio resources are stretched and need to prioritize. This ain't one of them. Any improvements to fix syncing issues should be implemented in the webGUI and visible to the user so its more intuitive than having to break out the CLI tool and read up on documentation.
  3. My feedback: Upgraded main Windows sync from 2.6.3, was the fastest and easiest upgrade I've ever experienced with Resilio so far. I almost thought the install didn't happen but Resilio opened up and showed 2.7.1 version. So far, only issue is that my local windows peer on the network is now showing up twice, as "Offline" and "Synced with". The peer correctly shows only one instance name of my main windows box. I've reopened Resilio and same thing. Maybe it'll time out. Upgraded my other windows sync box on the network. This time, I was prompted to set a default sync mode that I've NEVER seen before. Don't know why it showed up on the 2nd Windows upgrade but not on linux or my main windows box. Also, looks like the listening port changed from what it was previously set and had to set it back. I see a note in the release notes about it getting fixed on Linux from randomly changing, hopefully its also resolved on Windows. I wonder if the port change explains the duplicate Offline/Synced with appearing on the other side. Lastly, I saw a huge improvement from 100Mbps to 300Mbps receiving from a Centos 8 VPS after upgrading the linux side from 2.6.3 to 2.7.1. I hope that wasn't just a coincidence and I'll know next time I have a large transfer.
  4. On May 21, @Helen said "Packages will be pushed to repo later". That being said, I said, "what the hell" and upgraded from 2.6.3 to 2.7.1.1370 on Centos 8 VPS and saw a substantial improvement. Finally seeing speeds I was expecting to see. On 2.6.3 right before the upgrade, it was averaging about 12MB/s (~100Mbps) from a VPS to my home. And I've consistently seen it max out around that for a long time. After the upgrade, the transfer resumed at ~300Mbps. Next time I have a long transfer, I'll check top for rslsync's CPU usage. I've thought that was using a lot for the 100Mbps transfers, and I wouldn't be surprised if it went down despite improving 3X. I think I might actually bite the bullet and upgrade my Windows machines that have 10GBe nics that generally don't do over 2.2Gbps with Resilio and see if I notice the computer not freezing up during the transfers.
  5. If you've seen the current debug logs, I doubt there is interest in users self debugging issues. It's not an open source product and fixing the problem isn't really in the user's capability, so spending resources on user's to use CLI debugging tools doesn't make much sense. They'd rather you contact them directly to get to the root of the problem, and then they'll assign resources to bugs that users are actually complaining about. But +1 vote for improving their logging verbosity and structure.
  6. I think leaving it default enabled and 30 days is best for the majority of users, especially since you should always lean towards data safety by default. I've had a few accidental deletes on media files and being able to go to the other side, move it from archive back into the sync folder and recover is by far faster and easier than having a separate backup solution. But they need to break out a lot of the power user settings into main configuration settings so that it isn't forgotten about and is brought to user's attention before they run out of space. Setting your trash days from 30 to 7 (or less) would be a nice trade off between catching the odd "oops" and running out of storage.
  7. kos13, Good post. I'm glad you guys were able to take care of the server refugees. Yes, that would have been ideal. I'm glad this was actually on your radar, at least. Next time... On the licensing front, am I correct that Pro license was a 5 user license and now a business license with 1 Server license means they would get a 20 user license? Or you're cooking up a special 5 user license for Pro->Server refugees? And I assume you've implemented a cutoff date < June 1st? Or I guess you just can't buy Pro anymore, so that is probably moot.
  8. Another problem with just releasing this feature deprecation without a release in between, is that on Server installs you should flat out prevent auto upgrade instead of allowing it. Upgrading within software and it stops working, that is 100% on the vendor and totally avoidable. Microsoft deprecates major features in nearly all the major releases they do when the feature was poorly designed or it has minimal usage. The differences are that they do not hide the fact, they announce it MONTHS in advance, they release beta builds without said features, and while they may ADD additional licenses (ie, Workstation Pro), they don't kill off fundamental functionality of a PAID feature tied specifically to the license purchased. Microsoft license says Home for Home and Pro for businesses, but they don't prevent Home from operating at businesses, they just limit features to the license they want to sell. There's other companies that charge a lower fee for when their software runs on desktop versions vs server versions (Acronis). However, they specifically excluded the Home Server 2011 (Which is just a lower featured server) from requiring business licenses. Companies usually charge more for when it is installed on Server versions because the labour to QA and ensure stability on Server versions is much higher than desktop versions. But does Resilio actually have QA cycles or just the developers commit their changes and run with it (my impression based on all evidence)? The installer was made May 7th and was released to the public on May 8th. Software projects with FAR, FAR few features and platforms takes longer to do basic sanity checks than that. The long delay between 2.6.3 and 2.7.0 with Server deprecation implies this was a planned and intentional move by Resilio to affect and disrupt as many users as they could. All the bug fixes are not available to the existing Server users who need to remain at 2.6.3. This comes off as Resilio being hostile to their customer base. There just isn't a lot of real world experience on the Resilio Development team (very young team?). Time and time again over the years, decisions are made that are 180* opposite with what well established software companies do for the good of both the developers and the customers. Usually, there should be an experienced manager running a team like this that forces good practices on the developers and prevent numerous issues Resilio has had over the years.
  9. Just to be clear, no, not "completely legal". All Microsoft can verify is that a key is valid, they cannot validate the license terms you're clearly breaking. Legal isn't defined by whether the key installs or not, its usage. You're not even being naive (ignorance is not a legal argument), just obtuse. That being said, many IT people have home labs and access to technical subscriptions from Microsoft and can obtain legal licenses for cheap (no, not $12, either) that are NOT intended for production but testing and development purposes. Having access to Windows Essentials by an IT person is pretty common. But again, not intended for use in production. If you don't understand anything I'm saying, the takeaway is that you're going to pay close to the MSRP to legally use Windows Server in "production environment" (home use is production if its not just used for test purposes). All Microsoft cheap licenses are only intended for internal testing purposes. Full.Stop. Resilio has several ways to enforce Business licenses on business usage. Most companies just try and ensure the branding and the terms that is for home use and not in a business so that company employees know they are cheating Resilio. It's a shame and embarrassment move. Think you'll see HP or Microsoft using Resilio without a business license? Never. Think you'll see this prevalent in India? Yes. But companies that have minimal users won't really care if anyone sees this branding, so it has little effect and Resilio has to burn it down completely. Will this move turn non-paying business circumventors into paying? No. Will it alienate the existing customer base that have only been using it for personal usage and have no funds or desire to pay $$$? Yes. I will be losing Sync functionality with my Windows 2016 VPS' which means I'll be sticking with 2.6.3 on these until they run into some issue that requires me to move to another solution.
  10. @Helen 1. When will the linux repo's be updated to 2.7.0? The Centos repo is still 2.6.3. It is my understanding you initially said linux x86/x64 wouldn't be supported anymore but I assume your edited post and release notes that specifically say Windows Servers no longer includes Linux OS so that Linux VPS' will continue to be supported? 2. Are there any known issues if Windows Server version 2.6.3 inter-operated with 2.7.0+ going forward? All the home users that used Resilio on cheap Windows VPS' ($25-$55/year) that are clearly not in the business or Enterprise game need to stick with 2.6.3 or move to other solutions. Thanks Edit: Also, please clarify if Windows 10 Enterprise is blacklisted as well. That truly is an Enterprise only OS, more so than the Server versions, actually.
  11. Dude, just don't update your programs and stop complaining about an issue only existing in your head. Talk about nonsense... The users generally chomping at the bit for updates is that we have chronic issues that don't get addressed. So for us as users, we always have to decide to put up with bugs/workarounds or look for another program. If development is stopped, then we know to look for permanent solutions, not temporary workarounds. If development isn't stopped, then an update may fix it and then its wait and see. Plenty of updates in the past have resolved previous issues, just look at the change log! For me, Resilio just isn't the syncing app for me for music on Android and time for alternate solutions. I sold my NAS because Resilio kept making it run out of memory. On the desktop, they generate a high amount of system interrupts and freezes up my PC during 1Gbps+ transfers (I have 10Gbps NICs). Syncs that show "a few seconds" that have hours to transfer or have no active peers online (this bug has been there for ages and irritates the crap out of me). Syncs that have a few conflicts but when you go to see which files, it says no peers online, or never shows the names of the files to better understand the problem or how to resolve them. They default to debug logging so your SSD's are getting written to constantly. The debug requires a decoder ring and not written for easy debugging except by Resilio. Lots of little things you see when you use the program a lot or have more devices or more situations, etc. If they were fixing bugs in their Android app or their NAS apps, then waiting 6+ months between releases makes no sense as they're depriving users of fixes. Going a long time between releases on new features or changes in operation makes it harder to correct if the users do not like them. There are always bugs and unforeseen problems in software, but the longer between releases and the bigger the changes in each release, the harder it is to find the root cause of new bugs or undo unpopular changes.
  12. How about a link to an internal Windows version that has a fix for when the sync fails at like 16% showing a conflict with 2 files, but instead of saying which two files are in conflict, it just goes to a Loading... page that says "These files cannot be downloaded as there are no source peers online for too long time. Sync will continue downloading if any source peer appears online" and never ever finishes loading to show the 2 frickin' files holding up TB's worth of syncing. It's the most frustrating bug for me for 2018-2019 (yes, more than a year old bug). The source side shows no problems so you think the other side is fine, too, except you find out later that sync was stuck and the check mark status is 100% garbage misleading. This bug has bitten me at least 5 times that if I had known there would STILL not be a fix after 1.5 years, I would have switched to something else by now. Taking so long between releases is just a bad, bad idea and doesn't give much hope of things ever getting better.
  13. How large is the folder? It shouldn't be 100% for very long. Do you have a decent hard drive or is it old and slow?
  14. I don't know if this is a Resilio or Linux issue, as I run into problems with users not having write permissions despite being in the group on Linux from time to time. Solution has been to use setfacl and give write access to the Resilio dirs to the user. Easier than changing users, systemd files or using chown over and over.
  15. I wouldn't try and copy over settings, I'd just re-set up the link. It'll scan both sides, determine they are in sync and then be happy. It won't retransmit everything again. If you had tons of shares, that might be worth it, but for 1? Just recreate the sync on the two new machines.
  16. Ah, you're right. That might be a privileged port thing like linux. You'd have to port forward port 443 in your router to the internal 5 digit port number of your sync install.
  17. Your company will have a policy on allowed software. They only want traffic going through port 80 and 443 so they can monitor it and make sure they don't have security issues. You're wanting to use software that isn't using http/https protocol to circumvent the companies policy. Resilio wants to sell their software to businesses, and they're not going to take kindly to a change like this. You're putting the "detour" effort on Resilio instead of yourself, which I think is wrong. Try and configure your Sync peers to listen on ports 80 or 443. Then you can put in the address of your peers and you won't need a VPN or need the relay. Since you want to use Resilio in business setting, you'll have a Pro license, you can do a feature request or contact support directly and get an official response from Resilio.
  18. Ah, I see (not really). Must be a Pro feature, as the free version doesn't have servers, just peers, nor default folders (the default folder is for config files, not sync). Checking the website, I see this "feature". You're probably going to have to open a feature request to add an option to not sync when adding a folder automatically. Add Folders to All Your Devices Automatically PRO Sync every folder automatically to all your devices. You add a folder to one and it automatically becomes available on all your linked devices.
  19. What? I don't know what/why/how dragging is different, but adding a folder should NOT automatically sync with all peers for other folders unless the peers also have that folder added. On my main PC, I have several folders sync'd with PC1 only, other folders with PC2 only, and other folders with all three PC's syncing. Let's say I have PC1, PC2, PC3 If I add a folder to PC1, it syncs with nothing unless I also add that folder on PC2 or PC3. I add Folder-Music to PC1. I copy the read/write key and add to PC2 and PC3. Music is automatically synced to PC2 and PC3. Now on PC1, I add folder "Programs". Again, it syncs with NOTHING until I copy the key and also add to PC2 or PC3. Adding to PC2 does not make it sync with PC3. I think you'll need to provide screenshots of your folder setup for us to better understand your config.
  20. Usually, companies don't like to actively circumvent the firewall protections that you're under, unless it is to get around draconian censorship. The solution is to change your firewall to allow it. That is of course, you're not authorized to be running this software in the first place. That's your problem, not everyone else's. Hint: use a VPN and your problem is solved for any software, not just Sync.
  21. I disagree. I would argue you're simply doing your folder syncs incorrectly. Don't sync the root folder, just sync the folder that the device should have. Adding the folders and having it sync automatically is what most users want most of the time, hence, the best default. You have something like 10 syncs available in the free version. Use them.
  22. That NAS model is too old/underpowered to support Sync.
  23. How much ram does your problem NAS have? I'm going to guess 512MB and your Docker capable has 2GB of RAM.
  24. I would suggest making a separate /etc/nginx/conf.d/browsing.conf whereby server_name will use something like browsing.hostname.org. Just add another A record to your domain DNS.
  25. Well, I'm at about 24GB and I can say the app on my Android hasn't worked since the initial sync 10 days ago. Says there is 1 of 2 peers connected, but just white page when trying to view the peers. The overall problem is they tried to develop too many features in short time without QAing them. Finding bugs within 5 minutes of an upgrade is pretty regular occurrence, but shouldn't be in a mature program.