MailInABox - Using a Self Signed Certificate After LetsEncrypt is Removed


#1

I have been playing around with Mail-in-a-box and also asked for a certificate, automatic from the MIAB software.

The MIAB for the domaines have now been deleted, but the certificate still works and hinders me from getting to the normal http website.

How do I cancel/delete/revoke my certificates for renovawel.com and care2cure.com? (on the same cert.)


#2

The pure existence of the certificate cannot prevent you from visiting the HTTP version of a site, and revoking it won’t change anything about the HTTP version.

Both domains don’t resolve for me, so it looks like you have a DNS problem, unrelated to Let’s Encrypt.


#3

In addition to what @fefrei said, revoking the certificate is almost never the right answer. The only time that’s called for is if you believe your private key has been compromised.


#4

Sorry, care2cure.com do now…but resolve to https://care2cure.com with NET::ERR_CERT_AUTHORITY_INVALID

---- Til to, 20 apr. 2017 13:38:51 +0200 Felix Freiberger <letsencrypt@discoursemail.com> skrev ----

        fefrei 

April 20

The pure existence of the certificate cannot prevent you from visiting the HTTP version of a site, and revoking it won’t change anything about the HTTP version.
vitamate:renovawel.com and care2cure.com
Both domains don’t resolve for me, so it looks like you have a DNS problem, unrelated to Let’s Encrypt.

 Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.


#5

maybe figured out that a self signed certificate is in use (which will lead to understanding that no matter how many certificates you revoke the problem will still be there) and read some documentation?

It seems like MailInABox will create a self signed certificate on installation so the admin interfaces are secure and prefers secure protocols (hence the self signed certificate)

Review the MailInABox documentation or post on MailInABox forums on how to remove the HTTPS redirects as this should be there somewhere :smiley:


#6

Tks for pointing me in the right direction…problem solved:)

/Peer

---- Til to, 20 apr. 2017 15:08:16 +0200 Andrei Hawke <letsencrypt@discoursemail.com> skrev ----

        ahaw021 

April 20

maybe figured out that a self signed certificate is in use (which will lead to understanding that no matter how many certificates you revoke the problem will still be there) and read some documentation?
It seems like MailInABox will create a self signed certificate on installation so the admin interfaces are secure and prefers secure protocols (hence the self signed certificate)
Review the MailInABox documentation or post on MailInABox forums on how to remove the HTTPS redirects as this should be there somewhere

 Visit Topic or reply to this email to respond.

In Reply To
vitamate
April 20

Sorry, care2cure.com do now…but resolve to https://care2cure.com with NET::ERR_CERT_AUTHORITY_INVALID ---- Til to, 20 apr. 2017 13:38:51 +0200 Felix Freiberger <letsencrypt@discoursemail.com> skrev ---- fefrei April 20 The pure existence of the certificate cannot prevent yo…
Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.


#7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.