Akeeba Backup for Joomla!

#8707 After installing 3.1.3 it now crashes site "500 internal server error"

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 Tuesday, 16 November 2010 21:45 CST

Tuesday, 16 November 2010 14:12 CST

kkrie616

I have been using Akeeba back up for quite a sometime and never had any issue. I just installed the latest update 3.1.3 and now when I hit backup (backs up to dropbox) i see the progress, when its nearly finished the entire site front-end and backend get an internal 500 server error.

The only way to fix it is to open a ticket with the hosting company and have them reset the permissions to the website.

Any ideas???

Tuesday, 16 November 2010 16:32 CST

user11523

I am having this exact issue. It seems something in the process is setting the permissions for the public_html to 777. Luckily I have a VPS therefore have control over it where I do not have to open a ticket. Downgrading to 3.1 solved it in the short term.

This is the error I am getting (personal info removed).

[Tue Nov 16 22:52:29 2010] [error] [client IP_ADDRESS] SoftException in Application.cpp:610: Directory "/home/website/public_html" is writeable by others, referer: https://www.mywebsite.com/administrator/index.php?option=com_akeeba&view=backup

This is a serious issue.

Tuesday, 16 November 2010 21:45 CST

nicholas

Fixed in 3.1.4. Take a look at the release notes. It's a composite bug, caused by Akeeba Backup passing an empty filename to Joomla!'s JFile::delete() and that core Joomla! function a. not checking if the filename passed is really a file b. trying to chmod it to 0777 permissions and c. PHP assuming that an empty filename means "your web site's root". That's the butterfly effect in software bugs :s Sorry guys, I was hit by the same issue on our own site as the normal testing didn't catch that case.

Note: you have to upgrade to 3.1.4 manually, the live update seems to be broken. I am investigating this issue, but I published the 3.1.4 release anyway to avoid having your site's down when backing them up using post-processing.

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