• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Question Letsencrypt and mailman

WielM

New Pleskian
I added mailman to one of my domains. Doing so creates a url called lists.my.domain. This url does not show up in the domain's subdomain overview. The domain uses a LetsEncrypt certificate to get https support. The certificate has wildcard set, but 'lists.my.domain' does not use it. The Digicert Certificate Installation checker shows that lists uses "Subject: E=[email protected], CN=Plesk" in stead of my subdomain name. When I try to access lists.my.domain/mailman/admindb/<listname> the browsers says:

Your connection is not private​

and the https is not valid. It doesn't even let me enter the mailman site.

How can I secure the Mailman pages with the Letsencrypt certificate of the main domain?

Plesk Obsidian on Ubuntu 18.04.4 LTS
 
There is an existing feature request in for this... I suggest that you up-vote this:

There's an existing user solution, but I'd much rather that Plesk implement something that works for all and is supported. This is a level or two of messing about with server configuration above where I'm prepared to play.
 
Back
Top