-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App issue: Poste.io TLS/SSL Cert #1113
Comments
Could you elaborate on this please? |
@coffseducation caprover app domain for poste.io, for example: |
ok, with more exploration in Poste.io docs I found this in its FAQs: Q: I want use my port 80 for reverse proxy (Nginx) A: Poste only needs to use port version: '3'
services:
nginx-proxy:
image: jwilder/nginx-proxy
labels:
com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
container_name: nginx-proxy
restart: unless-stopped
ports:
- "80:80"
- "443:443"
volumes:
- /data/nginx/conf.d:/etc/nginx/conf.d
- /data/nginx/vhost.d:/etc/nginx/vhost.d
- /data/nginx/html:/usr/share/nginx/html
- /data/nginx/certs:/etc/nginx/certs:ro
- /var/run/docker.sock:/tmp/docker.sock:ro
nginx-letsencrypt:
image: jrcs/letsencrypt-nginx-proxy-companion
container_name: nginx-letsencrypt
restart: unless-stopped
volumes:
- /data/nginx/conf.d:/etc/nginx/conf.d
- /data/nginx/vhost.d:/etc/nginx/vhost.d
- /data/nginx/html:/usr/share/nginx/html
- /data/nginx/certs:/etc/nginx/certs:rw
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- NGINX_DOCKER_GEN_CONTAINER=nginx-proxy
- NGINX_PROXY_CONTAINER=nginx-proxy
mailserver:
image: poste.io/mailserver:dev
container_name: mailserver
restart: unless-stopped
ports:
- "25:25"
- "110:110"
- "143:143"
- "587:587"
- "993:993"
- "995:995"
- "4190:4190"
environment:
- [email protected]
- LETSENCRYPT_HOST=mail.poste.io
- VIRTUAL_HOST=mail.poste.io
- HTTPS=OFF
volumes:
- /etc/localtime:/etc/localtime:ro
- /data/nginx/html/.well-known:/opt/www/.well-known
- /data/mailserver:/data How do we handle |
Any suggestion from the original author? @ronaldloyko |
Hello,
While I did read #231 (suggestion comments 1 and 2) and followed them, there is some issues.
HTTPS = OFF
) and map those certs to Poste.io certs, panels would have certs but because Poste.io is a mailserver and I need to connect multiple domains to it some/most apps would decline this cert with this error:So I tried to issue the cert while this option is used and did use Poste.io Let's Encrypt and I got this error:
Note is even if I use CapRover SSL cert and map it because it is for the app name not the hostname of mail server mentioned issue would still be there and I need alt names for other domains and the hostname itself and also I cannot connect the mail server hostname to the app directly I don't know why in this structure:
appname.caproverRoot.name.domain
mail.name.domain
1107 : Verification Failed.
while I do have DNS record pointing to the IP of the server.Also I don't think this is the issue because even Poste.io demo website structure is like this:
demo.poste.io
mail.poste.io
HTTPS = blank
and let Poste.io handle the SSL/TLS certs and remove both(as mentioned in the comment number 1 of the mentioned issue) in the Nginx config of the app, no matter what the app won't run and if I open the domain CapRover/Nginx will show
Nothing is here yet
page.Another problem is, the instruction that shows up after installation of Poste.io, looks like only applies to
HTTPS = OFF
option and no mention about how to handleHTTPS = blank
.I'll appreciate any help,
Regards.
The text was updated successfully, but these errors were encountered: