EasyEngine/easyengine

EasyEngine Network Services Failing

afruit opened this issue · 2 comments

afruit commented

I am having an issue with the EasyEngine web service related to networking, where it is not listening on the web ports 80 & 443. The resulting affect is two-fold:

  1. None of my hosted websites on this droplet are accessible. I just get a "Can not Connect to server" error. They were previously working and everything was fine.

  2. I cannot connect with anything externally from the droplet. My droplet has software updates that when I try to update from the terminal via SSH, I get 404 errors for all of the resources it attempts to connect to. If I try and install any command line tools, it fails with 404 errors, etc.

I can reach the Droplet's SSH port from external tests so the overall network of the Droplet is functioning properly. There is no protocol/DNS level issue and I have no security or firewall blocks on the Droplet either. I can make a connection over http to an external source (e.g. curl -IL google.com, so it seams like it's not an issue with the Droplet itself.

System Information

ee cli info

+-------------------+----------------------------------------------------------------------------+
| OS                | Linux 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 |
| Shell             | /bin/bash                                                                  |
| PHP binary        | /usr/bin/php7.3                                                            |
| PHP version       | 7.3.28-1+ubuntu21.04.1+deb.sury.org+3                                      |
| 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  | /opt/easyengine/config/config.yml                                          |
| EE project config |                                                                            |
| EE version        | 4.6.5                                                                      |
+-------------------+----------------------------------------------------------------------------+

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 21.04
Release:        21.04
Codename:       hirsute

docker version

Client: Docker Engine - Community
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        370c289
 Built:             Fri Apr  9 22:48:16 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:46:27 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker-compose version

docker-compose version 1.22.0, build f46880fe
docker-py version: 3.4.1
CPython version: 3.6.6
OpenSSL version: OpenSSL 1.1.0f  25 May 2017
afruit commented

Additional info:

If I run:
ip -br a

One of the things I see in the output is:
docker0 DOWN 10.0.0.1/24

This Networking Configuration Issues article at Digital Ocean makes it sound like it shouldn't be that way:
https://docs.digitalocean.com/support/check-your-droplets-network-configuration/

I can not run ifup, however, because I would need to install ifupdown with:apt install ifupdown, and as I have already established above, my droplet isn't able to connect externally.

afruit commented

Update:

I fixed it using freedog96150's solution, seen here:
https://community.easyengine.io/t/services-and-sites-not-restarting-on-reboot/14195/2

Solution Summarized:

  1. Disable each site on droplet individually with: sudo ee site disable sitename.com
  2. Run docker-compose down && docker-compose up -d (must cd into the services directory beforehand)
  3. Re-enable each site on droplet individually with: sudo ee site enable sitename.com

His theorization on why this happens is interesting. I guess no fix has been employed by EasyEngine to allow a more organized start up process.

  • 👍1