Support

Akeeba Backup for Joomla!

#8472 can not perform auto upgrade for pro ver

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 nicholas on Monday, 26 July 2010 04:34 CDT

user6558
* SERVER_CONNECT_FAILED, failed to open stream: No such file or directory
* Could not download the update package. Make sure your server's firewall doesn't block the connection and that you have specified a valid username and password for the Professional edition.

my user name and password is correct.
should not be firewall issue as I can upgrade free ver.

dlb
I don't know what the problem might be. I will flag this for Nicholas.

You can manually download the latest version and install it as a normal component (don't uninstall the current version).


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)

nicholas
Akeeba Staff
Manager
Hm... I couldn't replicate this issue. Do note that the two releases (Core/Pro) use different distribution servers. The Core release is hosted on JoomlaCode.org whereas the Core release is hosted on AkeebaBackup.com. Also note that, due to some bugs, automatically upgrading from Akeeba Backup 3.0.b1 might not be possible. In this case the only workaround is to manually install the upgrade package. Beta 2 and RC 1 do not have this issue.

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!

user1176
I'll throw my hat in here... I also had this issue, but I was on rc1. I manually updated the component without a problem, but the automatic update failed with the same error as SKY described above.

nicholas
Akeeba Staff
Manager
Um... It worked on several sites I manage. Do you have any non-alphanumeric characters in your username and/or password? I need to be able to replicate this in order to resolve it :)

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!

user1176
The username and password contain only upper/lowercase letters and numbers.

I too manage several sites, and those work as expected. I'm not sure why this one is special :)

I'd be happy to give you admin privileges to the site if you want to poke around.

nicholas
Akeeba Staff
Manager
The only possibility left is something on our servers blocking their communication. First check that there is no firewall blocking the connection at your end. If there is, you'll have to open port 80 and 443 to akeebabackup.com. If you had done that previously you'll have to do that again, as our site's IP changed in early June due to the installation of our SSL certificate (we moved to a dedicated IP plan to support the certificate). If this doesn't help, just send me a PM with your site's URL and I'll ask our host if mod_security is blocking your site on our end.

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!

piggybank
I too started receiving this error. I manage several websites and all are behaving this way.

nicholas
Akeeba Staff
Manager
@piggybank Can you download the component manually from this site?

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!

piggybank
yes.

nicholas
Akeeba Staff
Manager
I just tested on 3 different servers. One live server in the US, one live server in the EU and a testing server in the office. All three could upgrade correctly, so it doesn't look like a problem on our server side.

If you are getting the exact error message as the original poster, you really have to talk to your host. Ask them to open connections to ports 80 and 443 to AkeebaBackup.com (IP address 72.249.175.22). If you had done that a few months ago, you'll have to do that again. About a month ago we installed an SSL certificate on the server. In order to do that we had to be assigned a dedicated IP address, which means that our domain (akeebabackup.com) remained the same, but the IP address it resolves to has changed. Since your host's firewall filters traffic based on IP addresses, you have to ask them to open connections to ports 80 and 443 (standard and SSL-encrypted HTTP traffic) to our new IP address.

This is exactly what I suggested in my June 24th reply right above your first post. Have you tried that?

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!

user8266
I get the same message
* SERVER_CONNECT_FAILED, failed to open stream: no suitable wrapper could be found
* Could not download the update package. Make sure your server's firewall doesn't block the connection and that you have specified a valid username and password for the Professional edition.

Username & password are OK. I get this on two separate servers that I manage & there is no problem with the firewall This update procedure did work OK with Joomlapack & as I recall used to work with Akeeba Backup.

I can download & install the upgrade manually but it's a shame not to have this cool feature working. This sort of automatic upgrade feature should be in every Joomla component (& should be fully working:-) I hate those components that insist on you uninstalling the old version before you install the new one. It's iobviously because they can't be bothered to code the installation procedure coirrectly. As far as I recall the only other component I use that does support in place upgrades is Joomla Content Editor (JCE).

Cheers

Nigel

nicholas
Akeeba Staff
Manager
This is a bit different message. "no suitable wrapper could be found" is a Joomla! error message which means that your server doesn't support the URL fopen wrappers. OK, this is the only verbatim block of Joomla! Framework API code I'm using and it has let hell break loose. Guess what? The next release will use custom code to work around this limitation in the Joomla! framework ;)

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!

user8266
Nicholas, Thanks for the very fast response. I guess that I didn't read the first post properly.

Now that you have explained the reason I think that it's probably because I have allow_url_fopen disabled as part of my lockdown of the more insecure parts of PHP

Cheers

Nigel

nicholas
Akeeba Staff
Manager
Exactly! The workaround I will be coding will try to fall back to cURL if fopen wrappers are not available. However, it will take a beta release to be rolled out to everyone.

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: 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!