Error with Letencrypt Certified !

Issue #703 closed
Angel Cantu created an issue

Hi.

Ima using 2.1.11 FREE # 449 from hub docker, I can receive and I cand connect to de inbox via imap or pop, but I have problems to SEND from submission port (587) 😞

  1. Error when I try to make the certificated:

This is my docker-compose:

version: '2'
services:
  proxy:
    container_name: proxy
    image: jwilder/nginx-proxy
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - /home/admin/nginx/conf.d:/etc/nginx/conf.d
      - /home/admin/certs:/etc/nginx/certs:ro
      - /home/admin/nginx/vhost.d:/etc/nginx/vhost.d:rw
      - /home/admin/nginx/html:/usr/share/nginx/html:rw
    networks:
      - mired
    labels:
      - com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy
  letsencrypt:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: certs
    restart: always
    volumes:
      - /home/admin/certs:/etc/nginx/certs:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
    volumes_from:
      - proxy:rw
    environment:
      - NGINX_DOCKER_GEN_CONTAINER=nginx
      - NGNIX_PROXY_CONTAINER=nginx
    networks:
      - mired
  mail:
    image: analogic/poste.io
    container_name: mail
    restart: always
    mem_limit: 400m
    ports:
      - "25:25"
      - "110:110"
      - "143:143"
      - "465:465"
      - "587:587"
      - "993:993"
      - "995:995"
      - "4190:4190"
    expose:
      - "80"
      - "443"
    volumes:
      - /usr/share/zoneinfo/America/Matamoros:/etc/localtime:ro
      - /home/admin/mail:/data:rw
      - /home/admin/nginx/html/.well-known:/opt/www/.well-known:rw
    environment:
      - HTTPS=OFF
      - VIRTUAL_HOST=mail.crver.net,smtp.crver.net
      - LETSENCRYPT_HOST=mail.crver.net,smtp.crver.net
      - LETSENCRYPT_EMAIL=soporte@sie-group.net
    networks:
      - mired

networks:
  mired:

Comments (3)

  1. Foddy

    For some reasons we also have this error with Apple Mail on MacOS Catalina (which is the newest OS right now). We bought a certificate by SECTIGO for our domain. When downgrading to Poste.io 2.1.11 everything works as before. With 2.2.0 in (PRO) all the TLS Ports are closed – according to the connection diagnostics in the admin area).

    Do we need to change some settings or certificates after upgrading to 2.2.X?

  2. Log in to comment