I have returned to a Classic website (after diving into Elements) to publish a minor update, and find that I’m now getting SFTP time-out failures. The server log for sshd says “Did not receive identification string…”
This worked fine last year, and I’ve not upgraded RWC or MacOS in the meantime. I am also not aware of any change to sshd at the server end (my company’s servers, not a 3rd party hosting provider).
I’m on RWC 9.6.1, which I’m aware is not the latest, but having “migrated” to Elements my Classic subscription has lapsed, so I’m unable/reluctant to upgrade (though I shouldn’t need to as nothing in the environment has changed!).
Does anyone have a clue as to why RWC is not supplying an identification string?
We fixed some publishing issues in later versions of RapidWeaver Classic after 9.6.1. Can you download a demo version of the latest Classic version (9.6.8) and test SFTP uploading on your work servers to see if it works?
You’ll need to use one of the sample project files located in the demo version.
Doesn’t work, but I’m getting a different error in RWC - “Failed initialisation”, and nothing is showing up in our sshd server log at all (which suggests this is an RWC issue…).
I have re-booted too, just to eliminate any OS-type issues, and I can sftp in to the same server from the command line, so no connection issues either.
It’s possible, but I’m having no issue logging into several of my servers via SFTP, which indicates is might be an issue with your work server’s SSH settings, or you just haven’t got the correct SFTP details entered in RapidWeaver’s publishing settings.
Are you using password authentication or SSH key pair to log in?
So, with regard to the SFTP details, they are the ones that were working the last time I updated this site, last year. Haven’t changed the publication settings.
I’m using password authentication.
The weird thing is that having switched back to RWC 9.6.1 I’m now getting the “Failed initialisation” message (and no trace in the server’s logs).
Behaviour in Elements with the exact same SFTP details is the same (“Failed initialisation”).
I could believe it was an sshd config issue if anything was actually showing up in the log (like it was with the “Did not receive identification string” error), but there is apparently no connection. Cyberduck has no problem connecting to the same FTP server via SFTP with the same settings.
For the sake of a quick update I may revert to FTP, but the Elements failure to connect is more troubling.
Without being able to log into your server and tail the auth.log while the connection attempt is happening I’m kind of limited with what I can do.
Can you send over your project file so I can just check your publishing settings and test an upload on my end?
Also can you send over your publishing logs? We have a guide here on how to send those logs over. I can take a look and see if our logging is picking anything up.
Feel free to send in a DM or via our email support@realmacsoftware.com if you prefer to keep the project file private.