Copy to Postfix caused ssl problem on webmin, can't access to webmin anymore

6 posts / 0 new
Last post
#1 Mon, 06/25/2018 - 03:07

Copy to Postfix caused ssl problem on webmin, can't access to webmin anymore


Today I tried something which I saw on another topic here and in ssl manager of a domain which is secured with a ssl certificate I clicked copy to postfix but now I cannot access in the panel anymore.

Secure Connection Failed

An error occurred during a connection to SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Backuping via virtualmin is really easy using ssh but Im tired with reinstallations all the time when something goes wrong,so if anyone can guide how to fix this problem would be great.

I tried to edit a line in etc/webmin/miniserv.conf I changed the ssl=1 to 0 and restarted webmin via command line but still having the same problem.


Mon, 06/25/2018 - 03:18

Okay looks like the real error is: Error code: SSL_ERROR_BAD_CERT_DOMAIN I'm using a promo ssl from comodo bought in namecheap so domain is passing all the steps in sslchecker sites or ssllabs.

Firefox says: Unable to communicate securely with peer: requested domain name does not match the server’s certificate.

HTTP Strict Transport Security: true HTTP Public Key Pinning: false Certificate chain: -----BEGIN CERTIFICATE-----

So my domain is when I check this or I see the above errors. Not sure what to do here!

Mon, 06/25/2018 - 09:32


After changing "ssl=0" and restarting the Webmin service, what you'd need to do at that point is connect to Webmin using HTTP rather than HTTPS.

From there, you could copy a different SSL certificate into Webmin.

Note that in regards to the SSL certificate -- you'd want to ensure you are connecting to one of the domain name(s) that is listed within the SSL certificate.


Mon, 06/25/2018 - 09:35

Hi, I reissued the certificate using instead and now the webmin is secured but domain name no. Using ssl=0 also enabled the access to make the configurations yes but looks like if I add another cert to the domain name it will break again the other one.

However I listed the domains with www or just as when I created the signing request but looks like comodo doesn't allow all the domains in cert.

So the buttons copy to postfix or webmin didn't work for me. my mail server is still insecured but mailing works I can send or recieve

Mon, 06/25/2018 - 09:41

Im not sure if I create a sub server and if I assign a new ssl certificate does the job or not because the is also the mx record name in dns records.

Mon, 06/25/2018 - 10:47

I created a sub server called and gave a new ssl cert installed also roundcube to it everything works fine I did what I needed more than one year with virtualmin Im loving everyday everything works perfect for now.


Topic locked