Issue No sodium extension for PHP 7.4.30 FPM

[ShayLash]

Hi,
I can confirm that the solution in the KB article does not solve the problem for me. The sodium.ini files were already removed from
/opt/plesk/php/7.4/etc/php.d/
/opt/plesk/php/8.0/etc/php.d/
/opt/plesk/php/8.1/etc/php.d/
so no need to move them to the /root directory (which is very strange to me by the way. Why the /root directory ??). I tried ( without much hope ) to add a sodium.ini_80 containing what the original sodium.ini file was containing to no avail.

@IgorG can you keep us posted if and when the dev find a solution to this bug.

Thanks.

 

[AvaDev]

We experienced the same issue. We had to upgrade our Plesk instance from Debian 9 to 10 in order to use Argon2i again.

Thanks for the hint. Dist-upgrade from debain 9 to debain 10 bring back Argon2id.

 

[Hangover2]

We had the same problems e.g. with Nextcloud instances (login was not possible anymore / error messages).

It seems after the upgrade the PHP handlers need to be restarted. This solved our login problem mentioned.
Some servers also hat the mentioned sodium.ini leftovers.

 

[Kapelan]

We had the same problems e.g. with Nextcloud instances (login was not possible anymore / error messages).

It seems after the upgrade the PHP handlers need to be restarted. This solved our login problem mentioned.
Some servers also hat the mentioned sodium.ini leftovers.

This does not solve the issues with Typo3 and Argon2... at least not for us.

 

[nbaumont]

Hello

None of the solutions offered here solve the problem.
I tried to install php7.4.29 but the PHP extensions screen remains blank.


When will this issue be resolved? It's getting pretty urgent.

 

[mizar]

Hello,

The updated packages are now availiable on dowload server, you can update your Plesk

 

[Kapelan]

Hello,

The updated packages are now availiable on dowload server, you can update your Plesk

Works. Thanks!

 

[Adam Makowski]

Thanks to the Plesk team for the quick repair ☺️

 

[Hangover2]

We did install the new update on two of our servers. The result was headache again.
Maybe our documentation can help others that run into the same problems.

Both servers are using Debian 10 and did get the previous Plesk PHP Updates from 14th of June 2022 already and were repaired accordingly.
They have the same configuration, but one server was upgraded from Debian 9 to Debian 10 in the past ("Server 1").

After applying the new Plesk PHP updates from 17th of June 2022 the following happened:

Server 1:
- we had again problems with our Nextcloud instances running on the server (login was not possible anymore / error messages)
- workaround: restart PHP handlers manually or reboot the server (we are using a lot of dedicated FPM handlers)

Server 2:
- this server had more serious problems: the sodium.ini files were not created by the update (on the update before on this server the sodium.ini files were also not removed - we did that manually as recommended by the Plesk team)
- workaround: create the files manually and restart the PHP handlers or reboot the server (we are using a lot of dedicated FPM handlers)
- follow-up problem: the sodium extension was still not listed again under "Tools & Settings => PHP Settings"
- workaround: run "plesk repair web -php-handlers"

 

[Deagan]

I'm trying to update a server ( yum update / CentOS 7 ), I got this error and found this topic. Seems related?

---> Package plesk-php74-sodium.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-sodium.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
--> Processing Dependency: libsodium.so.23()(64bit) for package: plesk-php74-sodium-7.4.30-1centos.7.220616.1430.x86_64
---> Package plesk-php74-tidy.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-tidy.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
---> Package plesk-php74-xdebug.x86_64 0:3.1.4-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xdebug.x86_64 0:3.1.5-1centos.7.220615.1150 will be an update
---> Package plesk-php74-xml.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xml.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
---> Package plesk-php74-xmlrpc.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xmlrpc.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
--> Finished Dependency Resolution
Error: Package: plesk-php74-sodium-7.4.30-1centos.7.220616.1430.x86_64 (PLESK_17_PHP74)
Requires: libsodium.so.23()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

 

[mizar]

I'm trying to update a server ( yum update / CentOS 7 ), I got this error and found this topic. Seems related?

---> Package plesk-php74-sodium.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-sodium.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
--> Processing Dependency: libsodium.so.23()(64bit) for package: plesk-php74-sodium-7.4.30-1centos.7.220616.1430.x86_64
---> Package plesk-php74-tidy.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-tidy.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
---> Package plesk-php74-xdebug.x86_64 0:3.1.4-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xdebug.x86_64 0:3.1.5-1centos.7.220615.1150 will be an update
---> Package plesk-php74-xml.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xml.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
---> Package plesk-php74-xmlrpc.x86_64 0:7.4.29-1centos.7.220415.1034 will be updated
---> Package plesk-php74-xmlrpc.x86_64 0:7.4.30-1centos.7.220616.1430 will be an update
--> Finished Dependency Resolution
Error: Package: plesk-php74-sodium-7.4.30-1centos.7.220616.1430.x86_64 (PLESK_17_PHP74)
Requires: libsodium.so.23()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

EPEL repository should be enabled during update to 7.4.30 by plesk installer, but yum update definitely doesnt' enable it.