Support

Akeeba Backup for Joomla!

#36624 Could not connect to the remote FTP server.

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Thursday, 17 March 2022 20:17 CDT

aguenther

We have replaced our internal web servers with a new one. The web server is managed via ISPConfig.

So far everything runs as it should, only Akeeba Backup Site Transfer Wizard does not want. It always comes the message "Could not connect to the remote FTP server." Although everything is set correctly.

As for network and firewall, everything is configured accordingly. Is there a more detailed log from Akeeba than just the short error message? Thank you.

Andreas

nicholas
Akeeba Staff
Manager

Unfortunately PHP does not provide more details than what we convey back to you. It returns a boolean (true / false) indicating if the connection is successful. In case of an error it does not provide any information as to why the connection failed.

If you are using plain FTP (not SFTP or FTPS) the things you need to check are the hostname, port, username, password and initial directory.

You also need to check if your origin server is filtering out FTP traffic.

Further to that, on the target server you need to make sure that the connection is not blocked by the firewall (IPtables) rules, the FTP server is indeed running and accepting connections, the port matches what you gave Akeeba Backup and the username and password do have permissions.

Here's how I would approach it.

First, try using the same hostname, port, username and password in Cyberduck to ensure that I can, in fact, connect to the FTP server. If that fails the problem is in the target server.

If it connects, I'd check the initial directory. It's been a LONG time since I last used ISPconfig but IIRC it uses vsftpd with chroot-jailed users to their home folders so the initial directory should be / (a single forward slash). If it uses an FTP service without chroot-jailing you'd need to use a full filesystem patch such as /home/myuser

At this point I'd check the FTP logs on the target server. If it shows no traffic I'd be wondering if the source server can connect to any FTP server. So I'd try to use FTP credentials to a known good server in Akeeba Backup and see if the connection is successful. If it's successful the problem is on your target FTP server (firewall issue).

Once we have established that a connection can be made and the hostname, port, username, password and initial directory are correct I'd look into whether it's possible to upload anything with that connection. If not, it's a target FTP server configuration issue, probably wrong permissions or having set up the FTP server in read-only mode.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!