Updated: 22 October 2026 · Applies to: General
Note: If you are forcing TLS, then make sure that you have already configured your PassivePortRange inside the /etc/pure-ftpd.conf file and also allowed the ports to be open on your firewall. Here is another post giving some details on how to do that.
STEP 1: Open up the FTP config file.
picop/etc/pure-ftpd.conf
STEP 2: Add your server IP to the ForcePassiveIP setting. This will be the main Public IP of your server.
PowerShell # Force an IP address in PASV/EPSV/SPSV replies. - for NAT. # Symbolic host names are also accepted for gateways with dynamic IP # addresses. # ForcePassiveIP 129.18.50.13 ForcePassiveIP <your_public_facing_server_ip_here> 1 2 3 4 5 6 # Force an IP address in PASV/EPSV/SPSV replies. - for NAT. # Symbolic host names are also accepted for gateways with dynamic IP # addresses. # ForcePassiveIP 129.18.50.13 ForcePassiveIP <your_public_facing_server_ip_here>
STEP 3: Restart FTP server
//usr/local/cpanel/scripts/restartsrv pureftpd
After that, TLS on Dreamweaver was working perfectly.
For any support, visit hire our experts.
This fix is specific to Dreamweaver using explicit FTPES (FTP over TLS); a different FTP client reporting a similar certificate or connection error on the same server may need a different adjustment, since not every client validates the certificate the same way.
Dreamweaver is not the only client that can show this kind of certificate complaint on a misconfigured FTPES setup, so if a different tool later shows a similar warning on the same server, revisit this same certificate chain before assuming it is a new, unrelated problem.
