Closed ttjaden closed 3 years ago
Did you reload your Nginx reverse proxy? The certificate seems to be acquired just fine. But maybe Nginx has not read it yet.
Am 17.01.2021 um 19:38 schrieb ttjaden notifications@github.com:
Prior to placing the issue, please check following: (fill out each checkbox with an X once done)
I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue. I have understood that this bug report is dedicated for bugs, and not for support-related inquiries. I have understood that answers are voluntary and community-driven, and not commercial support. I have verified that my issue has not been already answered in the past. I also checked previous issues. Summary
My system works for years now, but after an dist-upgrade from Ubuntu 16.04 LTS to 18.04 LTS I suddenly have have a Problem with the SSL certificates. When visiting the Web-GUI I See
Subject: autoconfig.oeko-t.de Issuer: R3 Expires on: 17.04.2021 I uses the wrong certificate, because the Web-GUI is called over: mail.oeko-t.de
Logs
I forced an update of the acme docker
docker-compose restart acme-mailcow docker-compose logs --tail=200 -f acme-mailcow which shows
acme-mailcow_1 | Sun Jan 17 19:13:33 CET 2021 - Detecting IP addresses... acme-mailcow_1 | Sun Jan 17 19:13:57 CET 2021 - OK: 2.59.133.82, 0000:0000:0000:0000:0000:0000:0000:0000 acme-mailcow_1 | Sun Jan 17 19:14:00 CET 2021 - Found A record for autodiscover.groeoenlandhof.de: 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:00 CET 2021 - Confirmed A record 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:02 CET 2021 - Found A record for autoconfig.groeoenlandhof.de: 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:02 CET 2021 - Confirmed A record 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:03 CET 2021 - Found A record for autodiscover.oeko-t.de: 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:03 CET 2021 - Confirmed A record 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:03 CET 2021 - Found A record for autoconfig.oeko-t.de: 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Confirmed A record 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Found A record for mail.oeko-t.de: 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Confirmed A record 2.59.133.82 acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Certificate /var/lib/acme/mail.oeko-t.de/cert.pem missing or changed domains 'mail.oeko-t.de autoconfig.groeoenlandhof.de autoconfig.oeko-t.de autodiscover.groeoenlandhof.de autodiscover.oeko-t.de' - start obtaining acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Copying shared private key for this certificate... acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Checking resolver... acme-mailcow_1 | Sun Jan 17 19:14:04 CET 2021 - Resolver OK acme-mailcow_1 | Parsing account key... acme-mailcow_1 | Parsing CSR... acme-mailcow_1 | Found domains: autoconfig.oeko-t.de, autoconfig.groeoenlandhof.de, mail.oeko-t.de, autodiscover.groeoenlandhof.de, autodiscover.oeko-t.de acme-mailcow_1 | Getting directory... acme-mailcow_1 | Directory found! acme-mailcow_1 | Registering account... acme-mailcow_1 | Already registered! acme-mailcow_1 | Creating new order... acme-mailcow_1 | Order created! acme-mailcow_1 | Verifying autoconfig.groeoenlandhof.de... acme-mailcow_1 | autoconfig.groeoenlandhof.de verified! acme-mailcow_1 | Verifying autoconfig.oeko-t.de... acme-mailcow_1 | autoconfig.oeko-t.de verified! acme-mailcow_1 | Verifying autodiscover.groeoenlandhof.de... acme-mailcow_1 | autodiscover.groeoenlandhof.de verified! acme-mailcow_1 | Verifying autodiscover.oeko-t.de... acme-mailcow_1 | autodiscover.oeko-t.de verified! acme-mailcow_1 | Verifying mail.oeko-t.de... acme-mailcow_1 | mail.oeko-t.de verified! acme-mailcow_1 | Signing certificate... acme-mailcow_1 | Certificate signed! acme-mailcow_1 | Sun Jan 17 19:14:36 CET 2021 - Deploying certificate /var/lib/acme/mail.oeko-t.de/cert.pem... acme-mailcow_1 | Sun Jan 17 19:14:36 CET 2021 - Verified hashes. acme-mailcow_1 | Sun Jan 17 19:14:36 CET 2021 - Certificate successfully obtained acme-mailcow_1 | Sun Jan 17 19:14:36 CET 2021 - Found orphaned certificate: autoconfig.oeko-t.de - archiving it at /var/lib/acme/backups/autoconfig.oeko-t.de/ acme-mailcow_1 | Sun Jan 17 19:14:36 CET 2021 - Reloading or restarting services... (1) acme-mailcow_1 | Restarting 9bb16a21c637ade026e8a1a12227a2a57643a0511b042cec0be5fa9ebeba215d... acme-mailcow_1 | command completed successfully acme-mailcow_1 | Restarting 036ee7d57f77f8bb4cbbe3185dd63e5b2b0c2b6ca3d55f76298ec7ab9d1cd033... acme-mailcow_1 | command completed successfully acme-mailcow_1 | Restarting 57de28c7a064ce74cd6fd4f7bd6a00d3299fff25142411095a6edfd3b415c0be... acme-mailcow_1 | command completed successfully acme-mailcow_1 | Sun Jan 17 19:14:44 CET 2021 - Waiting for containers to settle... acme-mailcow_1 | Sun Jan 17 19:14:54 CET 2021 - Certificates successfully requested and renewed where required, sleeping one day Reproduction
Only dist-upgrade from Ubuntu 16.04 to 18.04 After that, the error occurs.
System information
Question Answer My operating system Ubuntu Server 18.04 LTS Is Apparmor, SELinux or similar active? no Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported KVM Server/VM specifications (Memory, CPU Cores) 8 GB, 4 Cores Docker Version (docker version) 20.10.2 Docker-Compose Version (docker-compose version) docker-compose version Reverse proxy (custom solution) Nginx Output of git diff origin/master, any other changes to the code? If so, please post them. diff --git a/data/conf/postfix/main.cf b/data/conf/postfix/main.cf index 840042c3..1d11bdbf 100644 --- a/data/conf/postfix/main.cf +++ b/data/conf/postfix/main.cf @@ -200,3 +200,5 @@ parent_domain_matches_subdomains = debug_peer_list,fast_flush_domains,mynetworks
DO NOT EDIT ANYTHING BELOW
User overrides
+myhostname = mail.oeko-t.de + diff --git a/data/conf/sogo/sogo.conf b/data/conf/sogo/sogo.conf index 78791d58..9cf53bf5 100644 --- a/data/conf/sogo/sogo.conf +++ b/data/conf/sogo/sogo.conf @@ -32,7 +32,7 @@ WOPort = "0.0.0.0:20000"; SOGoMemcachedHost = "memcached";
- SOGoLanguage = English;
- SOGoLanguage = German; SOGoMailAuxiliaryUserAccountsEnabled = YES; SOGoMailCustomFromEnabled = YES; SOGoMailingMechanism = smtp; — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Did you reload your Nginx reverse proxy? The certificate seems to be acquired just fine. But maybe Nginx has not read it yet.
I restartet the nginx-service several times. What I'm wondering about: If I visit https://mail.oeko-t.de/ the webbrowser shows a warning because the the certificate belongs to autodiscover.oeko-t.de and autoconfig.oeko-t.de
Edit: After restarting several times I RELOADED the nginx-service and now it's working again.
Sorry for any inconvenience
Prior to placing the issue, please check following: (fill out each checkbox with an
X
once done)Summary
My system works for years now, but after an dist-upgrade from Ubuntu 16.04 LTS to 18.04 LTS I suddenly have have a Problem with the SSL certificates. When visiting the Web-GUI I See
I uses the wrong certificate, because the Web-GUI is called over: mail.oeko-t.de
Logs
I forced an update of the acme docker
which shows
Reproduction
Only dist-upgrade from Ubuntu 16.04 to 18.04 After that, the error occurs.
System information
docker version
)docker-compose version
)git diff origin/master
, any other changes to the code? If so, please post them.+myhostname = mail.oeko-t.de + diff --git a/data/conf/sogo/sogo.conf b/data/conf/sogo/sogo.conf index 78791d58..9cf53bf5 100644 --- a/data/conf/sogo/sogo.conf +++ b/data/conf/sogo/sogo.conf @@ -32,7 +32,7 @@ WOPort = "0.0.0.0:20000"; SOGoMemcachedHost = "memcached";