EE Push

Troubleshooting

Installation Issues

Add-on not appearing in the Control Panel

  • Ensure the ee_push folder is in system/user/addons/
  • Check that addon.setup.php exists in the folder
  • Clear EE's cache: Developer > Utilities > Cache Manager > Clear All
  • Verify file permissions — the folder should be readable by the web server

CSS/JS not loading

EE Push loads assets from the themes directory. Ensure the assets are copied or symlinked:

# Copy
cp -r system/user/addons/ee_push/assets/ themes/user/ee_push/

# Or symlink
ln -s ../../system/user/addons/ee_push/assets themes/user/ee_push

Deployment Issues

Pre-flight check: "Database connection failed"

This means EE Push couldn't verify the database connection. Check your EE database configuration in system/user/config/config.php.

Pre-flight check: "Insufficient disk space"

EE Push requires at least 100 MB of free disk space for backups. Free up space or change the backup path to a volume with more space.

Webhook returns 4xx/5xx

  • Verify the webhook URL is correct and accessible from your server
  • Check that any authentication headers are correct
  • Test the webhook URL with curl from your server
  • Check the deployment log for the exact HTTP status and response body

SSH: "phpseclib3 not found"

Install the SSH library:

composer require phpseclib/phpseclib:~3.0

SSH: "Authentication failed"

  • Verify the username is correct
  • For key auth: ensure the private key is in PEM format and the public key is in the remote server's ~/.ssh/authorized_keys
  • For password auth: verify the password is correct
  • Check that the server allows the authentication method (some servers disable password auth)

SSH: "Permission denied on git pull"

  • Ensure the SSH user owns or has write access to the remote path
  • Ensure the Git remote is configured with appropriate credentials (SSH key or token)
  • Try running the git commands manually as the same user

Plesk: "API returned 401/403"

  • Verify the API key is correct and hasn't been revoked
  • Check that the API key has permission for Git operations
  • Ensure the Plesk API URL includes the correct port (usually 8443)

Backup Issues

"mysqldump: command not found"

The mysqldump binary is not in the system path. Find its location and update the PATH or configure the full path.

# Find mysqldump
which mysqldump
# or
find / -name mysqldump 2>/dev/null

Backup file is empty or zero bytes

  • Check that the PHP process has permission to write to the backup directory
  • Verify database credentials in EE's config
  • Check server error logs for mysqldump output

Rollback Issues

Rollback button not appearing

Rollback requires:

  • Deployment status must be success or failed
  • A backup file must exist at the recorded path
  • The deployment must not have already been rolled back

Performance

Deployment progress not updating

The progress view polls the server every 2 seconds. If updates are slow, check:

  • Browser console for JavaScript errors
  • Server response time — slow servers may delay AJAX responses
  • PHP execution time limits — long deployments may hit the limit

Getting Help

If you're still stuck, check the full deployment log under Deployment Logsin the Control Panel. The log includes timestamps and error messages for every step of the deployment process.