Issue Error opening Extensions

[ismaeldc]

Hi,
I encountered a similar error when trying to access the page for any of my extensions : ERROR: Declaration of DI\CompiledContainer::get($name) must be compatible with DI\Container::get(string $id): mixed (CompiledContainer.php:41)

I solved it by disabling then updating the Node.js extension - Toolkit
Here are the commands I used as root:
* extenions page test: OK
My other extensions, including Grafana mentioned above, do not cause this error.

Perfect!!! The problem nodejs. Thanks.

 

[hayridumanli]

In my case, Node.js was never installed, I don't use it. But for control, I installed it ("Phusion Passenger server" was also installed), it took a little bit long to be installed. Of course the error issue was not solved.

Then I uninstalled "NodeJS support" and "Phusion Passenger server", but still the same, when I click Extensions, Mail Queue, Monitoring, etc., it's still error;
ERROR: Declaration of DI\Definition\Source\DefinitionFile::getDefinition(string $name) must be compatible with DI\Definition\Source\DefinitionArray::getDefinition(string $name): ?DI\Definition\Definition (DefinitionFile.php:36)

And I never installed Grafana, too. So, error is going on and I'm getting more nervous. Because I tried add a domain, it's added, but I couldn't install Let's Encrypt, still error. The VPS is dying

 

[hayridumanli]

I enabled Debug mode in Plesk. I made "/var/log/plesk/panel.log" empty (true > panel.log). Then I clicked Extensions, same error. But panel.log file have hundreds of lines in a second, it's impossible to find the error message.

 

[Taliaonii]

I have the exact same problem and don't know what to do about it

 

[mizar]

Hi!

This error can be caused non-update extensions. May be you have customer extension catalog configured by catalog.url in /usr/local/psa/admin/conf/panel.ini ? If yes, temporary comment the line and run plesk daily UpgradeExtensions. If no, try to compare installed version with version from ext.plesk.com.

 

[Sofiia Kulish]

Your server might use the custom extension catalog with outdated plesk extensions versions.

Check the configuration parameter in the file /usr/local/psa/admin/conf/panel.ini
[extensions]
catalog.url

In case it's present in the configuration file, comment it, update the extension using
plesk bin extension -g performance-booster

Then check the access to the extensions list.
Then go to the Updates page, check for extension updates and update all outdated extensions.

Also you can update all extensions with
plesk daily -f UpgradeExtensions

After that uncomment your custom extension catalog URL.

 

[hayridumanli]

None of them is working, all the people here wrote the error code, but there is no solution on Plesk side, I feel like being a beta tester

But I solved it,

I rented another VPS in the same data center, plus I bought a FTP backup storage. I backed up to FTP storage and Google Drive, and I created a snapshot in Data Center, so I tried to take all the precautions. Then I installed the same OS (Alma Linux 9) to new VPS, bought a Plesk license. I migrated everything from current server to new server. I formatted the old server, of course all the Updates and Extensions should be the same in both VPS's, I did it. Then I migrated everything from new VPS to old VPS (clean installed). Migration gave some errors, but Re-sync solved it all. So, now old VPS is working without any problem. Errors have gone away with clean install.

All my data is 110 GB, so all process took almost 8 hours, I spent all night sleepless. Of course new VPS, Plesk, FTP backup costed me a lot, but at the end I got rid of those errors.

 

[Sofiia Kulish]

Another possible way why the server still uses the outdated extensions version is turned off "Auto update" toggle on /modules/catalog/index.php/updates.
Turn it on and run
plesk daily -f UpgradeExtensions