Cannot create/start proxy container. Please make sure port 80 and 443 are free. Only 2 sites are on server


#1

Tried to add new site to latest version of easyengine but facing issue Cannot create/start proxy container. Please make sure port 80 and 443 are free.
command lsof -i :80 | grep LISTEN
gives: docker-pr 1450 root 4u IPv6 21041 0t0 TCP *:http (LISTEN)
and same with
lsof -i :443 | grep LISTEN
docker-pr 1410 root 4u IPv6 20925 0t0 TCP *:https (LISTEN)

Also how do i add cache to old site built using command ee site create example.com --type=wp
Kindly help.


#2

It appears something in v4.0.8 is broken. I am also unable to create any sites. All of my containers have random numbers appended to the end.

ee site create example.com --type=wp
Error: Cannot create/start proxy container. Please make sure port 80 and 443 are free.

ee.log:

[27-12-2018 22:39:39] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-nginx-proxy_1  
[27-12-2018 22:39:39] ee.DEBUG: STDOUT:    
[27-12-2018 22:39:39] ee.DEBUG: STDERR: Error: No such object: services_global-nginx-proxy_1   
[27-12-2018 22:39:39] ee.DEBUG: RETURN CODE: 1
docker ps | grep services_global
51749b3ede23        easyengine/mariadb:v4.0.0       "docker-entrypoint.s…"   21 hours ago        Up 8 minutes        3306/tcp                                   services_global-db_1_9e9ab889f5a8
6f3a64e7e8b1        easyengine/redis:v4.0.0         "docker-entrypoint.s…"   21 hours ago        Up 8 minutes        6379/tcp                                   services_global-redis_1_a6c67d822edf
0384539aea37        easyengine/nginx-proxy:v4.0.1   "/app/docker-entrypo…"   21 hours ago        Up 8 minutes        0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   services_global-nginx-proxy_1_b66957c41f47

#3

A follow up post. I built a new ee v4.0.8 server and everything works fine. Somehow during the upgrade from 4.0.6 to 4.0.8 the containers changed their names. I did have a hard time upgrading and had to run ee cli update several times. I assume that had something to do with it.


#4

@diamond_sharma please send logs present at /opt/easyengine/logs/ee.log to ee@rtcamp.com so that this issue can be looked into.


#5

had to run ee cli update several times

@mram why did this happen? ee cli update needs to be run only once. Did you cancel it in between? Random numbers at the end should not have come. Can you send the logs of that server to ee@rtcamp.com so that this can be investigated.


#6

i have sent the logs. Kindly look into it once and plz tell me how to add cache to pre existing site


#7

Emailed. Thanks


#8

plz tell me how to add cache to pre existing site

It is my understanding the ee site update is not fully functional yet. You need to backup the site, create it again with --cache and then restore. I have been making a lot of progress on my backup/restore scripts. You are welcome to try them. https://github.com/microram/ee4-tools


#9

Got any solution for this problem then???


#10

Got any solution for this problem then???

I was able to fix by putting up a new clean v4.0.8 server and restored the sites without issue. Do you have your sites backed up in an automated way? I consider EE servers to be disposable. I expect sites to get trashed (grrr users) or compromised or whatever and have made sure I am in a position to burn down the old server at any time and spin up a new one quickly with some scripts. EasyEngine is a free open source project. I don’t expect anything from them and welcome everything they accomplish that helps me. Being on the bleeding edge comes with issues. If you need stability, move back to ee v3 for a while. If you have a backup/restore question, please post it. This is a great community and we will all help.


#11

I had the same issue as described by @diamond_sharma after upgrading to v4.0.8. I had to manually stop the nginx_proxy container and even so, I could not ee site create as Easy Engine would not find the appropriate containers.

Looking at the logs, it seemed like EE was unable to find the services container to create the new site.

[30-12-2018 05:49:51] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec  
[30-12-2018 05:49:51] ee.DEBUG: STDERR: Error: No such container: services_global-db_1   
[30-12-2018 05:49:51] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:51] ee.DEBUG: -----------------------  
[30-12-2018 05:49:52] ee.DEBUG: -----------------------  
[30-12-2018 05:49:52] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec  
[30-12-2018 05:49:52] ee.DEBUG: STDERR: Error: No such container: services_global-db_1   
[30-12-2018 05:49:52] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:52] ee.DEBUG: -----------------------  
[30-12-2018 05:49:53] ee.DEBUG: -----------------------  
[30-12-2018 05:49:53] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec  
[30-12-2018 05:49:53] ee.DEBUG: STDERR: Error: No such container: services_global-db_1   
[30-12-2018 05:49:53] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:53] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec  
[30-12-2018 05:49:54] ee.DEBUG: STDERR: Error: No such container: services_global-db_1   
[30-12-2018 05:49:54] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: COMMAND: docker cp /tmp/db_exec services_global-db_1:/db_exec  
[30-12-2018 05:49:54] ee.DEBUG: STDERR: Error: No such container:path: services_global-db_1:/   
[30-12-2018 05:49:54] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec  
[30-12-2018 05:49:54] ee.DEBUG: STDERR: Error: No such container: services_global-db_1   
[30-12-2018 05:49:54] ee.DEBUG: RETURN CODE: 1  
[30-12-2018 05:49:54] ee.DEBUG: -----------------------  
[30-12-2018 05:49:54] ee.INFO: ======================== site cleanup start ========================  
[30-12-2018 05:49:54] ee.WARNING: Could not create user auroraho_wp. Please check logs.  
[30-12-2018 05:49:54] ee.WARNING: Initiating clean-up.  

What fixed it for me was to rename the containers using

docker rename services_global-db_1_d078010c6da5 services_global-db_1
docker rename services_global-redis_1_e110b3e62906 services_global-redis_1
docker rename services_global-nginx-proxy_1_c9c4a1226dc0 services_global-nginx-proxy_1

I was then able to create the site normally.

@mram Thanks for the backup scripts. I am looking forward to testing them!


#12

Thanks for the hint about renaming the containers. I didn’t know you could do that. I have not spent much time with docker.


#13

Will this fix my issue too. And if i use this steps will i have to make new changes if there is an update for easyengine again


#14

thanks finally solved the issue. hope i wont need to make any more changes now.


#15

@diamond_sharma @mram @timl

This happened due to a change in docker-compose, which later got reverted back. Please check this issue for more details and solution: https://github.com/EasyEngine/docs/issues/54

These kind of changes have been noted and a better practice of using tags and labels will be used so that this issue never repeats.


"Please make sure port 80 and 443 are free" when they are