With the current version of Classic v 9.2.1, if I make a small change to a page and publish and then find I need to make a further change, publishing will cause 100’s of other uploads as well. In my case for one site it is over 460 uploads.
I found that for any subsequent changes, I have to quit RW and open it again to avoid this problem.
Another issue I noticed with RW classic latest version is that after three or four site modification publications, I have to restart RW so that it does not produce the “failed to connect” error in sftp. This is not serious since I only have to restart, that’s why I did not think to report this bug until now. I use an sftp connection with asymmetric authentication keys, FYI.
Hey @martef86,
Are you publishing a blog page per chance?
Hey @Bruno ,
Strange, I’m using SSH key based auth to my server as well and I never experience this. Once the file has been transferred, the SFTP connection should be closed to allow for additional connections. Is your server spawning zombie SFTP connection processes that aren’t getting closed? I’ve seen that before on some peoples’ servers. If you have SSH access to your server you can use the top or htop command to see all running processes.
No, nothing to do with blogs. I can make a simple text change and if I don’t quit first and make another change it will do it. E.g. if I make a change it might upload 2 changes but if I edit the same text again, it will upload over 450 changes.
Hi @dang The server does not present any remarkable element but I’m not in publishing session now. During each publication of site RW works well and returns me “idle” at the end of publication. I then close the publication window. It happens that this problem does not occur despite about ten publications but it is rare, most usually it is after the fourth publication that the problem occurs. Just restart RW and it starts again. Really not a problem, it does not bother me in my use. But it is true that it is always good to know why a problem occurs. I will monitor the server during my next session with several publications (probably next weekend) and see if it is a blow of zombies 
. I will keep you informed. 
1 Like
If you’d like to share your project file with us I’d like to see if I can reproduce this.
I think it is too big and it also accesses many files that are external to the project including several MySQL databases.
I think what I will attempt to do is to experiment with some other projects and see if they replicate the problem and report back.
1 Like