# Nodes stopped working upon move from Node-red 3.1.0 to 3.1.3

**URL:** https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697
**Category:** General
**Created:** [13 December 2023 20:09 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697 "2023-12-13T20:09:33Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![tonymacdonald](https://avatars.discourse-cdn.com/v4/letter/t/77aa72/32.png) [@tonymacdonald](https://discourse.nodered.org/u/tonymacdonald)
#### Post date: [14 December 2023 15:06 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/9 "2023-12-14T15:06:47Z")

</div>

Just about to upgrade from NR 3.1.0 to 3.1.3 on a raspberry pi 4

Given this thread, is that recommended?

if so what is the recommended process for a minor upgrade.

wondering if the process mentioned here is required.

> [@tada Node-RED 3.1.3 Released](https://discourse.nodered.org/t/node-red-3-1-3-released/83512/2):
>
> After pulling the 3.1.3 version and still seeing 3.1.0 running I fixed the problem by stopping and removing the running image and then starting up fresh. Never had to do that before. man_shrugging Sorry for the noise. EDIT: Man, I'm "losin' it" even more than I thought. I've always had to do the above and even have a command alias for it alias NR-postupdate='NR-stop; NR-remove; NR-startdaemon' but completely spaced it. Taking suggestions for an institution to check into... crazy_face …

---

_[View the full topic](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697)._