Support

Akeeba Backup for Joomla!

#39530 Internal server error 500 ( backup transfer from hostin to vps server )

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/a4.3.4 Stable
PHP version
n/a8.1.23
Akeeba Backup version
9.7.1

Latest post by tampe125 on Thursday, 28 September 2023 04:21 CDT

Marieke_dmn

ciao....

In breve gli steps seguiti fino ad ora .

1- creazione backup del sito mariekeboot.consulting ospitato su hosting ionos

2- trasferimento interno del dominio mariekeboot.consulting tra il servizio di hosting e quello di server virtuale VPS gestito da Plesk

3- creazione di un abbonamento plesk unlimited con associazione del dominio appena trasferito mariekeboot.consulting

4- copia delle impostazioni php del dominio di hosting nelle impostazioni personalizzate del dominio  comprese le direttive aggiuntive

5- test del domionio appena trasferito con una istallazione pulita j4.3.4 (ok)

6- controllo del file system di plesk per la presenza di eventuali arrori attraverso i tools di diagnostica integrata (Ok)

7- creazione in plesk  di un DB MariaDB 10.6.12 correlato al dominio mariekeboot.consulting 

8- primo tentativo di ripristino del backup akeeba sul dominio trasferito attraverso kickstart/angie ( processo eseguito senza errori lasciando il setting dei file di configurazione di joomla as "no change". Al termine della processo di istallazione clean up eseguito correttamente quindi  all' apertura del front-end ( int err 500)

8- ripeto il tentativo di ripristino cambiando solo setting dei file di configurazione di joomla as "predefinito" questa volta l'istallazione si interrome immediatamente  ( int err 500)

----------

*Qui trovi la copia funzionante sul servizio di hosting: https://mariekeboot.nl 

*i files di configurazione di J nella root del sito sembrano molto dirty probabilmente a causa delle riscritture automatizzate dei backups precedenti. Onestamente non mi sono mai azzardato a fare editing su questi files. se pensi che la loro consultazione possa esserti utile, te li mando 

*Lista direttive aggiuntive php
----------------------------------------
upload_tmp_dir = /httpdocs/tmp
upload_max_filesize = 32M
post_max_size =32M
memory_limit = 128M
max_execution_time = 60
display_errors = off
output_buffering = off
max_allowed_packet = 20

tampe125
Akeeba Staff

Salve,

di seguito riporto gli step per capire il motivo dell'errore 500:

A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP 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. 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 hosting control panel.

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 remove 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 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.

If that fails again, remove the php.ini file and create a file named .user.ini (note that it's dot user dot ini, the leading dot is important) with the contents:

display_errors=on
error_reporting=E_ALL

and upload it into your site's root and your site's administrator directory. Wait for 10 minutes. Waiting is important, .user.ini files do not apply immediately. 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 or .user.ini file your created and consult your host. They have to provide you the PHP error message, file and line it occurs (along with the error's backtrace) themselves.

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.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Marieke_dmn

Ciao..
Linea .htacces responsabile dell'errore:

Options +FollowSymlinks

Nei server gestiti da plesk è impostata per default quindi va disabilitata in .htaccess. Lo scrivono chiaramente nell' header

##
# The line 'Options +FollowSymLinks' may cause problems with some server configurations.
# It is required for the use of Apache mod_rewrite, but it may have already been set by
# your server administrator in a way that disallows changing it in this .htaccess file.
# If using it causes your site to produce an error, comment it out (add # to the
# beginning of the line), reload your site in your browser and test your sef urls. If
# they work, then it has been set by your server administrator and you do not need to
# set it here.
##

Grazie Davide per le tue fast reply e per il gentile supporto... buon lavoro

--
Nessuno sviluppatore è stato torturato per la chiusura di questo Ticket.
timezone and cultural differences were respected.
--

 

tampe125
Akeeba Staff

Ottimo! Grazie mille per il feedback!

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
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!