I have just updated my Mac Studio to the latest Sequoia 15.2, and now RapidWeaver Classic cannot connect to the local FTP server. If I manually use FTP from a shell session, it works fine. I have changed nothing in the publishing configuration, and nothing has been changed on the FTP/Web server (on my local subnet inside the firewall). The server has lots of unused disk space. The pure-ftpd log file on the FTP server shows no attempt by RapidWeaver to connect, but manual connection from a shell session leaves the expected entries in the log. File puts and gets work ok in shell sessions.
I have tried all modes of connect (passive/active/sftp/ftps/ftp) but nothing works … it immediately returns a “Couldn’t sign in to your FTP server” error popup. Permissions on the FTP server are all correct. Username and password have not changed on the server.
Is there a setting on macOS that is blocking RapidWeaver from using FTP? The Mac firewall shows RapidWeaver is enabled for incoming connections, and turning the firewall off doesn’t help.
The web server and the FTP server are the same machine, of course. It’s firewall and pure-ftpd server configs have not been changed for years.
I guess I could reinstall Classic if there is a need to link to a different FTP library, but will wait to hear from the Forum.
This is a real mystery, and I tend to point the finger at something on the Mac since the FTP log file shows only manual shell session connects.
Your advice is most welcome, with my thanks.