Weebly FTP Not using TLS1.2 or FTPS

[KDMantra]

Hello,

We're currently using the Weebly WHMCS module through MarketingConnect to provide Weebly as a service for our client's sites.

Weebly correctly creates the FTP information on our cPanel backend server, and even properly attempts to publish. However, because we enforce TLS1.2 and FTPS for all FTP uploads, we receive the following error:

Dec 30 01:13:52 pure-ftpd: [INFO] New connection from xx.xx.xx.xx
Dec 30 01:13:53 pure-ftpd: [WARNING] Sorry, cleartext sessions and weak ciphers are not accepted on this server.#012Please reconnect using TLS security mechanisms.

Is there any way to modify the ciphers this Weebly addon uses? Is our case standard, or is this unexpected behavior for Weebly?

Thanks!

[webnb]

On 30/12/2021 at 7:19 PM, KDMantra said:

Hello,

We're currently using the Weebly WHMCS module through MarketingConnect to provide Weebly as a service for our client's sites.

Weebly correctly creates the FTP information on our cPanel backend server, and even properly attempts to publish. However, because we enforce TLS1.2 and FTPS for all FTP uploads, we receive the following error:

Dec 30 01:13:52 pure-ftpd: [INFO] New connection from xx.xx.xx.xx
Dec 30 01:13:53 pure-ftpd: [WARNING] Sorry, cleartext sessions and weak ciphers are not accepted on this server.#012Please reconnect using TLS security mechanisms.

Is there any way to modify the ciphers this Weebly addon uses? Is our case standard, or is this unexpected behavior for Weebly?

Thanks!

Discovered this recently.  It's expected behaviour.  From the WHMCS KB article:

NOTE: Publishing only supports plain FTP. If your server requires FTP/TLS or SFTP, this requirement will need to be removed.

This is not ideal: it essentially involves reducing the security on the hosting server.

Surprised that such a well-known tool as Weebly can't publish over FTPS.  I imagine that's who you'd need to raise it with, rather than WHMCS.

 

 

[RadWebHosting]

On 3/14/2022 at 7:26 AM, webnb said:

Discovered this recently.  It's expected behaviour.  From the WHMCS KB article:

NOTE: Publishing only supports plain FTP. If your server requires FTP/TLS or SFTP, this requirement will need to be removed.

This is not ideal: it essentially involves reducing the security on the hosting server.

Surprised that such a well-known tool as Weebly can't publish over FTPS.  I imagine that's who you'd need to raise it with, rather than WHMCS.

 

 

With all that data shifting servers, how does anyone maintain any semblance of GDPR compliance?