Git Product home page Git Product logo

multiarch-letsencrypt-nginx-proxy's Introduction

This repository is archived

As of 13/04/2021, all components of the nginx-proxy stack are available as multi arch images from Dockerhub. This repository isn't needed anymore and won't receive further updates, issues or pull requests.

For Amazon Linux 1 or 2, CentOS 7 or 8, Debian stable without debian-backports, Raspbian stable, Ubuntu 14.04 or earlier, and Windows users, please be aware of this issue with out-of-date libseccomp and Alpine >= 3.13, and this workaround for Debian based OSes.

nginx-proxy with letsencrypt-nginx-proxy-companion on armhf and arm64

This repo provide a simplified way to run up to date nginx-proxy stack with Let's Encrypt support on non amd64 architectures.

It requires Docker 17.05+ and docker-compose to run.

Usage:

  • git clone https://github.com/buchdag/multiarch-letsencrypt-nginx-proxy

Depending on which setup you want, either

  • cd multiarch-letsencrypt-nginx-proxy/nginx-proxy-2containers

or

  • cd multiarch-letsencrypt-nginx-proxy/nginx-proxy-3containers

  • docker-compose up -d

Please note that on low end ARM devices, container build will take a while and DH parameters generation by letsencrypt-nginx-proxy-companion might take even longer.

Certificate issuance was successfully tested on Scaleway C1 and ARM64-2GB servers.

The two multi-stage Dockerfiles will produce a build container that won't be automatically cleaned afterwards. You can remove it with docker image prune --filter label=stage=intermediate.

multiarch-letsencrypt-nginx-proxy's People

Contributors

buchdag avatar unicod3 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

multiarch-letsencrypt-nginx-proxy's Issues

This image abnormally uses the CPU after 3600 seconds.

The process called letsencryt-service is abnormally using CPU.
After rebooting 3600 s is working normally, but after that the CPU has been used abnormally.
I am using it with armhf. (Scaleway C1)
What is the problem?

Are you mining anyway?

no live upstreams while connecting to upstream

Hello,

i installed the 2 Container Version and made everything as described, but i get the following error message:

2019/08/20 18:13:10 [error] 212#212: *26 no live upstreams while connecting to upstream, client: 86.175.42.181, server: container.mydomain.de, request: "GET / HTTP/2.0", upstream: "http://container.mydomain.de/", host: "container.mydomain.de"

The SSL signing worked as expected.

This are my settings in the container which i want to reach over a SSL signed Subdomain:

version: "3"
services:
  container:
    image: container-image
    container_name: 'container'
    environment:
      TZ: 'Europe/Berlin'
      PGID: '1000'
      PUID: '1000'
      VIRTUAL_HOST: 'container'
      VIRTUAL_PORT: '6789'
      LETSENCRYPT_HOST: 'container.mydomain.de'
      LETSENCRYPT_EMAIL: '[email protected]'
    ports:
      - "6789:6789"
    volumes:
      - /etc/container:/config
    restart: unless-stopped
    networks:
      - container

The Subomain Website shows me:
502 Bad Gateway


nginx/1.13.12

Is there any failure in my configuration?

Greetings

Daniel

"Error: nginx-proxy container isn't running" on Nextcloud setup

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:

version: '3'

services:
  db:
    image: postgres
    restart: always
    volumes:
      - db:/var/lib/postgresql/data
    env_file:
      - db.env

  app:
    image: nextcloud:fpm
    restart: always
    volumes:
      - nextcloud:/var/www/html
    environment:
      - POSTGRES_HOST=db
    env_file:
      - db.env
    depends_on:
      - db

  web:
    build: ./web
    restart: always
    volumes:
      - nextcloud:/var/www/html:ro
    environment:
      - VIRTUAL_HOST=cloud.example.org
      - LETSENCRYPT_HOST=cloud.example.org
      - [email protected]
    depends_on:
      - app
    networks:
      - proxy-tier
      - default

  nginx-proxy:
    build: ./nginx-proxy
    image: nginx-proxy
    container_name: nginx-proxy
    restart: always
    ports:
      - 80:80
      - 443:443
    volumes:
      - vhost.d:/etc/nginx/vhost.d
      - html:/usr/share/nginx/html
      - certs:/etc/nginx/certs:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - dhparam:/etc/nginx/dhparam
      - conf:/etc/nginx/conf.d
    networks:
      - proxy-tier

  letsencrypt:
    build: ./letsencrypt-nginx-proxy-companion
    image: letsencrypt-nginx-proxy-companion
    container_name: nginx-proxy-le
    restart: always
    volumes:
      - vhost.d:/etc/nginx/vhost.d
      - html:/usr/share/nginx/html
      - certs:/etc/nginx/certs:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - dhparam:/etc/nginx/dhparam
      - conf:/etc/nginx/conf.d
    networks:
      - proxy-tier
    depends_on:
      - nginx-proxy

volumes:
  db:
  nextcloud:
  vhost.d:
  html:
  certs:
  dhparam:
  conf:

networks:
  proxy-tier:

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.

# docker-compose version
docker-compose version 1.22.0, build unknown
docker-py version: 3.4.1
CPython version: 3.6.6
OpenSSL version: OpenSSL 1.1.0h  27 Mar 2018

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.