Obtaining CA Certs

DocFraggle

Not if you configure it correctly… the above URL doesn’t get proxied to mailcow

Dvalin21

Any other ideas? Right now I have it down, will bring back up shortly. I don’t know if its the certs im using or the naming scheme or what. It just fails each time

DocFraggle

When the ACME client is trying to issue a certificate it creates a file on your mailcow server. Letsencrypt then tries to access this file, which in your case isn’t possible because your reverse proxy doesn’t proxy

http://autoconfig.houseofmanns.com/.well-known/acme-challenge/rOEn6gTtsqkr8g0HbmDlcni1SjTkYB7JeKoqP8Ztx3U

(The example from your log above)

As long as you don’t fix or get rid of your reverse proxy it won’t work

Dvalin21

DocFraggle
So how should I fix my proxy? I have my domain attached, but don’t have a proxy for the ip of the mailcow. So not sure what else I could do.

Dvalin21

The instructions says that if your using a reverse proxy, that you should use 127.0.0.1 for the binding in the env. But when I tried that, I was never able to access the web interface.

DocFraggle

Dvalin21 The instructions says that if your using a reverse proxy, that you should use 127.0.0.1 for the binding in the env.

Yes, that’s if you use a local reverse proxy running directly on the mailcow host.
If you use Cloudflare you have to bind to you external IP.
I don’t have the slightest idea about how to configure Cloudflare though…

Dvalin21

DocFraggle

So good knews, I was able to get the cert to work…….now I can’t delete emails….sigh. I removed my domain from cloudflare, but I am behind npm. I didn’t have to use the 127.0.0.1 in the binding.

Update: Restarted container, all is well.

Fix

Downloaded certs from NPM.

Fullchain,pem = cert.pem
Permission: 644
Privkey.pem = key.pem
Permission: 600

Disabled Letsencrypted
Verify IP
Verify HTTP

Setup dns as suppose to.

« Previous Page