EasyEngine OpenVZ "Little Creek Hosting" - failed to EasyEngine

Good day,

I have installed Ubuntu 16.04 (LTS) and did an update after the installation. Then I installed EasyEngine.

Unfortunately, I have received the following message:

Hit:6 …/ubuntu xenial InRelease
Err:3 …/ubuntu xenial InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
Reading package lists… Done
W: GPG error: …/ubuntu xenial InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
E: The repository …/ubuntu xenial InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.

I have no idea why it happened in the first place. It happened after installing EasyEngine.

WARNING: The following packages cannot be authenticated!
libpcre3 libicu65 libssl1.1 libxml2 openssl
Install these packages without verification? [y/N] y

The sad part is, I cannot start EasyEngine.

root@vps:~# ee --help
/usr/bin/env: ‘php’: No such file or directory
root@vps:~# ee

Now, I have decided to install Ubuntu 18.04 (LTS).

After the installation I saw this:

Status: Downloaded newer image for easyengine/redis:v4.0.0

| OS | Linux 3.10.0-1062.12.1.vz7.131.10 #1 SMP Mon Mar 16 15:3 |
| | 9:59 MSK 2020 x86_64 |
| Shell | /bin/bash |
| PHP binary | /usr/bin/php7.3 |
| PHP version | 7.3.21-1+ubuntu18.04.1+deb.sury.org+1 |
| php.ini used | /etc/php/7.3/cli/php.ini |
| EE root dir | phar://ee.phar |
| EE vendor dir | phar://ee.phar/vendor |
| EE phar path | /root |
| EE packages dir | |
| EE global config | |
| EE project config | |
| EE version | 4.1.1 |
-----> Run “ee help site” for more information on how to create a site.

When I decided to create a site, I received this message:

root@vps:~# ee site create onekarlo.com --type=wp --ssl=le
Error: Cannot create/start proxy container. Please make sure port 80 and 443 are free.

Any thoughts about this?

Most OpenVZ servers can’t run Docker due to the host node using an ancient kernel. Ask your host or upgrade to a KVM VPS.

1 Like

The complaint on port 80 and 443 is most likely because your Ubuntu 18.04 install template provided by your hosting company came with Apache installed. Check for running processes using top, htop, or ps. I suspect you’ll find Apache running. Also check ports using
sudo lsof -i -P -n | grep LISTEN

Even after you deal with that you will most likely run into problems running EE4 which uses docker on an OpenVZ host. I use ramnode and I believe they have a modern kernel and modern OpenVZ. I’ve installed and run docker without issue. Yet I have just had issues with the latest version of EE which appears to be related to sysctls now being in the docker compose files for EE4 containers. It would appear OpenVZ or ramnode prevents writing those sysctls and therefore everything fails. You can see my other thread here from this weekend. My solution was to run and older version of EE4.

I’d suggest trying to use KVM or Xen based vps providers.