Closed Mr5quid closed 6 years ago
Hi. Your compose file seems to lack a way to make the letsencrypt container aware of the nginx-proxy container ID. Please see https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/wiki/Docker-Compose#getting-containers-ids
Hi @buchdag and thank you for your answer. That's right I was missing something. My first version had the label though but it still didn't go very well.
Either way, I purged up all images, containers and volumes and started again with that compose file to which I added the NGINX_PROXY_CONTAINER=nginx-proxy
env var and it's now up and running ! It's really great.
By the way, thank you for bringing these awesome images on ARM architectures. It made my day when I found it.
Hi,
I'm working on a server setup on my Odroid XU4 (armv7 32bits) running ArchArm which includes Nextcloud-fpm with an nginx web server, a postgres container and of course the letsencrypt-nginx-proxy-companion bundled with the nginx-proxy from this repo. I'm pretty new at docker so I basically did a mix of the Nextcloud Docker installation guide's docker-compose file and the docker-compose for the 2-containers-setup from this repo:
And so it started, I had openssl eating up two cpu threads for quite a while and then it finished but since then my server is only accessible through HTTP on port 80. There's no trace of an SSL cert.
Checking up the docker-compose logs I first have this error at the beginning :
nginx-proxy-le | 2018/07/26 21:30:23 Error: nginx-proxy container dc2a0f4851cd5a2451a53b8e395f84d89cb677b2bf7d7184f4785216983fa139 isn't running.
The complete logs are available here : https://bin.disroot.org/?8351bc21b6ffc09b#Hj320WtqokB69t212DdSB9EOjQf4B4yjVdDNlpfFaR4=
When idle it pretty much loops on that.
Like I said I'm running ArchArm on the Odroid XU4 with an armv7l architecture.
Any help would be greatly appreciated ! I'm very excited about this setup for which I plan to migrate my non-dockerized XMPP server to soon.