# Chromium browsers now showing custom blockpage

**URL:** <https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134>\
**Category:** Help\
**Created:** [November 18, 2021, 5:46pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134 "2021-11-18T17:46:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![oicangi](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/oicangi/32/28200_2.png) [@oicangi](https://discourse.pi-hole.net/u/oicangi)\
**Post date:** [November 18, 2021, 5:46pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/1 "2021-11-18T17:46:48Z")

</div>

## Expected Behaviour:

I added a custom block page following steps I found [here](https://discourse.pi-hole.net/t/customize-block-page/4693) and in some other pages that did the same steps. When I try to access a blocked page through Mozilla, everything works fine, giving me this result:

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/b/0/b0e089d6e1266e929f2d94f0d2148692923e6e3d.png)

## Actual Behaviour:

When I try and use any chromium browser (chrome, edge, etc.) I get this:

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/c/8/c8d0bb80c12d13d4326cc5f31275dfef8b61bd05.png)

## Debug Token:

[Debug token](https://tricorder.pi-hole.net/xdGEHI8W/)

I couldn't find anything about this and I don't know if I did something wrong. Thanks for the help on advance!

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 18, 2021, 6:10pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/2 "2021-11-18T18:10:48Z")

</div>

Custom block pages only work for **http** URL's. Your second example is for an **https** page.

---

<div class="post-metadata">

**Author:** ![oicangi](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/oicangi/32/28200_2.png) [@oicangi](https://discourse.pi-hole.net/u/oicangi)\
**Post date:** [November 18, 2021, 6:41pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/4 "2021-11-18T18:41:06Z")

</div>

you are right... why does this happen? is there some way to have custom block page on websites with HTTPS?

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 18, 2021, 7:01pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/5 "2021-11-18T19:01:23Z")

</div>

> [@oicangi](#):
>
> is there some way to have custom block page on websites with HTTPS?

Not without making a certificate that will work with https sites. This would involve setting up a MITM on your Pi with a trusted cert, etc. Not recommended.

The block page option will likely be removed in a future Pi-hole version due to it's very limited usefulness. Only a very few sites on the internet use http.

---

<div class="post-metadata">

**Author:** ![oicangi](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/oicangi/32/28200_2.png) [@oicangi](https://discourse.pi-hole.net/u/oicangi)\
**Post date:** [November 19, 2021, 2:46pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/6 "2021-11-19T14:46:40Z")

</div>

ok... thank you for your help, sorry it was such a noob question

---

<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:** [December 10, 2021, 2:47pm UTC](https://discourse.pi-hole.net/t/chromium-browsers-now-showing-custom-blockpage/51134/7 "2021-12-10T14:47:14Z")

</div>

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