# Discord - cert problem or pi-hole blocking?

**URL:** <https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538>\
**Category:** Community Help\
**Created:** [February 2, 2025, 7:50pm UTC](https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538 "2025-02-02T19:50:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![snic](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/snic/32/45303_2.png) [@snic](https://discourse.pi-hole.net/u/snic)\
**Post date:** [February 2, 2025, 7:50pm UTC](https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538/1 "2025-02-02T19:50:42Z")

</div>

**The issue I am facing:**

Discord has suddenly started being blocked at home, across all devices that use pi-hole as the DNS.

Web, app, multiple PCs. It will work fine if I use say, the Google DNS 8.8.8.8, but not via my local pi-hole.

I've whitelisted discord.com discordapp.com but no better.

When I go to browse discord.com on the web, I get a invalid cert error. I've looked at the cert details from home, and at work (where discord.com works) and I notice that the certifcate is different, which I find odd.

The discord.com cert at home is issued by Cisco, at work, it is by Google Trust Services.

**What I have changed since installing Pi-hole:**

Nothing that I can think of. I've updated pi-hole, after the issue, in case there was something that would resolve it. Updated gravity too. No change to the behaviour.

So, should a cert change between different internet providers/PCs?

Has anyone else got issues with discord on pi-hole lately?

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [February 3, 2025, 8:19am UTC](https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538/2 "2025-02-03T08:19:40Z")

</div>

> [@snic](#):
>
> When I go to browse discord.com on the web, I get a invalid cert error.

What's the exact error message you see?

TLS negotiations could only commence after successful DNS resolution, so I doubt your observation would be related to blocking, unless you'd be blocking OCSP responder domains used to check certificate validity of a variety specifically used by Edge browsers.

> [@snic](#):
>
> So, should a cert change between different internet providers/PCs?

I wouldn't expect that, but it's not impossible either.  
Authoritative DNS servers (as queried by your Pi-hole's upstreams) may answer requests with different IP addresses based on a requestor's IP, and in theory, certificates for different IPs could well be issued by different CAs.

Would domains resolve to different IPs when using Pi-hole vs. 8.8.8.8?  
What public resolvers are you using as Pi-hole's upstreams?

---

<div class="post-metadata">

**Author:** ![snic](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/snic/32/45303_2.png) [@snic](https://discourse.pi-hole.net/u/snic)\
**Post date:** [February 3, 2025, 8:31am UTC](https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538/3 "2025-02-03T08:31:55Z")

</div>

Thanks for the reply.

I did a little more digging and found that it had something to do with Cisco Umbrella Security and a reference to OpenDNS. I forgot I had set OpenDNS familyshield as the upstream DNS, I switched to OpenDNS and still the same problem. But when I set as Google upstream, discord is back to normal.

So I think the problem was that OpenDNS has implemented some discord blocking.

So yeah, your query about the upstream server was right.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [February 24, 2025, 8:32am UTC](https://discourse.pi-hole.net/t/discord-cert-problem-or-pi-hole-blocking/75538/4 "2025-02-24T08:32:02Z")

</div>

Closed on February 24, 2025, 8:32am UTC

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