# SOLVED! Error loading settings.js after changing the ENV setting TZ in docker

**URL:** <https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875>\
**Category:** General\
**Tags:** docker\
**Created:** [24 April 2023 09:16 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875 "2023-04-24T09:16:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [24 April 2023 09:16 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875/1 "2023-04-24T09:16:58Z")

</div>

Pretty much as the title says.  
Spun up a new instance of NodeRed in Docker last year and only just noticed that the times are wrong, spotted an error in the docker TZ property, changed and now NR refuses to run claiming that settings.js can't load.  
Any ideas on what to try? Not keen on making changes to settings.js since it's been fine and not modified for months despite several restarts and container updates... Thanks

Not made any changes to the settings.js file for over 3 months and all has been fine.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/3/33de207c00be1f21c91ae793724c631f7695a20d.png)

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [24 April 2023 09:27 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875/2 "2023-04-24T09:27:48Z")

</div>

Update: Changed the TV env variable to the previous incorrect value but still NR fails to run.  
Short of a hardware reboot, I'm at a loss....

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 April 2023 10:09 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875/3 "2023-04-24T10:09:33Z")

</div>

In that case something is not as it was before. I suggest you start by looking at settings.js.

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [24 April 2023 10:12 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875/4 "2023-04-24T10:12:55Z")

</div>

Hi Colin,  
Thanks, found the problem.  
I'd added some code to the bottom of the settings file. It was part of testing something, but sure I restarted the container many times during testing about a month ago. I also have watchtower running that updates NR whenever a new version is available, so felt sure it would have restarted a few times since making the changes.  
I've now removed the changes and all is well, thanks.

---

<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:** [8 May 2023 10:13 UTC](https://discourse.nodered.org/t/solved-error-loading-settings-js-after-changing-the-env-setting-tz-in-docker/77875/5 "2023-05-08T10:13:02Z")

</div>

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