As I mentioned yesterday, I had a long day trying to get my hosting set up with RW.
My hosting company basically gave up yesterday, but I said if RW didn’t work with them, I’d find a host that does. They then promised to look into it a bit more.
Below is the reply I’ve just received.
I’ve done some extensive testing on this, including setting up an entirely separate server and running tests with both TLS and plaintext. Plaintext has no issues at all, and as expected the full 6 connections can be used and operate absolutely fine.
During testing I’ve noticed several anomalies with how Rapidweaver operates over TLS, including reporting that authentication failed when it actually passed (I can see this from the server side). Sometimes it publishes over TLS with one connection, sometimes it doesn’t, in each case the server doesn’t report an error to the client so it’s the application considering it to be failed. Even hitting the ‘test’ button in Rapidweaver fails, but then succeeds to publish correctly (so testing fails but publishing works - sometimes). Rapidweaver even crashed several times during TLS negotiation.
My conclusions are that the Rapidweaver application is failing to operate correctly over TLS encrypted connections in any way suitably.
TLS and encryption in general are now an industry requirement, including for PCI DSS compliance, so this is an issue you would connecting to almost any FTPS service.
Unfortunately, because this is a client problem, it’s not something we can account for on the server side.
So it appears that my host is not compatible.
By the way, what he’s saying is true. It works sometimes, but only with one connection used.
Could it be possible that it just won’t work with my host? If not, I’m happy to look for another.