Akeeba Backup for Joomla!

Friday, 26 March 2010 15:14 CDT

user9417

Fatal error: Using $this when not in object context in /home/stjamesa/public_html/administrator/components/com_akeeba/akeeba/plugins/utils/amazons3.php on line 168

New to both Amazon S3 & Akeeba so probably just a formatting error but don't know enough to know what I'm doing wrong - can't find any reference in the forums or how to's for this error message. Back up works fine when not using S3.

Pat

Saturday, 27 March 2010 10:20 CDT

dlb

Pat,

There hasn't been much forum traffic on the s3 backup. Please zip and post your backup log, Nicholas will have to look at this. I'll flag this for him when we get all the puzzle pieces together. :)

Dale L. Brackin
Support Specialist

English: 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)

Saturday, 27 March 2010 14:39 CDT

user9417

TEXT
Have tried several different ways to specify the bucket & directory name. Not sure if any of them is correct. got different errors at different times but are successful when baking up to the server rather than S3

I think the zip attachment worked (long day)

Saturday, 27 March 2010 15:54 CDT

dlb

It worked. :) I'll flag this for Nicholas.

Dale L. Brackin
Support Specialist

English: 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)

Sunday, 28 March 2010 11:28 CDT

nicholas

First, please use the latest developer's release which works around this issue. It only happens when Akeeba Backup is unable to connect to S3. 3.0.a5.1 throws a PHP error instead of simply reporting that connection to S3 was impossible.

The other thing you have to take care of is your host's firewall. Many hosts restrict outbound connections. You have to ask your host to enable your access to the s3.amazonaws.com domain for the backup to S3 to work properly. I guess this is the real problem you have.

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!

Sunday, 28 March 2010 22:56 CDT

user8463

When I tried to backup my site I 've received a message:
Akeeba Backup may not work as expected

Akeeba Backup detected the following potential problems:

* Default output directory in use
Is there anything wrong or I can continue with procedure?
Thank you

Sunday, 28 March 2010 23:01 CDT

user8463

When I extracted kickstart-2.4.1.zip there appeared 7 .ini files except for the kickstart.php. Is necessary to upload all .ini files together with the kickstart.php?
Thank you

Monday, 29 March 2010 00:12 CDT

nicholas

The warning message is a link. Clicking on it redirects you to a page full of info which answers your question ;)

Regarding the INI files, they are translations. You don't need to upload them if you can stand Kickstart's interface appearing in English.

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!

Monday, 29 March 2010 00:23 CDT

user8463

Thank you very much

Monday, 29 March 2010 12:54 CDT

user9417

We are asking our host to enable access to S3. They write

[indent]We can open up the firewall to allow the connection through. We will need to know the IP address and port. Once we have that information, we can whitelist the outbound connection. [/indent]

We looked for this at Amazon but had no joy. Can you help?

Monday, 29 March 2010 13:13 CDT

user9417

Tried back up with latest developer release. Appeared to loop - attaching log file.

Monday, 29 March 2010 18:56 CDT

user9417

Yes. We got it working! The key was getting our host to whitelist S3. This is the info they used

[indent]http://developer.amazonwebservices.com/connect/thread.jspa?messageID=87807#87807 part of this follows

There is also a CIDR address which the firewall guys might want instead:
"CIDR: 72.21.192.0/19"

Some other random info:
s3.amazonaws.com is a CNAME for s3-1.amazonaws.com and I think s3-2.amazonaws.com. Nothing above s3-2 resolves for me.

The two ranges of IPs I see assigned for these are:
72.21.192.0 - 72.21.223.255
207.171.160.0 - 207.171.191.255 [/indent]

They used ports 32004 and 32007

Thanks!

Support