Resolved PECL doesn't work anymore?

[mxm.k.marquette@gmail]

Server operating system version

Ubuntu 20.04

Plesk version and microupdate number

Plesk Obsidian 18.0.50.0

when trying to install some extension for php

/opt/plesk/php/8.2/bin/pecl install memcached
No releases available for package "pecl.php.net/memcached"

/opt/plesk/php/8.2/bin/pecl install apcu
No releases available for package "pecl.php.net/apcu"

/opt/plesk/php/8.1/bin/pecl install apcu
WARNING: channel "pecl.php.net" has updated its protocols, use "pecl channel-update pecl.php.net" to update
Could not download from "https://pecl.php.net/get/apcu-5.1.22.tgz", cannot download "pecl/apcu" (Connection to `ssl://pecl.php.net:443' failed: )
Error: cannot download "pecl/apcu"
Download failed
install failed


Is there anything to do because its not nice to not be able to install extension at all

 

[mxm.k.marquette@gmail]

also got that error

N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'Index of /pool/SITEBUILDER_18.0.50_30 all InRelease' doesn't support architecture 'amd64'

 

[Peter Debik]

Have you tried running the suggested command "pecl chhannel-update pecl.php.net"?

 

[Peter Debik]

Also, if you believe you have found a product issue, please report it here: Reports

 

[mxm.k.marquette@gmail]

yes i have run the cmd with

/opt/plesk/php/8.2/bin/pecl channel-update pecl.php.net

and only the cmd

pecl channel-update pecl.php.net

 

[Peter Debik]

An engineer has tried to reproduce the issue, but it could not be reproduced here. We believe there is a certificate issue on the server, but that is not related to Plesk.
Could you instead try to download the extension directly, e.g.
# curl https://pecl.php.net/get/apcu-5.1.22.tgz
and then add it to PHP manually? Some steps are described in https://support.plesk.com/hc/en-us/...-for-PHP-engines-shipped-with-Plesk-on-Linux-

 

[mxm.k.marquette@gmail]

root@optimusprime ~ # curl https://pecl.php.net/get/apcu-5.1.22.tgz
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
root@optimusprime ~ #

 

[Peter Debik]

Well, then use parameters
-- output <FILE>
or try other download method like wget.

 

[mxm.k.marquette@gmail]

root@optimusprime ~ # curl --output apcu-5.1.22.tgz https://pecl.php.net/get/apcu-5.1.22.tgz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 93926 100 93926 0 0 119k 0 --:--:-- --:--:-- --:--:-- 119k
root@optimusprime ~ #


it work flawlessly so i dont know how the ingeneer cant reproduce it but me i have this bug.

 

[Peter Debik]

There can be many reasons for blocked connections. This will probably need to be checked on your server. Asking Plesk support is always an option for it. Is a firewall in the way? Were there recent operating system changes/updates? It's not possible to tell from the forum post. This needs to be checked on the server.

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com

 

[mxm.k.marquette@gmail]

i fix it myself, the people of plesk were not able to do it.

for the futur and posterity if someone need help with that i found the solution online and adapt it.

How to install openssl 1.0.2 with default openssl (1.1.1) on Ubuntu 16.04?

P4Python does not work on Ubuntu 16.04 since the distribution comes with OpenSSL 1.1.0g.(details). I am trying to build P4Python from source using --ssl path/to/openssl1.0. I need to install OpenSS...

askubuntu.com

 Fix for Ubuntu 20.04, Openssl after upgrade if problem with PECL

# (Uninstall new version of openssl most like 1.1.1ish)
cd folder/where/you/download/install/the/new/version/
sudo make uninstall

# (Install compiling library Make)
sudo apt-get install make

# (Download the latest OpenSSL 1.0.2u binaries)
wget https://ftp.openssl.org/source/old/1.0.2/openssl-1.0.2u.tar.gz

# (Extract the tar ball to the local directory)
tar -xzvf openssl-1.0.2u.tar.gz

# (Enter extracted OpenSSL directory)
cd openssl-1.0.2u

#  (Configure binaries for compiling)
sudo ./config

# (install configured binaries)
sudo make install

# (This will create a sym link to the new binaries)
sudo ln -sf /usr/local/ssl/bin/openssl `which openssl`

# (Used to check the version of the Current OpenSSL binaries)
openssl version -v

should give this output.
OpenSSL 1.0.2u

 

[mxm.k.marquette@gmail]

then boom christmas magic on ubuntu! it rework and everything is fine!

 

[Peter Debik]

i fix it myself, the people of plesk were not able to do it.

Could you please let me know your support ticket ID? It's hard to believe that Plesk engineers could not find a solution, so I'd like to check into the ticket to see what has happened with that support case. You did open a ticket, didn't you?

 

[mxm.k.marquette@gmail]

Yes and it's not against them just that they think that it was not something related to plesk so since that they cannot give support.

i had stefan and a girl really gentil a nice, always love the staff here last time man it took almost 1 week to finally make my server survive lol man you did magic.

https://support.plesk.com/hc/en-us/requests/401074

 

[Peter Debik]

Thank you, I checked both tickets. The support engineers concentrated on solving the installation issues and were successful. Both are great experts I must say and very experienced. Stefan pointed out that there is a general OpenSSL issue on the server. As operating system configurations and maintenance are not scope of Plesk, it was correct that you went ahead and updated OpenSSL on your server to solve that. So after all, this was a perfect solution approach: For one, the specific requests were solved through support, second you were able to solve the underlying cause on the operating system level. So future installations will work on your system again.

Thank you, too, for letting us know your solution for the OpenSSL upgrade. This will help others a great deal when they run into a similar situation.