# Websites started having issues with SSL certificate

**URL:** <https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991>\
**Category:** Help\
**Created:** [April 2, 2022, 9:56am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991 "2022-04-02T09:56:24Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 9:56am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/1 "2022-04-02T09:56:24Z")

</div>

Hello,

The two websites which are facing the issues are: lanla.pl , shebella.pl

I have been using let's encrypt for years now, 3-4 days ago on 2 of my website strange issues started happening. People who are trying to visit my page are getting SSL certificate errors.

For PC visitors who have avast, they are getting blocked by avast with "URL:blacklist" infection error, people who are trying to browse with android or google chrome mobile are getting errors like: NET:: ERR\_CERT\_AUTHORITY\_INVALID or SSL\_UNTRUSTED

My hosting company is trying to find out what the issue is but they are unable as everything with certificate seems to be fine.

I checked my websites via let's debug, virus total, and many other sites, everything seems smooth:

Cheers,  
Lukasz

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 10:07am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/2 "2022-04-02T10:07:36Z")

</div>

> [@Kukiman0](#):
>
> For PC visitors who have avast, they are getting blocked by avast with "URL:blacklist"

This has nothing to do with your certificate. Avast believes your site is compromised, you have to check that with avast (or clean up your site)

> [@Kukiman0](#):
>
> NET:: ERR\_CERT\_AUTHORITY\_INVALID or SSL\_UNTRUSTED

Your websites look fine to me.

- [SSL Server Test: shebella.pl (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=shebella.pl)
- [https://www.ssllabs.com/ssltest/analyze.html?d=lanla.pl](https://www.ssllabs.com/ssltest/analyze.html?d=lanla.pl)

Something is probably intercepting connections to your website and serving an improper certificate. Please tell us what the name of the CERT\_AUTHORITY in that error is. Click on "more info, show certificate" or something like that.

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [April 2, 2022, 10:08am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/3 "2022-04-02T10:08:26Z")

</div>

> [@Kukiman0](#):
>
> 3-4 days ago on 2 of my website strange issues

Maybe it's a coincidence but:

 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/1/1/113069af6d67b47ad04ad30f9e8d874a544cdeec.jpeg)

Maybe you can report it to them: [False Positive File Form](https://www.avast.com/false-positive-file-form.php).

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 10:35am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/4 "2022-04-02T10:35:17Z")

</div>

> [@\_az](#):
>
> Maybe it's a coincidence but:

Yes, I am aware that the issue started happening 4 days ago, today I sent requests to avast for them to check, it might take up to a few days to receive a response.

> [@9peppe](#):
>
> Something is probably intercepting connections to your website and serving an improper certificate. Please tell us what the name of the CERT\_AUTHORITY in that error is. Click on "more info, show certificate" or something like that.

I am not able to replicate the error on my side, I am asking some other person to try and get it, however after clicking "more info" (number 1 inthe screen) it redirects to a page which shows mutiple ways of fixing it, but not a specific certificate name etc. Just a dozen of links on how to fix certain issues.

When clicking on "advanced" this is number 2 in the screen, it says some default stuff about connection possible being interceptied etc.

 ![xx](https://global.discourse-cdn.com/letsencrypt/original/3X/0/f/0f69b2e9d1e48063ff0aa3a45b0a594ab249779e.png)

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 10:53am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/5 "2022-04-02T10:53:23Z")

</div>

Click on the triangle with the ! (in the address bar) and show us the certificate.

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 11:01am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/6 "2022-04-02T11:01:54Z")

</div>

there you go,  
I can translate it into english if you wish, via some image translator.

 ![z1](https://global.discourse-cdn.com/letsencrypt/original/3X/1/2/1261d560a4b3b9e0935c77a9e037c15d5aec1d9b.png)

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 11:02am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/7 "2022-04-02T11:02:28Z")

</div>

I am attaching it in separate reply as I am restricted to only 1 attachement as a new user

 ![z2](https://global.discourse-cdn.com/letsencrypt/original/3X/1/f/1ff461e4ca5a761d2c8055273480c83a5d5c3b19.png)

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 11:05am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/8 "2022-04-02T11:05:25Z")

</div>

That certificate looks fine at first sight.

What the hell. For some reason your phone does not like it.

Ok, you are serving the short chain. Android versions before 7.1.1 do not like that.

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 11:07am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/9 "2022-04-02T11:07:03Z")

</div>

This is not only my phone, many people reported that it is not working for them both on PCs and mobile phones.

> [@9peppe](#):
>
> k, you are serving the short chain. Android versions before 7.1.1 do not like that.

Is there some way to fix it?

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 11:09am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/10 "2022-04-02T11:09:43Z")

</div>

On Android you can solve it by using the long chain. (Which is the default if you use Certbot)

On computers, you have to make your clients install the ISRG Root X1 root certificate. Or use a recent version of Firefox. Or switch certificate authority for one that has better support for old clients.

> **[Certificate Compatibility - Let's Encrypt](https://letsencrypt.org/docs/certificate-compatibility/)**
>
> The main determining factor for whether a platform can validate Let’s Encrypt certificates is whether that platform trusts ISRG’s “ISRG Root X1” certificate. Prior to September 2021, some platforms could validate our...

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 11:15am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/11 "2022-04-02T11:15:44Z")

</div>

> [@9peppe](#):
>
> On Android you can solve it by using the long chain. (Which is the default if you use Certbot)
> 
> On computers, you have to make your clients install the ISRG Root X1 root certificate. Or use a recent version of Firefox. Or switch certificate authority for one that has better support for old clients.

Seems a little bit too complicated for me, I am using let's encrypt as it is built in via my hosting company in their direct admin panel. I have no clue whether they have all of the certbot updates on the cloud servers they provide. I will forward this reply to them, maybe they can check if they are up to date with everything.

However this is all very strange as none of this issues appeared before 4 days ago, nobody reported anything.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 11:17am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/12 "2022-04-02T11:17:18Z")

</div>

That mainly depends on your clients. The only one your hosting can solve is the android compatibility one.

The rest, they're just too old.

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 11:28am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/13 "2022-04-02T11:28:12Z")

</div>

> [@9peppe](#):
>
> The only one your hosting can solve is the android compatibility one.

The problem is the person who reported the mobile phone issue is using the latest android available 😕

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 11:31am UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/14 "2022-04-02T11:31:41Z")

</div>

Then there is more than one issue. Right now it should only work on Android \>= 7.1.1.

But, if you really are on a blocklist, that will give SSL errors to whoever gets filtered.

---

<div class="post-metadata">

**Author:** ![Kukiman0](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kukiman0/32/59651_2.png) [@Kukiman0](https://community.letsencrypt.org/u/Kukiman0)\
**Post date:** [April 2, 2022, 3:14pm UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/15 "2022-04-02T15:14:10Z")

</div>

thank you sir, I really appreciate it. I already contacted both mcafee and avast, I will update you on the issue as soon as any of them replies to me.

Have a nice weekend 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 2, 2022, 3:14pm UTC](https://community.letsencrypt.org/t/websites-started-having-issues-with-ssl-certificate/174991/16 "2022-05-02T15:14:11Z")

</div>

Closed on May 2, 2022, 3:14pm UTC

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