# Custom domain SOS - Cloudflare issue

**URL:** <https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118>\
**Category:** Report a Bug\
**Created:** [January 27, 2024, 7:32am UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118 "2024-01-27T07:32:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Evgeny1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/evgeny1/32/68231_2.png) [@Evgeny1](https://community.glideapps.com/u/Evgeny1)\
**Post date:** [January 27, 2024, 7:32am UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118/1 "2024-01-27T07:32:29Z")

</div>

Hey folks,

I’ve had my custom domain configured, and all worked well. Until this morning I tried accessing my app using the custom domain and saw this:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/0/309d7540c95b86dd656d36084f8cf8ca487c5379.jpeg)

Domain configured correctly:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/f/af8c6e1371d8e627d95589056ea2429089920d32.jpeg)

Cloudflare is configured correctly - DNS only, no proxy.

Any idea what could be wrong?

As it stands, the custom domain is unusable. And it broke overnight - I did not change any settings on either the glide’s side or the Cloudflare’s side…

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 27, 2024, 4:34pm UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118/2 "2024-01-27T16:34:35Z")

</div>

Escalating this to the team for investigation.

In the meantime, would using the default, non-custom app subdomain work as a fallback?

---

<div class="post-metadata">

**Author:** ![Evgeny1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/evgeny1/32/68231_2.png) [@Evgeny1](https://community.glideapps.com/u/Evgeny1)\
**Post date:** [January 27, 2024, 4:47pm UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118/3 "2024-01-27T16:47:25Z")

</div>

Andy - yes, but a very temporary fallback - seeing as we’re linking to the custom domain everywhere.

Thank you for escalating. Please ask then to prioritise - we’ve followed the instructions to the letter and everything was working fine from November.

Until now (we haven’t changed a thing).

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 27, 2024, 8:40pm UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118/4 "2024-01-27T20:40:51Z")

</div>

Understood! I sent you a DM.

Edit: Looks like we’ve found the source I’m closing up this thread as it’s a domain-specific issue with Cloudflare.

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 29, 2024, 5:41pm UTC](https://community.glideapps.com/t/custom-domain-sos-cloudflare-issue/70118/5 "2024-01-29T17:41:42Z")

</div>