# Splash screen stuck until hard refresh

**URL:** <https://meta.discourse.org/t/splash-screen-stuck-until-hard-refresh/261206>\
**Category:** Product Support\
**Created:** [April 10, 2023, 4:16pm UTC](https://meta.discourse.org/t/splash-screen-stuck-until-hard-refresh/261206 "2023-04-10T16:16:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [April 10, 2023, 5:11pm UTC](https://meta.discourse.org/t/splash-screen-stuck-until-hard-refresh/261206/4 "2023-04-10T17:11:07Z")

</div>

> [@yanokwa](#):
>
> For this server in question, there is no reverse proxy

> [@yanokwa](#):
>
> I suppose the CDN could be doing some proxying?

This is literally the job of the CDN, so yes, you need to make sure that the correct end user IP is maintained through the request chain.

I’m guessing you haven’t done that, and all of the requests from the CDN are being tallied against the request rate limit of the CDN POPs rather than the end users.

![image](https://global.discourse-cdn.com/meta/optimized/4X/3/f/a/3fa8bffcd056f882ed45bfd8f050d71555ad0921_2_690x24.png)

You can see the CDN is returning the 429 here, but you’ll need to investigate your specific setup to determine who is making the decision to return that error (i.e. the proxy or the real server).

---

_[View the full topic](https://meta.discourse.org/t/splash-screen-stuck-until-hard-refresh/261206)._