update to php 7.2 in Ubuntu 18.04

@acanton77 I'm sorry to hear that you are having some trouble installing PHP 7.2. I'm not certain if there were additional steps in your install, but the error message you received seems to point towards having the wrong package installed. The forum posts below include a solution that may work for Ubuntu 18.04

• ERROR: Module php7.0 does not exist!

• White Screen - PHP 7 on Ubuntu 16.04 fails to render scripts

I hope these are helpful, and let the Community know if you have any more questions.

I've looked around and it seems that I have to "apt-get install" php 7.2 from somewhere. HOWEVER, it might be easier to just jump up to 7.3.

It is not done via a plain old "apt-get."

It seem that 7.2 is in a Ubuntu repository but 7.3 is not?

This should be easy, but I'm totally confused. I'm not the most experienced system admin, but I can maintain a simple Linode with Ubuntu.

What am I missing here.

See:

https://www.cloudbooklet.com/how-to-install-php-7-3-on-ubuntu-18-04/

Skip down to the section entitled Add PPA for PHP 7.3… You've done all the stuff before that.

I used PPAs from this developer for many years…for both apache2 and php7.x. They're rock solid.

-- sw

I got it done!

I decided to go right to PHP 7.4 and this site tells just how to do it… step by step:

https://www.cloudbooklet.com/upgrade-php-version-to-php-7-4-on-ubuntu/

I'd also advise to forget LISH. On my iMac with Catalina and latest Chrome, the web terminal was unstable… kept losing the cursor and overwriting its messages. It was a mess. I just did a standard ssh from my iMac terminal.

@acanton77 I'm glad you were able to get PHP sorted! The Lish console, accessible from Cloud Manager, does have some limitations. This is due to the actual size of the terminal, and the set size can't be changed at this time. You will find that the text may get weird if you go over the number of characters that fit across that size screen. That being said, I wanted you to know that you can always access LISH using a terminal application. I've linked the section of our Lish guide that explains this a bit more. Stay safe!

• Use a Terminal Application

I tried to use LISH from my terminal. Previously I added my id_rsa.pub Public Key and set LISH to use both the key and password. But it won't work and so I gave up on it.

al@acimac ~ % ssh xxxxxx@lish-fremont.linode.com
xxxxxxxx@lish-fremont.linode.com: Permission denied (publickey).
al@acimac ~ %

I can't imagine what I did wrong… this is not exactly rocket science… pasting in the key and hitting the 'save' button!! Maybe I didn't read the directions correctly. I don't see what the big advantage of LISH is over a normal SSH?

(PS: Is there a way to get an email notification when someone answers a question here? I looked all over for a setting can didn't fine one.)

Do you have a login called al on your Linode? If not, you're going to get that error because ssh(1) is going to use the login al.

Try this:

al@acimac ~ % ssh xxxxxx@lish-fremont.linode.com -l some-login

replacing some-login with a valid user on your Linode. Or, create a user al on your Linode.

If you create a user al…and you don't want to be prompted for al's password every time you login from your Mac, you need to put the public key for your Mac on the Linode (you generate ssh(1) keys on your Mac the same way you do on Linux). It has to be in the file /home/al/.ssh/authorized_keys and /home/al/.ssh and the authorized_keys file need to have the correct ownership and permissions.

Here's the contents of my /home/stevewi/.ssh directory:

-rw-------  1 stevewi stevewi 1209 Apr  4 12:42 authorized_keys
-rw-------  1 stevewi stevewi 1823 Jul 15  2019 id_rsa
-rw-r--r--  1 stevewi stevewi  394 Jul 16  2019 id_rsa.pub
-rw-------  1 stevewi stevewi 1332 Apr  4 12:43 known_hosts
drwx------  2 stevewi stevewi 4096 Apr  4 12:43 public_keys

known_hosts is maintained by sshd(1). id_rsa* are the keys for my Linode. public_keys is a directory maintained by me containing the public keys for all the systems I want to use to sign on to my Linode using the login stevewi. authorized_keys is formed using the commands:

cat public_keys/* >authorized_keys
chmod 0400 authorized_keys

/home/al/.ssh must have ownership/permissions like this:

drwx------  3 stevewi stevewi  4096 Apr  4 12:43 .ssh

(i.e., 0700).

-- sw