CodeGuard Cannot Connect via FTP

CodeGuard is a third-party website backup service that connects to your hosting account via FTP or SFTP to download and store copies of your files. If CodeGuard reports it can't connect, the issue is usually an incorrect hostname, blocked IP, or passive FTP port range problem. This guide covers the most common causes and fixes.

01. Correct FTP Settings

02. Firewall Blocks

CodeGuard connects from a range of IP addresses. If our server firewall (CSF) has blocked one of CodeGuard's IPs due to failed login attempts, the connection will fail.

Check if CodeGuard's IPs are blocked:

# Search the firewall deny list
csf -g [CodeGuard IP]

# Or search all deny lists
grep "CodeGuard_IP" /etc/csf/csf.deny

If blocked, unblock the IP and whitelist it:

csf -dr [CodeGuard IP]
csf -a [CodeGuard IP] "CodeGuard backup service"

You can also check for blocks using our firewall unblock guide. If you're not sure what IPs CodeGuard uses, contact their support for their current IP range.

03. Passive FTP Issues

FTP uses two connections: a control connection (port 21) and a data connection. In passive mode (which CodeGuard uses), the server tells the client to connect on a random high port. If the firewall isn't configured to allow the passive port range, the control connection succeeds but file transfers fail.

On Ultra Web Hosting servers, the passive FTP port range is configured in Pure-FTPd. Verify it's set and the firewall allows it:

# Check passive port range
cat /var/cpanel/conf/pureftpd/main | grep PassivePortRange

# Ensure CSF allows these ports (should be in TCP_IN)
grep "TCP_IN" /etc/csf/csf.conf | head -1

04. Using SFTP Instead

SFTP (SSH File Transfer Protocol) is more reliable than FTP for automated backup services because it uses a single connection on port 22, avoids passive mode complications, and encrypts all data in transit.

If CodeGuard supports SFTP (most plans do), switch to it:

1. Change protocol to SFTP in your CodeGuard site settings
2. Set port to 22
3. Use your cPanel credentials - Same username and password as FTP
4. Verify SSH access is enabled - In cPanel, check that "Shell Access" is enabled for your account. If it's not, contact support to enable it

For more on FTP vs SFTP, see our FTP guide and SSH access guide.

05. Troubleshooting

Connection timeout - Firewall is blocking the IP or the hostname doesn't resolve to the right server. Try using the direct server IP instead of the hostname.

Authentication failure - Wrong username or password. Reset your cPanel password and update it in CodeGuard. Make sure you're using the cPanel username, not an email address.

Directory listing fails - Connected but can't list files. Usually a passive FTP issue. Switch to SFTP.

Backup starts but fails partway - Large accounts may hit FTP timeout limits. Switch to SFTP which handles long transfers more reliably. Also check disk space on both sides.

Quick Recap: CodeGuard FTP Connection

1. Use the server hostname - Not your domain name, especially if using Cloudflare
2. Check firewall - Make sure CodeGuard's IPs aren't blocked by CSF
3. Switch to SFTP - More reliable, avoids passive FTP issues
4. Use cPanel credentials - The main account username and password
5. Consider JetBackup - Free daily backups are already included with your hosting

Last updated March 2026 · Browse all FTP articles