Quantcast
Channel: EasyEngine Community Forum - Latest posts
Viewing all 12639 articles
Browse latest View live
↧

Brand new EC2 instance fails installing V4

March 3, 2019, 12:27 pm
$
0
0

V4 issues continue. I agree with the popular post recently that V4 is still in beta phase and shouldn’t be used live.

Here’s my latest try. Brand new EC2 t2.medium, all I did is updated the packages and ran EEv4 install and got this:

ubuntu@ip-172-31-11-87:/opt/easyengine$ sudo ee site create website.com --type=wp
Error: There was some error in starting services_global-nginx-proxy_1 container. Please check logs.

Checking logs gives you this:

[03-03-2019 20:26:12] ee.INFO: ::::::::::::::::::::::::ee invoked::::::::::::::::::::::::
[03-03-2019 20:26:12] ee.DEBUG: -----------------------
[03-03-2019 20:26:12] ee.DEBUG: COMMAND: docker ps > /dev/null
[03-03-2019 20:26:12] ee.DEBUG: RETURN CODE: 0
[03-03-2019 20:26:12] ee.DEBUG: -----------------------
[03-03-2019 20:26:12] ee.DEBUG: -----------------------
[03-03-2019 20:26:12] ee.DEBUG: COMMAND: command -v docker-compose > /dev/null
[03-03-2019 20:26:12] ee.DEBUG: RETURN CODE: 0
[03-03-2019 20:26:12] ee.DEBUG: -----------------------
[03-03-2019 20:26:12] ee.DEBUG: Using default global config: /opt/easyengine/config/config.yml
[03-03-2019 20:26:12] ee.DEBUG: No project config found
[03-03-2019 20:26:12] ee.DEBUG: argv: /usr/local/bin/ee site create website.com --type=wp
[03-03-2019 20:26:12] ee.DEBUG: Running command: site
[03-03-2019 20:26:12] ee.DEBUG: COMMAND: which docker
[03-03-2019 20:26:12] ee.DEBUG: RETURN CODE: 0
[03-03-2019 20:26:12] ee.DEBUG: -----------------------
[03-03-2019 20:26:12] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-nginx-proxy_1
[03-03-2019 20:26:13] ee.DEBUG: STDOUT:
[03-03-2019 20:26:13] ee.DEBUG: STDERR: Error: No such object: services_global-nginx-proxy_1
[03-03-2019 20:26:13] ee.DEBUG: RETURN CODE: 1
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: COMMAND: docker network inspect ee-global-backend-network
[03-03-2019 20:26:13] ee.DEBUG: STDOUT: [     {         "Name": "ee-global-backend-network",         "Id": "8d5d7e1b671d50889aa4a3dffe11118587d984bea3aeb89aced5035ca9d043eb",         "Created": "2019-03-03T19:57:49.457591081Z",         "Scope": "local",         "Driver": "bridge",         "EnableIPv6": false,         "IPAM": {             "Driver": "default",             "Options": {},             "Config": [                 {                     "Subnet": "172.18.0.0/16",                     "Gateway": "172.18.0.1"                 }             ]         },         "Internal": false,         "Attachable": false,         "Ingress": false,         "ConfigFrom": {             "Network": ""         },         "ConfigOnly": false,         "Containers": {},         "Options": {},         "Labels": {             "org.label-schema.vendor": "EasyEngine"         }     } ]
[03-03-2019 20:26:13] ee.DEBUG: RETURN CODE: 0
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: COMMAND: docker network inspect ee-global-frontend-network
[03-03-2019 20:26:13] ee.DEBUG: STDOUT: [     {         "Name": "ee-global-frontend-network",         "Id": "06619a56d91995c4b10c0542db5a32dd67fecf3ababd3874dfb95cec54f4d7cb",         "Created": "2019-03-03T19:57:49.577470065Z",         "Scope": "local",         "Driver": "bridge",         "EnableIPv6": false,         "IPAM": {             "Driver": "default",             "Options": {},             "Config": [                 {                     "Subnet": "172.19.0.0/16",                     "Gateway": "172.19.0.1"                 }             ]         },         "Internal": false,         "Attachable": false,         "Ingress": false,         "ConfigFrom": {             "Network": ""         },         "ConfigOnly": false,         "Containers": {},         "Options": {},         "Labels": {             "org.label-schema.vendor": "EasyEngine"         }     } ]
[03-03-2019 20:26:13] ee.DEBUG: RETURN CODE: 0
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.DEBUG: COMMAND: docker-compose up -d global-nginx-proxy
[03-03-2019 20:26:13] ee.DEBUG: STDERR: Volume global-nginx-proxy_vhostd declared as external, but could not be found. Please create the volume manually using `docker volume create --name=global-nginx-proxy_vhostd` and try again.
[03-03-2019 20:26:13] ee.DEBUG: RETURN CODE: 1
[03-03-2019 20:26:13] ee.DEBUG: -----------------------
[03-03-2019 20:26:13] ee.ERROR: There was some error in starting services_global-nginx-proxy_1 container. Please check logs.
↧
Search

Improve my.cnf from the server

March 3, 2019, 12:35 pm
$
0
0

Server in Digital Ocean, 2GB / 50GB Disk

↧
↧

After installing EE 4.0.10 command is not working

March 3, 2019, 12:48 pm
$
0
0

After installing EE 4.0.10 commands are not working. It is showing Error: could not find driver.

Not a single command is working that are working on EE 3.8.

Any suggestions or any guide to go back to previous version EE 3.8 so all previous commands are working fine for me.

↧

Upgrade from v3 to v4

March 3, 2019, 1:22 pm
$
0
0

Hey,

I updated through direct download command from EE 3.8 to EE 4 now not a single command is working even for creating a new site. Any suggestion how to fix it.

For every command i am getting “Error: could not find driver”

OR

How to reinstall my previous version EE 3.8

↧

There was some error in starting services_global-nginx-proxy_1 container

March 3, 2019, 4:33 pm
$
0
0

When creating a site the error occurs: Error: There was some error in starting services_global-nginx-proxy_1 container. Please check logs.

follows the error log:

[03-03-2019 23:49:37] ee.INFO: ::::::::::::::::::::::::ee invoked::::::::::::::::::::::::

COMMAND: docker ps > /dev/null
RETURN CODE: 0

COMMAND: command -v docker-compose > /dev/null
RETURN CODE: 0

Using default global config: /opt/easyengine/config/config.yml
No project config found
argv: /usr/local/bin/ee site create mysite.com.br --type=php --ssl=le
Running command: site
COMMAND: which docker
RETURN CODE: 0

COMMAND: docker inspect -f ‘{{.State.Running}}’ services_global-nginx-proxy_1
STDOUT: false
RETURN CODE: 0

COMMAND: docker network inspect ee-global-backend-network
STDOUT: [ { “Name”: “ee-global-backend-network”, “Id”: “0c3186f4ae3f4e5f9d47416a73719cb4361136253ec0aa18bb445b65d48b44fc”, “Created”: “2018-11-29T21:30:02.357309234Z”, “Scope”: “local”, “Driver”: “bridge”, “EnableIPv6”: false, “IPAM”: { “Driver”: “default”, “Options”: {}, “Config”: [ { “Subnet”: “172.18.0.0/16”, “Gateway”: “172.18.0.1” } ] }, “Internal”: false, “Attachable”: false, “Ingress”: false, “ConfigFrom”: { “Network”: “” }, “ConfigOnly”: false, “Containers”: {}, “Options”: {}, “Labels”: { “org.label-schema.vendor”: “EasyEngine” } } ]
RETURN CODE: 0

COMMAND: docker network inspect ee-global-frontend-network
STDOUT: [ { “Name”: “ee-global-frontend-network”, “Id”: “a7143232caf8f7d45d32591e1c859fd70544cf2fcdf17c2b13269147f12dd403”, “Created”: “2018-11-29T21:30:02.66337447Z”, “Scope”: “local”, “Driver”: “bridge”, “EnableIPv6”: false, “IPAM”: { “Driver”: “default”, “Options”: {}, “Config”: [ { “Subnet”: “172.19.0.0/16”, “Gateway”: “172.19.0.1” } ] }, “Internal”: false, “Attachable”: false, “Ingress”: false, “ConfigFrom”: { “Network”: “” }, “ConfigOnly”: false, “Containers”: {}, “Options”: {}, “Labels”: { “org.label-schema.vendor”: “EasyEngine” } } ]
RETURN CODE: 0

COMMAND: docker-compose up -d global-nginx-proxy
STDERR: Starting services_global-nginx-proxy_1 … e[1Ae[2K Starting services_global-nginx-proxy_1 … e[31merrore[0m e[1B ERROR: for services_global-nginx-proxy_1 Cannot start service global-nginx-proxy: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown ERROR: for global-nginx-proxy Cannot start service global-nginx-proxy: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown Encountered errors while bringing up the project.
RETURN CODE: 1

ee.ERROR: There was some error in starting services_global-nginx-proxy_1 container. Please check logs.

Does anyone know how to solve

↧
↧

SFTP setup tutorial is not working for me

March 3, 2019, 6:02 pm
$
0
0

same. has someone figured it out? this is insane, i just wasted hours on this

↧

EEv4 Current Status (4.0.10) - So close yet so far

March 3, 2019, 6:36 pm
↧

Upgrade Issue 4.0.4 -> 4.0.10

March 4, 2019, 1:24 am
$
0
0

Guys I’m facing an update issue again. This time from 4.0.4 to 4.0.10

     Error: Errors were encountered while processing: 20181225063950_service-command_change_global_service_container_names.php
     Unable run change-global-service-container-name migrations.

That’s what ee cli update gives me. SSL renewals also don’t seem to work anymore.

Any idea to solve it?

↧
Search

EEv4 Current Status (4.0.10) - So close yet so far

March 4, 2019, 1:37 am
$
0
0

Hey, interesting approach with your own docker stack? I’m a big fan of docker and using it on some other projects. Why not share it and have a few interested people improve it together?

↧
↧

EEv4 Current Status (4.0.10) - So close yet so far

March 4, 2019, 1:50 am
$
0
0

Interesting to read that. I just noticed it’s made by Delicious Brains. I had my experience with them through their WP Migrate DB plugin which holds me off from instantly jumping on any boats they control. Though will be interesting to see how SpinupWP develops.

↧

EEv4 Current Status (4.0.10) - So close yet so far

March 4, 2019, 1:54 am
$
0
0

Hi, thanks for your interest. It’s nowhere near ready for other people to use it yet, the main bash script has lots of bugs I’m working on.

↧

EEv4 Current Status (4.0.10) - So close yet so far

March 4, 2019, 2:01 am
$
0
0

First of all: I’m a big fan of docker. I can imagine people having a hard time getting used to the changes involved by the nature of docker I think it’s totaly the right thing to switch to it.

Apart from that I’m also wondering how that Switch to EEv4 happened in the way it happened. I have to admit, I don’t have a deep insight into the project and what it means for the company behind from an outside perspective I’d say the switch overall was a bit unlucky. For a final release you’d expect to have at least the most important featureset onboard or otherwise put big warning letters on every public post that says stuff like “Be aware that this is a complete rewrite and we start off with a very limited featureset” naming all the important stuff missing like (s)ftp to single sites, editable sites, switching types etc.

In addition the reliability of the update script of course is a problem. It’s kind of the central tool that has to work reliably.

I can remember having read about funding problems for the project in the past and can only imagine that it’s hard to keep it up. That’s why I try to stay soft on the critics. I’m sure the guys behind this, especially @rahul286 are investing a lot of time and energy to try to keep this free and open source. I appreciate that but I also agree with what @terencemilbourn said. I wish there was a commercial model in addition. One that also is affordable for the smaller customers, probably enables some additional features or support but foremost opens the ability to put this project on a solid funding base. With all the other projects around I think there’s still a lot of potential for such a project.

I’ll definitely stay with EE as long as I can keep my sites running and i’m totally willing to work around some glitches if only in thanks for what the guys did for the community in the last years.

↧

Ubuntu 16.04 LTS fresh install gives error

March 4, 2019, 2:28 am
↧
↧

SSL Cert Renewal & CLI update Failure

March 4, 2019, 8:00 am
$
0
0

Hi there,

I’m having the same issues as Helmi here: SSL Cert renewal failed on RC2, now updates to 4.0.10 fails because of that

My current EE version is 4.0.5 and attempting to update with ee cli update or to renew SSL certs gives me the error:
Error: Errors were encountered while processing: 20190128101515_site-command_renew_ssl.php
cURL error 60: SSL certificate problem: certificate has expired (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Is it possible for you to share the steps taken to correct this issue?

↧

My all site got down

March 4, 2019, 9:15 am
↧
Search

SSL Renew ERROR and update 4.0.3 to 4.0.10 impossible

March 4, 2019, 9:25 am
$
0
0

I have some problems about ssl certificat renewal doesn’t work anymore and also impossible to make any update to a newer version of ee.

When I try to make update i get that errors:

Error: Encountered error while processing remove-global-ee-containers in EE\Migration\ChangeGlobalServiceContainerNames::remove_global_ee_containers. Exception: Unable to remove global service containers
Error: Errors were encountered while processing: 20181225063950_service-command_change_global_service_container_names.php
Unable run change-global-service-container-name migrations.

or if I try to force renew ssl cert :

Error: Failed to verify SSL: cURL error 60: SSL certificate problem: certificate has expired (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Does i really need backup all site I have and make newer install ?

↧

Ubuntu 16.04 LTS fresh install gives error

March 4, 2019, 9:36 am
$
0
0

pls help me

This site can’t be reached

ganvwale.com refused to connect.

Try:

  • Checking the connection
  • Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

Reload : nginx [Failed]

All site got down pls argent help.

↧
↧

Upgrade Issue, SSL-Renewal error 4.0.x -> 4.0.10

March 4, 2019, 7:00 pm
$
0
0

Ive been trying to figure this one out and am failing…

↧

Working with 2 VPS's - Staging and Production - How to copy from one to another

March 4, 2019, 10:31 pm
$
0
0

You don’t - you need to create a new site - when you’re migrating you need to have environment of the new (live) site. The changes apply only to the DB. It’s not wise to transfer any config files or system files (including nginx/docker) between servers.
So you need to create a new site with live URL then migrate files and DB and then do search and replace in the DB on the new site.

↧

Cannot install ioncube on EE v4

March 4, 2019, 11:08 pm
$
0
0

im looking for solutions too.

Hope they will support us

↧
Viewing all 12639 articles
Browse latest View live
Search