Support

Akeeba Backup for Joomla!

#8515 [FIXED] Upload to remote FTP server - not working

Posted in ‘Akeeba Backup for Joomla!’
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

user12388
Hi,

I'm unable to get "Upload to remote FTP server" post processing option to work.
I tested this with 2 versions of Akeeba: 3.0 Pro release and svn174.
Test was run to two different hosts.
Two different FTP servers on two different hosts were tried. (Not on the Joomla hosts)
All test were tried with and without passive FTP option
In all cases the FTP connection test in the configuration page tested OK
Archive file size was 24KB - both zip and JPA were tried.
No files at all were transferred - not even a 0 size file.

Interesting to note that DirectFTP option (without post processing configured) also failed. This without an error message.

I have uploaded 2 log files. Log Files

Any suggestions?

user12388
I also tried to upload to rack cloud using the latest svn version and received the following error message:

Invalid AJAX data:
Fatal error: Call to undefined method AEUtilCfhttp::getCDNMUrl() in /home1/galwebor/public_html/gampie.net/administrator/components/com_akeeba/akeeba/plugins/utils/cloudfiles.php on line 1179

Log included here TEXT

Hope this helps.

dlb
This one needs to go to Nicholas. :) I'll flag it for his attention.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user12388
Whooops!! I got the upload to FTP server to work. It was a simple as inserting the missing slash before the remote directory name. :/ :/

Perhaps the preceding slash can be checked for and inserted if missing. This is important as the FTP connection check indicates success even without the slash (chdir).

However the rackcloud option is still not working (slash or no slash).

nicholas
Akeeba Staff
Manager
Thank you for your bug report! I didn't have the chance to test the CloudFiles integration, as there seems to be a problem with the cooperation of mine and RackSpace's banks which prevent me from being able to pay them for a subscription.

I fixed both reported bugs and just uploaded SVN181 developer's release. Please test it and report back any further issues. Thanks!

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!

user12388
SVN181 is giving an error during install.
Can you please check to see if its not only my problem.
As soon as 181 is up and running I'll give the upload to Rackspace a check.

Thanks,
David

nicholas
Akeeba Staff
Manager
Can you be more specific on the error you get? Maybe post a screenshot, if possible.

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!

user12388
The error message says:
--------------------------
-1 - An error has occurred.

It was not possible to copy the selected file.
-----------------------------
The install rolls back and the previous version is still working
here is a screencap

nicholas
Akeeba Staff
Manager
This is a Joomla! error, usually denoting problems with the path names. As far as I know, if you have certain special characters and whitespace in the absolute path to your site or temporary directory this message appears. The other possibility is a corrupt download. Joomla! doesn't do a very good job at letting you know what exactly happened. I'd suggest trying the "manual installation" procedure outlined in our documentation. If this still doesn't work, please let me know.

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!

user12388
Thank you for your bug report! I didn't have the chance to test the CloudFiles integration, as there seems to be a problem with the cooperation of mine and RackSpace's banks which prevent me from being able to pay them for a subscription.



I fixed both reported bugs and just uploaded SVN181 developer's release. Please test it and report back any further issues. Thanks!


Hi Nicholas,

I tested uploading to RackSpace using SVN183 and it works fine. It put the zipped archive (I tested db only) and a zipped log file in the cloud file storage. BTW, I'm not sure if the directory field is required as well as the container field. All containers only have roots with no directory structure.

Great stuff!! Keep up the good work.
David

nicholas
Akeeba Staff
Manager
Thank you! That's good to know, as it was a fly-by-night coding experience for me (no account to test with) :D

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!

user12388
Yiamas!

user18318
I hate to open this thread, but Rackspace is not working for me. Akeeba Backup Professional 3.1 (2010-09-19). I get an erro that states :container not found.

I've tried multiple containers that work via Cyber Duck FTP. No joy.

nicholas
Akeeba Staff
Manager
The only way to get that error is if the container doesn't really exist. Do note that container names are case-sensitive and they must start with a letter. These are the limitations of the PHP CloudFiles API that I am aware of. Unfortunately, I can not test CloudFiles myself because RackSpace claims that my bank rejects the transaction when I try to sign up with them and my bank claims RackSpace is the one who rejects the transaction. I suspect RackSpace is at fault, as I have successfully registered with all other cloud space providers without a problem. If you want, you can send me a PM with Super Admin access to your site and information on connecting to a CloudFiles account so that I can test the connection on your server.

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!

user18318
OK. Finally got it to work.

Some keys:

1. On Rackspace Could Files, make your container name a contiguous string, and use the name, NOT the container URL (which I wrongly assumed was the only way to find the container)

1. Make a container for your site backups, name it something like "Acme_Site_Backups"
2. Use this name in the Akeeba setup for Rackspace cloud container name
3. Get your key exactly correct - no spaces.

I recommend leaving the delete backup after post processing unchecked. You wind up with a backup on both your webserver and Rackspace clould.

It WOULD be COOL if you could do both Rackspace and another action (FTP / S3) for complete redundancy)

nicholas
Akeeba Staff
Manager
Ah! Spaces have to be URL-encoded as %20 to work. For example "Some Backup" should be written as "Some%20Backup".

Regarding multiple post-processing engines running at the same time, it is an interesting feature to implement in version 3.2 or 3.3, but I am not sure whether most users will find it usable enough. So, for now, you only get to choose a single post-processing engine :)

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!

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.