Back to Community

Troubleshooting Common WPvivid FTP and SFTP Remote Storage Connection Issues

15 threads Sep 9, 2025

Content

Connecting your WordPress site to a remote FTP or SFTP server for backups is a core feature of the 'Migration, Backup, Staging – WPvivid Backup & Migration' plugin. However, users often encounter frustrating errors that prevent successful setup. Based on common community reports, this guide will help you diagnose and resolve the most frequent connection problems.

Common Error Messages and Their Meanings

When adding remote storage, you might see one of these errors:

  • "Failed to add FTP storage. It can be because the FTP folder permissions are insufficient, or calling PHP ftp_put function of your web server failed."
  • "Login failed. You have entered the incorrect credential(s). Please try again." (for SFTP)
  • "The connection failed because of incorrect credentials or server connection timeout."
  • The 'Test and Add' button does nothing when clicked.

Why These Connection Issues Happen

These errors rarely mean your credentials are simply wrong. They typically point to a deeper technical conflict between your web server's configuration, the remote server's security settings, and how the plugin initiates the connection. Common root causes include:

  • Incorrect directory path or insufficient write permissions on the remote server.
  • A missing or disabled PHP function (like ftp_put) on your web server.
  • The remote server's firewall blocking connection attempts from your web host.
  • A plugin conflict, most notably with MainWP, which can make the connection button unresponsive.
  • A change in the PHP version on your server that affects the plugin's connection library.
  • The remote server requiring SSH key authentication, which the plugin does not currently support.

Step-by-Step Troubleshooting Guide

Follow these steps to identify and fix the problem.

1. Verify Basic Settings and Permissions

  • Double-Check Credentials: Ensure the host, username, password, and port are correct. For the path, use an absolute path (e.g., /home/username/backups/).
  • Confirm Directory Exists and Has Write Permissions: Using an FTP client like FileZilla, log in and verify that the target folder exists and that the user account has full read/write/create permissions for that directory.
  • Check for Non-Standard Ports or Special Characters: If your server uses a port other than 21 (FTP) or 22 (SFTP), specify it. Avoid spaces in folder names if possible.

2. Investigate Server-Side Issues

  • Check PHP Functions: Contact your web host to confirm that the PHP ftp_* functions (for FTP) or the SSH2 extension (for SFTP) are installed and enabled on your server.
  • Check Firewall Rules: The error might be that your web host's firewall is blocking outbound connections to your SFTP/FTP port, or your remote server's firewall is blocking inbound connections from your web host's IP address. You may need to whitelist the IP.
  • Test with Different PHP Versions: Some users have reported that connections fail on PHP 8.2 but work on PHP 7.4. If possible, test after temporarily switching your site's PHP version.

3. Check for Conflicts and Use Browser Tools

  • Plugin Conflict Test: Deactivate all other plugins, especially MainWP, and try to add the storage again. If it works, reactivate plugins one-by-one to find the culprit.
  • Use Browser Developer Tools: If the 'Test and Add' button does nothing, press F12 to open your browser's developer tools, go to the 'Console' tab, and then click the button. Any JavaScript errors that appear here can provide a crucial clue.

4. Understand Plugin Limitations

  • SSH Key Authentication Not Supported: The plugin currently only supports password authentication for SFTP connections. If your server has password login disabled and requires SSH keys, you will not be able to use SFTP with WPvivid and must use a different remote storage option or enable password auth.
  • Connection Timeouts on Large Backups: For very large sites, uploads can sometimes fail mid-transfer due to server timeouts or script execution limits. This may require adjustments on your server.

When All Else Fails

If you have worked through all these steps and the issue persists, the problem may be highly specific to your server environment. The best course of action is to gather detailed information, including:

  • Full error logs from the plugin.
  • Any errors from your browser's console (F12).
  • Your PHP version and server environment details.

This information is essential for further investigation into configuration-specific conflicts.

Related Support Threads Support