Removing a certificate for a domain

Hi, I am completely new to SSL certificates. The former admin of our server added a let’s encrypt certificate to my domain buildenvironment.com. Now I redirected this domain to nheeren.github.io. However, when using https://, my web browser will complain about the certificate.

What steps do I need to perform to “liberate” this domain and make this redirect work properly. In the future I intend to add an SSL certificate again. Any help would be greatly appreciated!

My domain is:
https://www.buildenvironment.com

I ran this command:
not sure

It produced this output:
n/a

My web server is (include version):
129.132.117.28

The operating system my web server runs on is (include version):
4.4.0-151-generic #178-Ubuntu

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):
Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.31.0

Hi @nheeren

there is no active Letsencrypt certificate. Check https://check-your-website.server-daten.de/?q=buildenvironment.com

There is a Comodo certificate

CN=chk.me, OU=PositiveSSL Multi-Domain, 
OU=Domain Control Validated
	16.08.2017
	16.08.2020
expires in 340 days	
chk.me, short.infomaniak.ch, short.infomaniak.com - 3 entries

There are a lot of older Letsencrypt certificates. But none of these is sent by your domain. Looks like the certificate of your hoster is used.

Thank you very much! I guess I am in the wrong place then… :blush:
It is odd, because there is definitely a certificate installed and I see it when I do certbot certificates.

Certificate Name: buildenvironment.com
    Domains: buildenvironment.com
    Expiry Date: 2019-10-29 19:54:48+00:00 (VALID: 48 days)
    Certificate Path: /etc/letsencrypt/live/buildenvironment.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/buildenvironment.com/privkey.pem

I will reach out to my hoster. Should I remove the certificates from our server however?

These are only the created certificates. Not used certificates - this is completely different.

You should use that certificate -> that would fix your error.