unable to set new WP website - nginx-proxy container not starting
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- backend, cli, infrastructure
Línea de trabajo
Comienza reproduciendo el comando proporcionado ee site create e inspecciona los registros del contenedor nginx-proxy, especialmente /etc/nginx/nginx.conf en la línea 42 y la zona proxy_cache desconocida indicada. Se considera completado cuando el contenedor nginx-proxy sigue ejecutándose y la configuración del sitio finaliza sin el error de inicio repetido.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
This issue tracker is only for issues related to EasyEngine. Please use http://community.rtcamp.com/c/easyengine for support questions.
If you feel the issue is a EasyEngine specific issue, please attach the output of the following commands.
System Information
- ee cli info
+-------------------+-------------------------------------------------------------------------+
| OS | Linux 5.4.0-1040-gcp #43-Ubuntu SMP Fri Mar 19 17:49:48 UTC 2021 x86_64 |
| Shell | /bin/bash |
| PHP binary | /usr/bin/php7.3 |
| PHP version | 7.3.27-9+ubuntu20.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 | /home/harshal |
| EE packages dir | |
| EE global config | /opt/easyengine/config/config.yml |
| EE project config | |
| EE version | 4.1.5 |
+-------------------+-------------------------------------------------------------------------+ - lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal - docker version
Client: Docker Engine - Community
Version: 20.10.5
API version: 1.41
Go version: go1.13.15
Git commit: 55c4c88
Built: Tue Mar 2 20:18:20 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.5
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: 363e9a8
Built: Tue Mar 2 20:16:15 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
ISSUE
- after installing & setup new website with following command
sudo ee site create www.maahi.ca
--type=wp
--dbhost=...
--dbuser=maa****
--dbpass=******
--dbname=maahi_soft_db
[email protected]
--admin-user=admin
--admin-pass=*****
--dbprefix=mss_
--cache
--php=latest
--with-local-redis
--ssl=le
--proxy-cache=on
--proxy-cache-max-size=1024m
--proxy-cache-max-time=14400s
[email protected]
--force
12bad5ef40dc easyengine/nginx-proxy:v4.1.4 "/app/docker-entrypo…" About a minute ago Restarting (0) 3 seconds ago services_global-nginx-proxy_1
nginx-proxy container is showing up as restarting...tried multiple things like disabling service or restarting container but nothing worked. while showing up log seeing below error: (docker logs > for above container)
harshal@mss-hp-vm:~$ sudo docker logs 12bad5ef40dc
WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used for now while a new one
is being generated in the background. Once the new dhparam.pem is in place, nginx will be reloaded.
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
dockergen.1 | 2021/03/29 22:17:26 Generated '/etc/nginx/conf.d/default.conf' from 1 containers
dockergen.1 | 2021/03/29 22:17:26 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:26 Watching docker events
dockergen.1 | 2021/03/29 22:17:26 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:32 Received event start for container 41ddf46f13e5
dockergen.1 | 2021/03/29 22:17:32 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:34 Received event die for container 41ddf46f13e5
dockergen.1 | 2021/03/29 22:17:34 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:39 Received event start for container 8dc533a573b0
dockergen.1 | 2021/03/29 22:17:39 Received event start for container 23198f4ea38b
dockergen.1 | 2021/03/29 22:17:39 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:39 Error inspecting container: f5024273c58e03e3c32e15ccdac81c1793626024c729430c11e1ff719b7f296e: No such container: f5024273c58e03e3c32e15ccdac81c1793626024c729430c11e1ff719b7f296e
dockergen.1 | 2021/03/29 22:17:39 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:40 Received event start for container f5024273c58e
dockergen.1 | 2021/03/29 22:17:40 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
dockergen.1 | 2021/03/29 22:17:40 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:41 Received event start for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:41 Received event die for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:41 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2021/03/29 22:17:41 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:43 Received event start for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:43 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2021/03/29 22:17:43 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:43 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2021/03/29 22:17:43 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:43 Received event die for container f5024273c58e
dockergen.1 | 2021/03/29 22:17:43 Received event die for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:43 Received event stop for container f5024273c58e
dockergen.1 | 2021/03/29 22:17:43 Received event stop for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:45 Received event start for container f5024273c58e
dockergen.1 | 2021/03/29 22:17:45 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
dockergen.1 | 2021/03/29 22:17:45 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:45 Received event start for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:17:45 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2021/03/29 22:17:45 Running 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:45 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:45 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:45 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:45 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:51 Received event die for container 8dc533a573b0
dockergen.1 | 2021/03/29 22:17:51 Received event stop for container 8dc533a573b0
dockergen.1 | 2021/03/29 22:17:51 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:52 Received event start for container 8dc533a573b0
dockergen.1 | 2021/03/29 22:17:52 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:17:52 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
Generating DH parameters, 2048 bit long safe prime, generator 2
This is going to take a long time
dhparam generation complete, reloading nginx
dockergen.1 | 2021/03/29 22:18:23 Received event die for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:18:24 Received event stop for container 19abbb6f9c14
dockergen.1 | 2021/03/29 22:18:24 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
dockergen.1 | 2021/03/29 22:18:24 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
dockergen.1 | 2021/03/29 22:18:25 Received event start for container ced5de09eab5
dockergen.1 | 2021/03/29 22:18:25 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2021/03/29 22:18:25 Running 'nginx -s reload'
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to dockergen.1
forego | sending SIGTERM to nginx.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to dockergen.1
forego | sending SIGTERM to nginx.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to nginx.1
forego | sending SIGTERM to dockergen.1
Custom dhparam.pem file found, generation skipped
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
nginx.1 | nginx: [emerg] "proxy_cache" zone "www-maahi-ca" is unknown in /etc/nginx/nginx.conf:42
forego | starting nginx.1 on port 5200
forego | sending SIGTERM to dockergen.1
forego | sending SIGTERM to nginx.1
- Lenguaje dominante
- PHP
- Estrellas
- 2.2k
- Forks
- 422
- Merge medio
- 2 d 3 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de EasyEngine/easyengine
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
EasyEngine/easyengine#1427 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
EasyEngine/easyengine#1893 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 38/100
EasyEngine/easyengine#1888 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
How to enable page cache?Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
EasyEngine/easyengine#1875 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
EasyEngine/easyengine#1810 · 2 comentarios · 4 reacciones ·
Los mantenedores suelen responder en 1 día
Todos los issues de EasyEngine/easyengine
Issues similares
-
sync-en
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 4 días
-
Перевод устарел
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
bug
Dificultad 2/5 Medio día Aptitud para principiantes 76/100
m3ue/m3u-editor#1604 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
femiwiki/docker-mediawiki#1497 ·
Los mantenedores suelen responder en 1 día