# R3 not trusted on iphone safari

**URL:** <https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022>\
**Category:** Help\
**Created:** [February 18, 2023, 8:54am UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022 "2023-02-18T08:54:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![khurramanis](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@khurramanis](https://community.letsencrypt.org/u/khurramanis)\
**Post date:** [February 18, 2023, 8:54am UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/1 "2023-02-18T08:54:40Z")

</div>

I have installed Let's Encrypt's SSL for my website using Plesk auto generate and install SSL feature.  
It's working on android/chrome, windows but giving error (Not trusted) on iPhone.  
What is missing or what do I need to do?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [February 18, 2023, 9:35am UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/2 "2023-02-18T09:35:50Z")

</div>

Hi @khurramanis, and welcome to the LE community forum 🙂

If the iPhone O/S can be updated, then that might correct the problem.  
If not, you might do better by having Plesk request a cert from another (free) CA.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [February 18, 2023, 9:59am UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/3 "2023-02-18T09:59:27Z")

</div>

Take a look at this compatibility list

> **[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...

if that iphone should be compatible please provide more information and we can help you

=======================================

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [crt.sh | example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

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

---

<div class="post-metadata">

**Author:** ![khurramanis](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@khurramanis](https://community.letsencrypt.org/u/khurramanis)\
**Post date:** [February 18, 2023, 10:49am UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/4 "2023-02-18T10:49:55Z")

</div>

My domain is: [meatonwheel.com](http://meatonwheel.com)

My web server is (include version): Plesk (Windows Hosting)

The operating system my web server runs on is (include version): windows

My hosting provider, if applicable, is: [creativeon.com](http://creativeon.com)

I can login to a root shell on my machine (yes or no, or I don't know): No (shared web hosting)

---

<div class="post-metadata">

**Author:** ![khurramanis](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@khurramanis](https://community.letsencrypt.org/u/khurramanis)\
**Post date:** [February 18, 2023, 1:32pm UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/5 "2023-02-18T13:32:34Z")

</div>

Thank you for your support. My issue has been resolved. Probably it was client's browser cache issue.  
Thanks

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [February 18, 2023, 1:32pm UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/6 "2023-02-18T13:32:46Z")

</div>

You are using a Sectigo cert. Not Let's Encrypt  
[https://decoder.link/sslchecker/meatonwheel.com/443](https://decoder.link/sslchecker/meatonwheel.com/443)

you will need to contact them about compatibility issues

The Let's Encrypt cert you got earlier did not have your www subdomain in it. That could be a reason for Sarari error message

---

<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:** [March 20, 2023, 1:33pm UTC](https://community.letsencrypt.org/t/r3-not-trusted-on-iphone-safari/193022/7 "2023-03-20T13:33:34Z")

</div>

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