Support

Site Restoration

#42970 Application Error when trying to restore (Akeeba WordPress)

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.2.31
CMS Type
WordPress
CMS Version
7.0
Backup Tool Version
9.1.3
Kickstart version
9.0.4

Latest post by nicholas on Monday, 25 May 2026 06:26 CDT

cirymarr

Hi

As a digital agency, we always use Akeeba Backup for backing up our core WordPress stack for new projects, and have never had problems up until today.

I have recently created a new backup (WordPress 7, PHP 8.2.31) - backup is fine.

Now, trying to restore the backup is where the problems start. As soon as the restoration script reaches "Run the Installer", I receive "Application Error" with the following:

RuntimeException — View Main does not exist

/home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Mvc/Factory.php::L179

#0 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Mvc/Controller.php(257): Akeeba\BRS\Framework\Mvc\Factory->view('Main', 'Raw', Array)
#1 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Mvc/Controller.php(208): Akeeba\BRS\Framework\Mvc\Controller->getThisView()
#2 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Mvc/Controller.php(224): Akeeba\BRS\Framework\Mvc\Controller->display()
#3 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Mvc/Controller.php(188): Akeeba\BRS\Framework\Mvc\Controller->main()
#4 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Dispatcher/Dispatcher.php(61): Akeeba\BRS\Framework\Mvc\Controller->execute('main')
#5 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/src/Framework/Application/AbstractApplication.php(82): Akeeba\BRS\Framework\Dispatcher\Dispatcher->dispatch()
#6 /home/customer/www/cmeonlinel175.sg-host.com/public_html/installation/index.php(103): Akeeba\BRS\Framework\Application\AbstractApplication->dispatch()
#7 {main}


Please note: SiteGround prompts for the kickstart.php plugin to be renamed so I rename it to webrestore.php (I've always done this).

This is very urgent, so a prompt response would be greatly appreciated.




nicholas
Akeeba Staff
Manager

I see something really odd in your screenshot. The header says it's version 7.1.4.2 from six years ago (released May 24th, 2020). The error message says it's version 9.1.3 from a month ago (released April 21st, 2026).

These are two completely separate generations of Akeeba Backup. It's not just being two major versions apart. The actual restoration script in each version is radically different than the other. Mixing their files would, indeed, break your site.

Delete the installation directory altogether.

Double check it's completely gone.

Now, extract the backup archive again with Kickstart.

Does that solve your 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!

cirymarr

Hi

I tried that to no avail - same issue.

 

So, I have returned to my source website to be backed up. I have removed previous install of Akeeba and have installed Akeeba Backup 9.1.3 core (no need or requirements for us to use the pro version for this task).

 

To restore from a v9.1.3 backup, do I need to use the kiockstart pro V 9.0.4 version?  Please advise.

 

Hoping this should solve my issue...

cirymarr

I'm now about to restore the backup.  I'm receiving the following:

 

Suboptimal PHP OPcache settings detected

Your server's PHP OPcache configuration may cause Kickstart to fail with an HTTP 500 error. Please ask your host to apply the following settings in your server's PHP configuration and restart PHP:

  • opcache.revalidate_path=1

 

I have submitted a support ticket to SiteGround asking them if they can oblige. I've never had this before.  Screenshot attached.

nicholas
Akeeba Staff
Manager
Kickstart is NOT a restoration script

Kickstart is the backup archive extraction tool. It only extracts the backup archive. It has nothing to do with the database restoration and the site reconfiguration. That is handled by BRS, the restoration script which was included in your backup archive at backup time.

This information is printed on your screen every time you run Kickstart, explained in our video tutorials, and included in several documentation pages.

Therefore, which version of Kickstart you use is irrelevant.

I am really confused by your saying that taking a new backup with Akeeba Backup 9.1.3 somehow ends up using an ancient version of the restoration scrip from 6 years ago. It makes zero sense.

I assume you did not install Akeeba Backup 9.1.3 from scratch and you didn't follow the upgrade instructions to Akeeba Backup 8.1 from 3 years ago either, simply uploading files into wp-content/plugins/akeebabackupwp? You could have ended up with a mix of two versions of Akeeba Backup which would explain why your restoration script is completely broken. Completely uninstalling and reinstalling Akeeba Backup would be the only way to fix the problem with taking backups.

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!

cirymarr

Hi

It appears the original issue was a caching issue at SiteGround Server level, and using "Ultrafast PHP" during restore. SiteGround support recommended I use "Managed PHP" until restoration is complete.

 

I did the above, and restoration worked perfectly.

 

You may close the ticket. Many thanks for your assistance.

nicholas
Akeeba Staff
Manager

Ah, that does make perfect sense! You had restored an older backup taken with Akeeba Backup 7 and they cached parts of the HTML output of that page. Since the old restoration script was making a request with format=raw which the new restoration script doesn't support you got an error – and a confusing mix of displayed version numbers.

I honestly thought that in the 5+ years I haven't used SiteGround they must have surely addressed this configuration issue with whatever they call these days their aggressive OPcache + Varnish option. I guess I was wrong on that front.

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!