Problem Publishing Directly from RapidWeaver

Classic
1

I have built a website here using the Realmac RapidWeaver theme “Final”…

Although this is quite an old theme it works well and my client loves the site.

The issue I have had ever since my client switched to their new hosting company (using FTPS) is that I am unable to upload directly from the RapidWeaver project file. I have to publish the files remotely and then upload them manually via Transmit. Here are the publishing settings I have…

Endo-Publishing-Settings
Endo-Publishing-Settings1292×1186 78.7 KB

What’s curious is that the site test in the publishing window tests fine but when I hit the publish button I get an error message…

Endo-Publishing-Error
Endo-Publishing-Error1350×856 258 KB

Assuming this was a hosting issue I contact the host and they ran some tests and made some tweaks but every time we tried we just couldn’t get it to work directly from RapidWeaver. Here is the error log from the host…

Log for TLS whilst performing test

2024-03-08 21:19:01,232 mod_tls/2.7[771915]: SSL/TLS-P requested, starting TLS handshake
2024-03-08 21:19:01,264 mod_tls/2.7[771915]: client supports secure renegotiations
2024-03-08 21:19:01,264 mod_tls/2.7[771915]: TLSv1.3 connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:01,310 mod_tls/2.7[771915]: Protection set to Private
2024-03-08 21:19:01,585 mod_tls/2.7[771915]: starting TLS negotiation on data connection
2024-03-08 21:19:01,612 mod_tls/2.7[771915]: TLSv1.3 data connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)

Log for TLS whilst trying to publish

2024-03-08 21:19:19,059 mod_tls/2.7[771948]: SSL/TLS-P requested, starting TLS handshake
2024-03-08 21:19:19,090 mod_tls/2.7[771948]: client supports secure renegotiations
2024-03-08 21:19:19,090 mod_tls/2.7[771948]: TLSv1.3 connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,130 mod_tls/2.7[771948]: Protection set to Private
2024-03-08 21:19:19,185 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:19,299 mod_tls/2.7[771948]: TLSv1.3 data connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,450 mod_tls/2.7[771949]: SSL/TLS-P requested, starting TLS handshake
2024-03-08 21:19:19,451 mod_tls/2.7[771950]: SSL/TLS-P requested, starting TLS handshake
2024-03-08 21:19:19,499 mod_tls/2.7[771949]: client supports secure renegotiations
2024-03-08 21:19:19,500 mod_tls/2.7[771949]: TLSv1.3 connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,502 mod_tls/2.7[771950]: client supports secure renegotiations
2024-03-08 21:19:19,502 mod_tls/2.7[771950]: TLSv1.3 connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,550 mod_tls/2.7[771950]: Protection set to Private
2024-03-08 21:19:19,550 mod_tls/2.7[771949]: Protection set to Private
2024-03-08 21:19:19,556 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:19,605 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:19,605 mod_tls/2.7[771949]: starting TLS negotiation on data connection
2024-03-08 21:19:19,633 mod_tls/2.7[771950]: TLSv1.3 data connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,633 mod_tls/2.7[771949]: TLSv1.3 data connection accepted, using cipher TLS_AES_256_GCM_SHA384 (256 bits)
2024-03-08 21:19:19,815 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:20,093 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:20,093 mod_tls/2.7[771949]: starting TLS negotiation on data connection
2024-03-08 21:19:20,146 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:20,237 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:20,282 mod_tls/2.7[771949]: starting TLS negotiation on data connection
2024-03-08 21:19:20,470 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:20,591 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:20,656 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:20,692 mod_tls/2.7[771949]: starting TLS negotiation on data connection
2024-03-08 21:19:20,865 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:21,016 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:21,055 mod_tls/2.7[771949]: starting TLS negotiation on data connection
2024-03-08 21:19:21,082 mod_tls/2.7[771948]: starting TLS negotiation on data connection
2024-03-08 21:19:21,230 mod_tls/2.7[771950]: starting TLS negotiation on data connection
2024-03-08 21:19:21,373 mod_tls/2.7[771949]: starting TLS negotiation on data connection

I wonder if anyone can make a suggestion as to how I can get this to work?

David

2

Hi @Printdevil ,

That path field looks suspiciously empty. Are you absolutely sure you’re supposed to publish to root on that server?

If yes - check your speed settings. RapidWeaver opens a lot of connections at once to speed up publishing, but some hosters don’t allow that. Click on the Connections dropdown and select the lowest speed possible. Then try again and see if it works.

Cheers,
Erwin

3

Hi Erwin,

The publishing folder is definitely the root level as I can see that when I browse the server via the RapidWeaver publishing panel. Also I can login to the server through Transmit…

Endo-Transmit-Settings
Endo-Transmit-Settings1286×830 137 KB

I have just tried publishing again at Connection speed of 1 and that failed in the same way. I then added a /test folder on the server and that didn’t work either.

I am sure it has something to do with Explicit FPS and I think RapidWeaver struggles publishing to FTPES servers, if anyone has been able to get it working on FTPES servers I would love to know what the solution is.

David

4

OK, thanks for checking. It’s rare to see hosters setting up root for you to publish in, is all; that’s why I asked.

I completely missed that you’re trying to publish over FTPES in your original post.

I’m not entirely sure, but I don’t think RapidWeaver supports FTPES. It’s supports non-explicit FTPS though, as well as SFTP. This would explain why the handshake is reinitialised every few milliseconds.

@dang will know for sure if FTPES is supported or not.

Cheers,
Erwin