Support

Akeeba Backup for Joomla!

#24670 FTP upload fails but no error given

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 Saturday, 07 May 2016 17:20 CDT

yetopen
Hi.
We purchased PRO to have FTP upload of several websites.
For some, hosted at netsons.com, the configuration and upload went fine. For others, hosted at aruba.it, we cannot manage FTP upload to work. The connection test is successful, but the upload fails. Sadly even with debug logging, no reason is given for the failed transfer.
We tried disabling passive FTP but same result. And even splitting file size to 10M doesn't change a bit, the upload always fails.

How can we figure out what's wrong?
thanks

[160314 11:55:44] ====== Starting Step number 25 ======
[160314 11:55:44] Kettenrad :: Ticking the domain object
[160314 11:55:44] Akeeba\Engine\Core\Domain\Finalization::_run() Running built-in method run_post_processing
[160314 11:55:44] Loading post-processing engine object (ftp)
[160314 11:55:44] Beginning post processing file <root>/administrator/components/com_akeeba/backup/site-www.domain.it-20160314-115411.jpa
[160314 11:55:44] Akeeba\Engine\Postproc\Ftp:: Connecting to remote FTP
[160314 11:55:44] Akeeba\Engine\Postproc\Ftp:: Starting FTP upload of <root>/administrator/components/com_akeeba/backup/site-www.domain.it-20160314-115411.jpa
[160314 11:55:54] Failed to process file <root>/administrator/components/com_akeeba/backup/site-www.domain.it-20160314-115411.jpa
[160314 11:55:54] Error received from the post-processing engine:
[160314 11:55:54] Uploading <root>/administrator/components/com_akeeba/backup/site-www.domain.it-20160314-115411.jpa has failed.
[160314 11:55:54] Not removing processed file <root>/administrator/components/com_akeeba/backup/site-www.domain.it-20160314-115411.jpa
[160314 11:55:54] Akeeba\Engine\Core\Domain\Finalization::_run() Running built-in method kickstart_post_processing

tampe125
Akeeba Staff
Buongiorno Riccardo,

potrebbe allegare il file di log di un backup non correttamente trasferito?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yetopen
Ho incollato nel ticket la parte relativa all'upload. Il resto del backup funziona, i file vengono generati in locale sul sito, ma non vengono trasferiti.

tampe125
Akeeba Staff
E' necessario allegare tutto il file, non solo le ultime righe, perchè sono presenti informazioni aggiuntive che aiutano a contestualizzare il problema.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yetopen
Eccolo

yetopen
ri-ecco

tampe125
Akeeba Staff
Può provare a diminuire ulteriormente la part-size a 5Mb?
Ha provato ad utilizzare un altro motore di upload (per eempio Dropbox)? L'errore si verifica lo stesso?
L'errore si verifica dopo appena 10 secondi, ho paura che le connessioni in uscita siano bloccate, specialmente per quanto riguarda l'FTP

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yetopen
anche abbassando a 5M l'errore rimane. su Dropbox l'upload è andato a buon fine.

tampe125
Akeeba Staff
Dal momento che su altri siti di altri hosting l'upload tramite FTP funziona, ho paura che il problema sia dovuto dall'hosting.
Potrebbe chiedere all'assistenza di Aruba di controllare se le funzioni FTP di PHP sono abilitate, così come le connessioni FTP in uscita?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

yetopen
Sto facendo un po' di debug con Aruba, ma non so se sia effettivamente lato loro il problema.
Facendo FTP da Aruba verso il sito stesso l'upload va ovviamente a buon fine. Facendo l'upload verso il nostro sito esterno, con la dimensione file ridottissima, alcuni vanno (pochi) ed altri no (la maggior parte). Ho messo il server di FTP in debug e questo è l'output.

File trasferito:
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [INFO] New connection from 62.149.143.144
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [user] [yetopenesteticaviva.it]
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [pass] [&lt;*&gt;]
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [INFO] yetopenesteticaviva.it is now logged in
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [cwd] [/]
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [type] [I]
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [port] [62,149,143,144,188,54]
Apr 7 15:25:59 demo pure-ftpd: ([email protected]) [DEBUG] Command [stor] [/site-www.esteticaviva.it-20160407-145446.j55]
Apr 7 15:26:01 demo pure-ftpd: ([email protected]) [NOTICE] /backup-dati/siti_akeeba/esteticaviva.it//site-www.esteticaviva.
it-20160407-145446.j55 uploaded (5242880 bytes, 2585.56KB/sec)
Apr 7 15:26:01 demo pure-ftpd: ([email protected]) [DEBUG] Command [quit] []
Apr 7 15:26:01 demo pure-ftpd: ([email protected]) [INFO] Logout.

File NON trasferito:
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [INFO] New connection from 62.149.143.144
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [user] [yetopenesteticaviva.it]
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [pass] [&lt;*&gt;]
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [INFO] yetopenesteticaviva.it is now logged in
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [cwd] [/]
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [type] [I]
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [port] [62,149,143,144,179,126]
Apr 7 15:26:06 demo pure-ftpd: ([email protected]) [DEBUG] Command [stor] [/site-www.esteticaviva.it-20160407-145446.j56]
Apr 7 15:26:12 demo pure-ftpd: ([email protected]) [DEBUG] Command [quit] []
Apr 7 15:26:12 demo pure-ftpd: ([email protected]) [INFO] Logout.

Purtroppo lato server vedo solo che viene richiesto l'upload (stor) ma poi non va avanti. Il server FTP ha delle restrizioni sulle porte passive utilizzabili, potrebbe creare qualche problema ad Akeeba? Con altri siti che usano lo stesso FTP e la stessa versione di Akeeba però non ho problemi.

E' possibile abilitare il debug dell'ftp su akeeba?

tampe125
Akeeba Staff
Se non ricordo male Aruba richiede un tipo di connessione attiva.
A seconda delle impostazioni, credo che non sia possibile effettuare il collegamento fra i due server, perchè alcune porte potrebbero essere bloccate.
La connessione FTP all'interno di Akeeba avviene direttamente a livello di PHP, per cui non è possibile abilitare il debug.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
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!