Node-red not starting in ubuntu

Hello guys,
I'am trying to start node-red in Ubuntu but it is unable to start and giving the following message whenever i run the command "node-red".
It ran once when i installed it but all of sudden it crashed.

admin:~$ node-red
Error loading settings file: /home/sagar/.node-red/settings.js
functionGlobalContext: {

SyntaxError: Unexpected identifier
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:616:28)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/usr/local/lib/node_modules/node-red/red.js:119:20)

kindly, help me with this issue.

Most likely you have lost a comma somewhere. Take careful note of the structure of the JavaScript object that contains that property.

Or possibly you have put the context line on the end of the settings file instead of in with the other keys.

I am a newbie in this field.So, it will be very helpful if you tell me which file to view and edit.

now getting this

23 Oct 12:00:56 - [info] Node-RED version: v1.0.2
23 Oct 12:00:56 - [info] Node.js version: v8.10.0
23 Oct 12:00:56 - [info] Linux 5.0.0-32-generic x64 LE
23 Oct 12:00:56 - [info] Loading palette nodes
23 Oct 12:01:01 - [info] Dashboard version 2.17.1 started at /ui
23 Oct 12:01:02 - [red] Uncaught Exception:
23 Oct 12:01:02 - Error: bind EACCES
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at _handle.lookup (dgram.js:266:18)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

Have you changed settings.js to tell it to use port 67? You can't do that as low port numbers cannot be used by code running as a normal user.
If you don't know why that is happening then post your settings.js file here.
Have you installed any extra nodes? If so then what.
Has node-red ever worked on this system?

Here it is....

GNU nano 2.9.3 .node-red/settings.js

        // Whether or not to include metric events in the log output
        metrics: false,
        // Whether or not to include audit events in the log output
        audit: false

// Customising the editor
editorTheme: {
    projects: {
        // To enable the Projects feature, set this value to true
        enabled: false


^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos
^X Exit ^R Read File ^\ Replace ^U Uncut Text^T To Spell ^_ Go To Line

Yes, it worked once when i just installed it for the first time.
But when i was installing some libraries at that time something went wrong.

I tried the following commands in order to get the things right but the attempt was not successful.
sudo npm -g uninstall node-red
sudo npm install -g --unsafe-perm node-red

Here is the settings.js file


  • Copyright JS Foundation and other contributors,
  • Licensed under the Apache License, Version 2.0 (the "License");
  • you may not use this file except in compliance with the License.
  • You may obtain a copy of the License at
  • Unless required by applicable law or agreed to in writing, software
  • distributed under the License is distributed on an "AS IS" BASIS,
  • WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  • See the License for the specific language governing permissions and
  • limitations under the License.

// The https setting requires the fs module. Uncomment the following
// to make it available:
//var fs = require("fs");

module.exports = {
// the tcp port that the Node-RED web server is listening on
uiPort: process.env.PORT || 1880,

// By default, the Node-RED UI accepts connections on all IPv4 interfaces.
// To listen on all IPv6 addresses, set uiHost to "::",
// The following property can be used to listen on a specific interface. For
// example, the following would only allow connections from the local machine.
//uiHost: "",

// Retry time in milliseconds for MQTT connections
mqttReconnectTime: 15000,

// Retry time in milliseconds for Serial port connections
serialReconnectTime: 15000,

// Retry time in milliseconds for TCP socket connections
//socketReconnectTime: 10000,

// Timeout in milliseconds for TCP server socket connections
//  defaults to no timeout
//socketTimeout: 120000,

// Maximum number of messages to wait in queue while attempting to connect to TCP socket
//  defaults to 1000
//tcpMsgQueueSize: 2000,

// Timeout in milliseconds for HTTP request connections
//  defaults to 120 seconds
//httpRequestTimeout: 120000,

// The maximum length, in characters, of any message sent to the debug sidebar tab
debugMaxLength: 1000,

// The maximum number of messages nodes will buffer internally as part of their
// operation. This applies across a range of nodes that operate on message sequences.
//  defaults to no limit. A value of 0 also means no limit is applied.
//nodeMessageBufferMaxLength: 0,

// To disable the option for using local files for storing keys and certificates in the TLS configuration
//  node, set this to true
//tlsConfigDisableLocalFiles: true,

// Colourise the console output of the debug node
//debugUseColors: true,

// The file containing the flows. If not set, it defaults to flows_<hostname>.json
//flowFile: 'flows.json',

// To enabled pretty-printing of the flow within the flow file, set the following
//  property to true:
//flowFilePretty: true,

// By default, credentials are encrypted in storage using a generated key. To
// specify your own secret, set the following property.
// If you want to disable encryption of credentials, set this property to false.
// Note: once you set this property, do not change it - doing so will prevent
// node-red from being able to decrypt your existing credentials and they will be
// lost.
//credentialSecret: "a-secret-key",

// By default, all user data is stored in a directory called `.node-red` under
// the user's home directory. To use a different location, the following
// property can be used
//userDir: '/home/nol/.node-red/',

// Node-RED scans the `nodes` directory in the userDir to find local node files.
// The following property can be used to specify an additional directory to scan.
//nodesDir: '/home/nol/.node-red/nodes',

// By default, the Node-RED UI is available at http://localhost:1880/
// The following property can be used to specify a different root path.
// If set to false, this is disabled.
//httpAdminRoot: '/admin',

// Some nodes, such as HTTP In, can be used to listen for incoming http requests.
// By default, these are served relative to '/'. The following property
// can be used to specifiy a different root path. If set to false, this is
// disabled.
//httpNodeRoot: '/red-nodes',

// The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot',
// to apply the same root to both parts.
//httpRoot: '/red',

// When httpAdminRoot is used to move the UI to a different root path, the
// following property can be used to identify a directory of static content
// that should be served at http://localhost:1880/.
//httpStatic: '/home/nol/node-red-static/',

// The maximum size of HTTP request that will be accepted by the runtime api.
// Default: 5mb
//apiMaxLength: '5mb',

// If you installed the optional node-red-dashboard you can set it's path
// relative to httpRoot
//ui: { path: "ui" },

// Securing Node-RED
// -----------------
// To password protect the Node-RED editor and admin API, the following
// property can be used. See for details.
//adminAuth: {
//    type: "credentials",
//    users: [{
//        username: "admin",
//        password: "$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN.",
//        permissions: "*"
//    }]

// To password protect the node-defined HTTP endpoints (httpNodeRoot), or
// the static content (httpStatic), the following properties can be used.
// The pass field is a bcrypt hash of the password.
// See
//httpNodeAuth: {user:"user",pass:"$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN."},
//httpStaticAuth: {user:"user",pass:"$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN."},

// The following property can be used to enable HTTPS
// See
// for details on its contents.
// See the comment at the top of this file on how to load the `fs` module used by
// this setting.
//https: {
//    key: fs.readFileSync('privatekey.pem'),
//    cert: fs.readFileSync('certificate.pem')

// The following property can be used to cause insecure HTTP connections to
// be redirected to HTTPS.
//requireHttps: true,

// The following property can be used to disable the editor. The admin API
// is not affected by this option. To disable both the editor and the admin
// API, use either the httpRoot or httpAdminRoot properties
//disableEditor: false,

// The following property can be used to configure cross-origin resource sharing
// in the HTTP nodes.
// See for
// details on its contents. The following is a basic permissive set of options:
//httpNodeCors: {
//    origin: "*",
//    methods: "GET,PUT,POST,DELETE"

// If you need to set an http proxy please set an environment variable
// called http_proxy (or HTTP_PROXY) outside of Node-RED in the operating system.
// For example - http_proxy=
// (Setting it here will have no effect)
// You may also specify no_proxy (or NO_PROXY) to supply a comma separated
// list of domains to not proxy, eg -,

// The following property can be used to add a custom middleware function
// in front of all http in nodes. This allows custom authentication to be
// applied to all http in nodes, or any other sort of common request processing.
//httpNodeMiddleware: function(req,res,next) {
//    // Handle/reject the request, or pass it on to the http in node by calling next();
//    // Optionally skip our rawBodyParser by setting this to true;
//    //req.skipRawBodyParser = true;
//    next();

// The following property can be used to pass custom options to the Express.js
// server used by Node-RED. For a full list of available options, refer
// to
//httpServerOptions: { },

// The following property can be used to verify websocket connection attempts.
// This allows, for example, the HTTP request headers to be checked to ensure
// they include valid authentication information.
//webSocketNodeVerifyClient: function(info) {
//    // 'info' has three properties:
//    //   - origin : the value in the Origin header
//    //   - req : the HTTP request
//    //   - secure : true if req.connection.authorized or req.connection.encrypted is set
//    //
//    // The function should return true if the connection should be accepted, false otherwise.
//    //
//    // Alternatively, if this function is defined to accept a second argument, callback,
//    // it can be used to verify the client asynchronously.
//    // The callback takes three arguments:
//    //   - result : boolean, whether to accept the connection or not
//    //   - code : if result is false, the HTTP error status to return
//    //   - reason: if result is false, the HTTP reason string to return

// The following property can be used to seed Global Context with predefined
// values. This allows extra node modules to be made available with the
// Function node.
// For example,
//    functionGlobalContext: { os:require('os') }
// can be accessed in a function block as:
//    global.get("os")
functionGlobalContext: {
    // os:require('os'),
    // jfive:require("johnny-five"),
    // j5board:require("johnny-five").Board({repl:false})
// `global.keys()` returns a list of all properties set in global context.
// This allows them to be displayed in the Context Sidebar within the editor.
// In some circumstances it is not desirable to expose them to the editor. The
// following property can be used to hide any property set in `functionGlobalContext`
// from being list by `global.keys()`.
// By default, the property is set to false to avoid accidental exposure of
// their values. Setting this to true will cause the keys to be listed.
exportGlobalContextKeys: false,

// Context Storage
// The following property can be used to enable context storage. The configuration
// provided here will enable file-based context that flushes to disk every 30 seconds.
// Refer to the documentation for further options:
//contextStorage: {
//    default: {
//        module:"localfilesystem"
//    },

// The following property can be used to order the categories in the editor
// palette. If a node's category is not in the list, the category will get
// added to the end of the palette.
// If not set, the following default order is used:
//paletteCategories: ['subflows','flow','input','output','function','parser','social','mobile','storage','analysis','advanced'],

// Configure the logging output
logging: {
    // Only console logging is currently supported
    console: {
        // Level of logging to be recorded. Options are:
        // fatal - only those errors which make the application unusable should be recorded
        // error - record errors which are deemed fatal for a particular request + fatal errors
        // warn - record problems which are non fatal + errors + fatal errors
        // info - record information about the general running of the application + warn + error + fatal errors
        // debug - record information which is more verbose than info + info + warn + error + fatal errors
        // trace - record very detailed logging + debug + info + warn + error + fatal errors
        // off - turn off all logging (doesn't affect metrics or audit)
        level: "info",
        // Whether or not to include metric events in the log output
        metrics: false,
        // Whether or not to include audit events in the log output
        audit: false

// Customising the editor
editorTheme: {
    projects: {
        // To enable the Projects feature, set this value to true
        enabled: false


no i did not make any changes to the port.

Which extra libraries? Do you mean nodes?
If you can't remember then look in package.json to see if it reminds you.
If you still can't remember then post package.json here.


I have the same problem. After updating some palettes in node-red i had to restart node-red.
It didn't want to start and got the following:

Starting as a systemd service.
28 Dec 15:31:32 - [info] Loading palette nodes
28 Dec 15:31:36 - [info] Dashboard version 2.19.3 started at /ui
28 Dec 15:31:36 - [red] Uncaught Exception:
28 Dec 15:31:36 - Error: bind EACCES
at dgram.js:321:20
at processTicksAndRejections (internal/process/task_queues.js:81:21)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.