# NR UI no longer comes up, red.js file corrupted?

**URL:** <https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246>\
**Category:** General\
**Created:** [18 February 2021 15:27 UTC](https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246 "2021-02-18T15:27:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![justin](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@justin](https://discourse.nodered.org/u/justin)\
**Post date:** [18 February 2021 15:27 UTC](https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246/1 "2021-02-18T15:27:29Z")

</div>

Hi. I have been using node red for a little while now, have a bunch of flows and custom developed nodes, etc. This morning all of a sudden the UI on a particular machine stopped loading. If I open the developer console I get the following error on the network tab:

```auto
    Uncaught 
Exception { name: "NS_ERROR_FILE_CORRUPTED", message: "", result: 2152857611, filename: "http://10.8.8.91:1880/red/red.min.js", lineNumber: 16, columnNumber: 0, data: null, stack: "init@http://10.8.8.91:1880/red/red.min.js:16:15527\ninit@http://10.8.8.91:1880/red/red.min.js:16:14928\n@http://10.8.8.91:1880/red/main.min.js:16:161\ne@http://10.8.8.91:1880/vendor/vendor.js:2:30005\nl/</t<@http://10.8.8.91:1880/vendor/vendor.js:2:30307\n" }

```

I have DEBUG log level set, no errors, the server starts fine it seems, its just the UI. Has anyone seen this situation occur?

JS

---

<div class="post-metadata">

**Author:** ![justin](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@justin](https://discourse.nodered.org/u/justin)\
**Post date:** [18 February 2021 15:46 UTC](https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246/2 "2021-02-18T15:46:10Z")

</div>

Apologies for this question, apparently the default flow mapping is missing so without /flows/# it breaks, but if I add a specific flow, etc it is fine??

---

<div class="post-metadata">

**Author:** ![justin](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@justin](https://discourse.nodered.org/u/justin)\
**Post date:** [19 February 2021 18:54 UTC](https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246/3 "2021-02-19T18:54:31Z")

</div>

Additionally if it helps anyone else out, the culprit was corrupted local storage in Firefox that was breaking when the initial redirect was trying to fire. Hope it helps.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 April 2021 18:55 UTC](https://discourse.nodered.org/t/nr-ui-no-longer-comes-up-red-js-file-corrupted/41246/4 "2021-04-20T18:55:31Z")

</div>

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