Is it possible to integrate WinSCP with Backblaze's B2 cloud storage? There's some software supporting Backblaze however it's either expensive or it doesn't have features that I want and WinSCP does have and I already fell in love with it :)
I think it shouldn't be a difficult task, here's how to do it.
Though there are so many cloud storages. We cannot implement them all. If we start doing that, we will for sure start with the major ones, line OneDrive, S3, etc.
Please include Backblaze and additional Cloud Providers
I have always preferred WinSCP over pretty much every other FTP client simply because it is so easy to use, and it integrates nicely with PuTTY so when I log into a Linux server I have both GUI & CLI options available to me. Today though I was searching for a way to easily connect to Backblaze, I used CyberDuck and it continues to crash when trying to remotely move files from one folder to another, and unfortunately I am now considering purchasing FZ Pro because of the integration with Backblaze.
I'd love to help however I can to help get this integrated into the product.
Just as an idea. Maybe it can be relesed as a kind of plugin or the separate ini? The are thousands of cloud storages it be great to connect simply. Peranally I need 3-4 of them, not listed in... Also others may not need to connect it daily.
Excessive S3 List Object Calls When Uploading to Backblaze B2
Hi, my upload to the Backblaze bucket via WinSCP was cut short when my daily Class C transactions hit the 2,500 free cap. As shown in the screenshot, WinSCP appears to be making a large number of S3 list object calls, which are counted against the free cap for assessing files that have been uploaded.
Could someone explain how WinSCP actually works while uploading files and suggest any ways to mitigate those calls?
Re: Excessive S3 List Object Calls When Uploading to Backblaze B2
@kelly: Please start anew topic and attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.