Support

Akeeba Backup for Joomla!

#28841 500 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 TravisC on Friday, 08 December 2017 13:49 CST

TravisC
Hello-

When I visit my Akeeba backup extension (/administrator/index.php?option=com_akeeba) I get a hard 500 error. I am NOT using PHP 7. This is a development server, so I am not totally certain if it used to work and then stopped, or has never worked.

The specific error is:

"PHP Warning: syntax error, unexpected '~' in Unknown on line 1
in E:\sitename\administrator\components\com_akeeba\BackupEngine\Util\ParseIni.php on line 43
PHP Warning: Invalid argument supplied for foreach() in E:\sitename\administrator\components\com_akeeba\BackupEngine\Platform\Base.php on line 258
PHP Warning: syntax error, unexpected '~' in Unknown on line 1
in E:\sitename\administrator\components\com_akeeba\BackupEngine\Util\ParseIni.php on line 43
PHP Warning: Invalid argument supplied for foreach() in E:\sitename\administrator\components\com_akeeba\BackupEngine\Platform\Base.php on line 258
PHP Warning: syntax error, unexpected '~' in Unknown on line 1
in E:\sitename\administrator\components\com_akeeba\BackupEngine\Util\ParseIni.php on line 43
PHP Warning: Invalid argument supplied for foreach() in E:\sitename\administrator\components\com_akeeba\BackupEngine\Platform\Base.php on line 258"

Thnaks so much for looking!

nicholas
Akeeba Staff
Manager
These are warnings, not errors. None of them would result in the 500 Internal Server Error. A white page or a page with a 500 Internal Server Error is, in fact, a PHP fatal error in disguise.

First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Please note that we are looking for something marked as "Error", not "Warning", "Notice" or "Deprecated". Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Development. Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):
ini_set( 'display_errors', true );
error_reporting( E_ALL ); 
Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:
php_flag display_errors On
php_value error_reporting 32767
and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini (on some hosts you need to use .user.ini) with the following content:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

IMPORTANT: Sometimes the error won't show. Edit your configuration.php and find the line starting with public $error_reporting and set it to:
public $error_reporting = 'development';

This instructs Joomla! to enable maximum error, warnings and notices verbosity. In 99.9% of cases it will result in the error messages being shown on the browser.

If you still get a white page, delete the php.ini / .user.ini files your created and post back here. We'll have to go about it a different way.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

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!

TravisC
So, I ended up uninstalling and reinstalling, and now it works just fine. Thank you for your help and for your excellent product!

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!