# Change node in v1.3.0 not working
**URL:** https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011
**Category:** General
**Created:** [12 April 2021 01:25 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011 "2021-04-12T01:25:17Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@grant1](https://discourse.nodered.org/u/grant1)
#### Post date: [12 April 2021 01:25 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/1 "2021-04-12T01:25:17Z")
Last week I was running v1.2.9 (I think) and my flow worked great. I updated to 1.3 now and for some reason the Change nodes used in my flow have the red triangle, which I understand means an error in the config. When I click on any of the red triangles, it says "Invalid Properties: -rules"
I have a feeling there is a simple fix for this that I am missing.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [12 April 2021 01:39 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/2 "2021-04-12T01:39:42Z")
Try adding in a new change node and set it with the rules you have and do a deploy and see if it works
---
### Author:  [@grant1](https://discourse.nodered.org/u/grant1)
#### Post date: [12 April 2021 01:54 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/3 "2021-04-12T01:54:31Z")
Unfortunately the result is the same (red triangle with error "Invalid Properties: -rules").
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [12 April 2021 03:13 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/4 "2021-04-12T03:13:53Z")
Hi .. what if you update to the very latest release which is **1.3.1**
It is mentioned in the [changelog](https://github.com/node-red/node-red/blob/master/CHANGELOG.md) that something was fixed relating to the Change node form validation.
---
### Author:  [@grant1](https://discourse.nodered.org/u/grant1)
#### Post date: [12 April 2021 11:03 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/5 "2021-04-12T11:03:25Z")
I am running Node-RED on an EC2 Debian instance and tried to install 1.3.1 but got the following:
# Welcome to Node-RED
12 Apr 10:56:48 - [info] Node-RED version: v1.3.1
12 Apr 10:56:48 - [info] Node.js version: v12.19.1
12 Apr 10:56:48 - [info] Linux 4.9.0-12-amd64 x64 LE
12 Apr 10:56:49 - [info] Loading palette nodes
12 Apr 10:56:49 - [info] Settings file : /home/admin/.node-red/settings.js
12 Apr 10:56:49 - [info] Context store : 'default' [module=memory]
12 Apr 10:56:49 - [info] User directory : /home/admin/.node-red
12 Apr 10:56:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Apr 10:56:49 - [info] Flows file : /home/admin/.node-red/flows\_ip-172-31-19-130.json
12 Apr 10:56:49 - [error] Unable to listen on [http://127.0.0.1:1880/](http://127.0.0.1:1880/)
12 Apr 10:56:49 - [error] Error: port in use
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
Opening the browser window still lists v1.3.0 and of course the red triangles are still there.
I do realize the above "Error: port in use" message means Node-RED is running, but in this case, I closed my browser window. Is there a more thorough way to stop Node-RED when running on an EC2 instance?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [12 April 2021 11:27 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/6 "2021-04-12T11:27:30Z")
Closing the browser window just closes the browser window - it doesn't stop the server running.
How did you install Node-RED originally? Did you use the install script we provide or something else? If you did use our install script, you should have `node-red-stop` and `node-red-start` as available commands.
Otherwise, you could try rebooting the server.
---
### Author:  [@grant1](https://discourse.nodered.org/u/grant1)
#### Post date: [12 April 2021 11:36 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/7 "2021-04-12T11:36:38Z")
Yes, I realized that closing the browser does not stop the server (sorry to have confused the matter...I realize that statement is repeated here a lot). I did originally install NR using the script, and typed node-red-stop in Putty (since that is how I am connected to the AWS Debian machine). Below is what I got (which seems to indicate the command worked). However, upon re-starting NR and re-launching the browser, it still says 1.3.0.
admin@ip-172-31-19-130:~$ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
---
### Author:  [@grant1](https://discourse.nodered.org/u/grant1)
#### Post date: [12 April 2021 15:28 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/8 "2021-04-12T15:28:23Z")
All: Thanks for your suggestions. Upgrading to 1.3.1 and rebooting the machine fixed the Change node issues. Everything works fine now.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [11 June 2021 15:29 UTC](https://discourse.nodered.org/t/change-node-in-v1-3-0-not-working/44011/9 "2021-06-11T15:29:20Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.