Support

Site Restoration

#43514 Difficulty by transfering to another webserver

Posted in ‘Site restoration’
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

PHP version
8.4.27
CMS Type
Joomla!
CMS Version
6.2.0
Backup Tool Version
10.5.0
Kickstart version
9.2.0

Latest post by moira on Monday, 16 November 2026 10:29 CST

WSchwaiger

Hi, I'm having a problem with a site restore.

This is my first time trying to restore a website to a different web server, and unfortunately, it keeps failing. The restoration runs normally without any error messages, but as soon as I go into the backend, there are all these Joomla error messages that weren’t there before.

Also, I can’t perform an update or repair the core files because I always get a server error.

 

Have you had experience with problems like this, and how can I fix them?

Thank you!

moira

Thank you for the details. Unfortunately, “Joomla error messages in the backend” and “a server error” are not enough for us to tell what is going wrong on the new server, so we need to see the actual error messages. By default, Joomla hides the technical details. Here is how to make it show them:

  1. Connect to your new server with FTP / SFTP, or use the File Manager in your hosting control panel.
  2. Download or open the configuration.php file in the root of your site.
  3. Find the line public $debug = false; and change it to public $debug = true;. If you also have a line public $error_reporting = 'default'; (or 'none'), change it to public $error_reporting = 'maximum';.
  4. Save the file (upload it back if you downloaded it), then reload the page that shows the errors in the backend.
  5. Please reply to this ticket with the complete text of the messages and, if Joomla displays one, the full error trace (the “Call stack” / backtrace). A screenshot is fine if you cannot copy the text. Please do the same for the server error you get when you try to update Joomla or run the core files repair: tell us the exact text of the error, and which page / button triggers it.
  6. Once you have sent us this information, set both lines back to their previous values ($debug = false; and your original error_reporting) so your site does not display technical details to visitors.

If the server error is a generic “500 Internal Server Error” page without any details, your host’s PHP error log will usually have the real message. In this case please also send us the last few lines of the error_log file (or the PHP error log your hosting control panel offers) from the time you triggered the error. Joomla’s own log files in the administrator/logs folder of your site may also contain useful information; please attach any recent files you find there.

When moving a site to a different server, the most common causes of problems like these are that the new server runs a PHP version that is not compatible with your site or its extensions, or that a PHP extension which your site needs is not enabled on the new server. This is only our best guess. We cannot be certain until we see the actual messages, so please do not change any server settings before we have had a look at them.

Moira Fari

Support Specialist

🇬🇧English: native 🕐 My time zone is Asia / Nicosia
Kindly note that my replies are fully vetted by our developers.

WSchwaiger

Hello there,

thank you for your response.

I have now tried to restore the same Site to a new domain on the same Webserver, but it is still not working.
What i have also tried is to take a new backup and restore it or to use kickstart pro to restore the site but neither was successfull.
I have now attached you the error messages of the restored backend of joomla end the Error Message when i try to update or in that case reinstall the core files of joomla. Unfortunatly there ain't much info what that error actually means.

For futher clarification, i have also uploaded a picture of the working frontend and one of the frontend after the restoration which is not working correctly (Many buttons have no function no longer / some of the icons are not displayed anymore)

Thank you for your help!

Best Regards!

WSchwaiger

Now the error log is also atteched.

moira

Thank you, the screenshots and the log helped. We believe the cause is the Live Site setting in your restored site's configuration.php and not your PHP version or a missing PHP extension. We cannot be 100% certain, but the symptoms fit it exactly, and the fix is quick and harmless to try.

What to do

  1. Connect to your server with FTP / SFTP, or use the File Manager in your hosting control panel.
  2. Open the configuration.php file in the root of the restored site.
  3. Find the line starting with public $live_site =. If it has a URL between the quotes, remove it so that it reads exactly:
    public $live_site = '';
  4. Save the file (upload it back if you downloaded it).
  5. Clear your browser's cache (or open the site in a private / incognito window), log into the backend again, and check the Joomla Update page and the frontend.

If you prefer to do it during a restoration, the same setting is the Live Site field on the Site Setup page of the restoration script. Leave it empty.

If anything still does not work after this, please tell us exactly what you see (a screenshot is fine) and we will take it from there.

If you enabled debug mode in configuration.php while following our earlier instructions, please set public $debug = false; again once everything works.

Moira Fari

Support Specialist

🇬🇧English: native 🕐 My time zone is Asia / Nicosia
Kindly note that my replies are fully vetted by our developers.

WSchwaiger

Hello again,

thank you very much this has fixed the problem.
Should I leave this field empty in every restoration from now on?

moira

We are glad to hear it is working now.

Yes, please leave the Live Site field empty in every restoration, and keep the public $live_site = ''; line in configuration.php empty as well. Joomla works out the correct address of your site by itself. A filled-in value that is not exactly the address you use to open the site (for example http:// instead of https://, www. instead of no www., or your old domain name) breaks the site in the way you saw.

Moira Fari

Support Specialist

🇬🇧English: native 🕐 My time zone is Asia / Nicosia
Kindly note that my replies are fully vetted by our developers.

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!