# NodeRed 1.0.3 docker now slow to start

**URL:** <https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209>\
**Category:** General\
**Created:** [16 December 2019 01:35 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209 "2019-12-16T01:35:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcusone](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@marcusone](https://discourse.nodered.org/u/marcusone)\
**Post date:** [16 December 2019 01:35 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/1 "2019-12-16T01:35:38Z")

</div>

Updated my docker to v1.0.3 and it now starts slowly, causing docker to set "unhealthy"

Seems to work ok still. Hue groups weren't responding and I restarted, when I noted the "unhealthy" state.

Nothing in the logs seems amis to me... attaching to terminal nothing is display (docker attach nodered).

---

<div class="post-metadata">

**Author:** ![marcusone](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@marcusone](https://discourse.nodered.org/u/marcusone)\
**Post date:** [16 December 2019 01:57 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/2 "2019-12-16T01:57:34Z")

</div>

Tested on another system, same thing. So think its something in code change from 1.0.2 to 1.0.3

---

<div class="post-metadata">

**Author:** ![marcusone](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@marcusone](https://discourse.nodered.org/u/marcusone)\
**Post date:** [18 December 2019 16:20 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/3 "2019-12-18T16:20:31Z")

</div>

No one else having this issue?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [18 December 2019 17:00 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/4 "2019-12-18T17:00:09Z")

</div>

All we have done is add the automatic healthcheck. That only runs once a minute so will take at least a minute before it reports back. It is independent of the actual runtime - which will be started just as quickly as before.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [19 December 2019 09:45 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/5 "2019-12-19T09:45:00Z")

</div>

Just to close out this thread, we identified the healthcheck uses http to check if NR is running, but if you've configured NR to use https then the healthcheck fails.

We've rebuilt the docker images to remove the healthcheck for the time being until we have a version that works for however NR is configured.

---

<div class="post-metadata">

**Author:** ![farooqhasny](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/farooqhasny/32/26586_2.png) [@farooqhasny](https://discourse.nodered.org/u/farooqhasny)\
**Post date:** [24 June 2021 01:52 UTC](https://discourse.nodered.org/t/nodered-1-0-3-docker-now-slow-to-start/19209/6 "2021-06-24T01:52:53Z")

</div>

As you mentioned that healthcheck don't work if https is configured and helthcheck are removed temporally for time being . I was wondering is there a way to add health checks with https configured ?