multiple php 7.4 on fresh ispconfig 3.2 install on debian buster

Hi,
I cannot much information concerning this. Is it risky? This is a prod environment so I would prefer not breaking anything.
Let recall that actually php version is 7.2. Should I use surry package.

Thanks, for your work.

 

Yes. Just follow the tutorial for it.

 

Thanks for your answer Ahrasis,
Tutos I found were dealing with debian 8-9.
I did not find confirmation tutos dealing with buster version.
Would you have a link for that?

 

Your topic says "multiple php 7.4". that I do not know how to make work. And why do you need multiple 7.4 versions anyway? If you are satisfied with PHP versions from 5.6. to 7.4, there is tutorial

https://www.howtoforge.com/tutorial...fig-3-from-debian-packages-on-debian-8-and-9/

 

Thanks for your answer Taleman.
Sorry I was not enough explicit. I have a fresh debian buster install with ispconfig 3.2.3 installed on it and thus I have php 7.3 installed as default for ispconfig. I did not find any tuto corresponding exactly to the
I read on the forum that is was a very bad idea to change default php version of ispconfig.
However, I need a php 7.4 for a website, so default php 7.3 was not enough. I added sury repo, installed 7.4 and added 7.4 version iin ispconfig, and ...
That worked!
Thanks again for you attention.

 

Hi guys,

I followed the guide for PHP 7.4 installation (the link that @Taleman posted) so I just have one question, on step 4 where we need to install gpg keys I get an error:

#wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg
#Resolving packages.sury.org (packages.sury.org)... 89.38.224.138
#Connecting to packages.sury.org (packages.sury.org)|89.38.224.138|:443... connected.
#ERROR: The certificate of ‘packages.sury.org’ is not trusted.
#ERROR: The certificate of ‘packages.sury.org’ has expired.

Does anybody have a solution for this? Just to mention it's Debian 9 in question.

Thanks..

 

Till, thank you very very much for your help . This was the problem regarding the Let's Encrypt CA revocation.