Troubleshooting FTP for NVRs

Published {$created} by Carsten Blum

Connecting Network Video Recorders (NVRs) to cloud storage for video backups is a crucial part of a robust surveillance system. However, various issues can arise. This guide addresses common problems encountered when using cloud FTP for NVR backups, focusing on practical solutions. We're assuming you're using an FTP, SFTP, or SCP connection as configured within your NVR's settings.

Connection and Authentication Errors

The most frequent problems involve establishing a reliable connection. Let's examine causes and fixes:

• Incorrect Hostname or IP Address: Double-check the hostname (edgeN.ftpgrid.com) entered into your NVR's configuration. A typo is surprisingly common. Confirm that your NVR can resolve this hostname via DNS.
• Firewall Issues: Firewalls, both on your network and potentially on your NVR itself, can block outgoing FTP or SFTP connections. Ensure that ports 21 (FTP), 22 (SFTP), or custom ports (if you’re using non-standard ports) are open. Consider temporarily disabling firewalls for testing purposes – but remember to re-enable them and configure appropriate rules afterward.
• Authentication Failures: This often means username or password errors. If using password authentication (strongly discouraged – see FTP 101: Authentication is unsecure), verify the credentials carefully. Transitioning to SSH key-based authentication (as described in Advanced SSH Key Authentication for SFTP) is considerably more secure and eliminates many password-related issues.
• SFTP Key Issues: When using SFTP and SSH keys, ensure the public key is correctly uploaded to your ftpGrid account. Pay close attention to permissions – keys often need to be in a specific format. The Create SSH keys for SFTP, SCP authentication tutorial is invaluable here.
• Passive vs. Active FTP: Many NVRs default to active FTP, which requires incoming connections. This can be problematic if your NVR is behind a NAT (Network Address Translation) device. Try switching to passive FTP mode within your NVR’s settings. Check our guide FTP 101: Active vs. Passive Connections for more information.
• Unsupported Protocol: Older NVR models may only support plain FTP, which is inherently insecure. Consider upgrading your NVR or using an SFTP client as an intermediary if direct SFTP is not an option, which is covered in FTP 101: FTP vs. FTPS vs. SFTP.

Transfer and Storage Problems

Successfully connecting is only half the battle; data must also transfer reliably and be stored correctly.

• Insufficient Storage Space: NVRs generate substantial amounts of video data. Regularly monitor your storage quota through the Dashboard and adjust it as needed. See Quick Storage API series: SFTP/FTP for automating checks.
• Transfer Speed Limitations: Network bandwidth, both at the NVR and at your internet connection, can throttle transfers. Test transfer speeds using tools like iperf. Consider upgrading your internet plan or optimizing your network configuration.
• File Corruption: Network instability or software bugs can sometimes corrupt files during transfer. Implement checksum verification to detect and re-attempt failed transfers.
• File Naming Conflicts: If your NVR doesn't generate unique filenames, you may encounter file overwriting issues. Configure your NVR to use timestamps or other unique identifiers in filenames.
• Unexpectedly large storage usage: While rare, disk usage can sometimes balloon unexpectedly. Monitor your historical storage usage via the Dashboard and investigate any anomalies.

For more information, see our guide on Migrate self-hosted FTP to managed FTP hosting and FTP 101: Rename and Remove in FTP.