# Just updated 2.4.4, getting 429 errors in Firefox + Chromium

**URL:** https://meta.discourse.org/t/just-updated-2-4-4-getting-429-errors-in-firefox-chromium/153064
**Category:** Support
**Created:** [May 28, 2020, 7:58am UTC](https://meta.discourse.org/t/just-updated-2-4-4-getting-429-errors-in-firefox-chromium/153064 "2020-05-28T07:58:29Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![dachary](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dachary/32/119731_2.png) [@dachary](https://meta.discourse.org/u/dachary)
#### Post date: [May 28, 2020, 7:58am UTC](https://meta.discourse.org/t/just-updated-2-4-4-getting-429-errors-in-firefox-chromium/153064/1 "2020-05-28T07:58:29Z")

</div>

Hi,

I updated to the [latest stable 2.4.4](https://github.com/discourse/discourse/releases/tag/v2.4.4) and b20ba9ee11b5098b9c39cd46e9f462d14ac6ce60 at [GitHub - discourse/discourse\_docker: A Docker image for Discourse · GitHub](https://github.com/discourse/discourse_docker) today using ./launcher rebuild app on the host.

The admin/upgrade page displays fine but the home page is blank. Looking at the network logs in the browser I see a 429 error which suggests there may be a regression in the handling of rate limiting, similar to [what happened last month](https://meta.discourse.org/t/just-updated-getting-429-errors-in-edge/148991).

Or maybe it is just me ?

---

<div class="post-metadata">

### Author: ![dachary](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dachary/32/119731_2.png) [@dachary](https://meta.discourse.org/u/dachary)
#### Post date: [May 28, 2020, 8:38am UTC](https://meta.discourse.org/t/just-updated-2-4-4-getting-429-errors-in-firefox-chromium/153064/2 "2020-05-28T08:38:33Z")

</div>

Looking at the console it turns out the 2.4.4 update broke [GitHub - merefield/discourse-locations: Tools for handling locations in Discourse · GitHub](https://github.com/angusmcleod/discourse-locations.git) and the 429 error is just because [only one error per minute is allowed](https://meta.discourse.org/t/just-updated-getting-429-errors-in-edge/148991/7).

> Error: Could not find module `I18n` imported from `discourse/plugins/discourse-locations/discourse/lib/location-utilities`

Is caused by the [latest commit in the discourse-locations](https://github.com/paviliondev/discourse-locations/commit/6fd0979ebd0d136d3feb4349b5b280ed239ebf43) repository. It probably is targeting **beta** using a module not available in **stable**.

I will report the bug in the issue tracker of the plugin, where it belongs.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [June 27, 2020, 8:44am UTC](https://meta.discourse.org/t/just-updated-2-4-4-getting-429-errors-in-firefox-chromium/153064/3 "2020-06-27T08:44:08Z")

</div>

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