# Deploy failing. No response from server (node:function)

**URL:** <https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244>\
**Category:** General\
**Created:** [16 June 2021 13:36 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244 "2021-06-16T13:36:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [16 June 2021 13:36 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/1 "2021-06-16T13:36:54Z")

</div>

Hey

I got a strange behavior with node Red.

I installed version node Red v1.3.5 with Node JS 14.16 on 3 PCs.

On one PC I cant update function blocks!

I already testet the following: I closed node Red and then startet. Then I created a new flow (without projects=true). I added a inject and a debug and deployed. This worked fine.

As soon as I add a simple function block and add "msg.info=1;" to the function code, everytime I push "Deploy" the error is shown by the browser.

Here is the detailed log of node RED:

````auto
Set No TLS Erros (Self Signed Crt)
Start Node
16 Jun 15:25:42 - [info]

Welcome to Node-RED
===================

16 Jun 15:25:42 - [info] Node-RED version: v1.3.5
16 Jun 15:25:42 - [info] Node.js version: v14.16.0
16 Jun 15:25:42 - [info] Windows_NT 10.0.17763 x64 LE
16 Jun 15:25:43 - [info] Loading palette nodes
16 Jun 15:25:44 - [debug] Module: node-red-contrib-config 1.2.1 C:\NodeRed\node_modules\node-red-contrib-config
16 Jun 15:25:44 - [debug] Module: node-red-contrib-crypto-js 0.1.1 C:\NodeRed\node_modules\node-red-contrib-crypto-js
16 Jun 15:25:44 - [debug] Module: node-red-contrib-elasticsearch7 0.0.7 C:\NodeRed\node_modules\node-red-contrib-elasticsearch7
16 Jun 15:25:44 - [debug] Module: node-red-contrib-fs 1.4.1 C:\NodeRed\node_modules\node-red-contrib-fs
16 Jun 15:25:44 - [debug] Module: node-red-contrib-fs-ops 1.6.0 C:\NodeRed\node_modules\node-red-contrib-fs-ops
16 Jun 15:25:44 - [debug] Module: node-red-contrib-gc-trigger 0.0.1 C:\NodeRed\node_modules\node-red-contrib-gc-trigger
16 Jun 15:25:44 - [debug] Module: node-red-contrib-iiot-opcua 3.12.1 C:\NodeRed\node_modules\node-red-contrib-iiot-opcua
16 Jun 15:25:44 - [debug] Module: node-red-contrib-jsonpath 0.1.1 C:\NodeRed\node_modules\node-red-contrib-jsonpath
16 Jun 15:25:44 - [debug] Module: node-red-contrib-mqtt-broker 0.2.5 C:\NodeRed\node_modules\node-red-contrib-mqtt-broker
16 Jun 15:25:44 - [debug] Module: node-red-contrib-os 0.2.0 C:\NodeRed\node_modules\node-red-contrib-os
16 Jun 15:25:44 - [debug] Module: node-red-contrib-simple-gate 0.5.0 C:\NodeRed\node_modules\node-red-contrib-simple-gate
16 Jun 15:25:44 - [debug] Module: node-red-contrib-simple-message-queue 0.2.7 C:\NodeRed\node_modules\node-red-contrib-simple-message-queue
16 Jun 15:25:44 - [debug] Module: node-red-contrib-smb 1.2.0 C:\NodeRed\node_modules\node-red-contrib-smb
16 Jun 15:25:44 - [debug] Module: node-red-contrib-spreadsheet-in 0.6.0 C:\NodeRed\node_modules\node-red-contrib-spreadsheet-in
16 Jun 15:25:44 - [debug] Module: node-red-contrib-string 0.2.2 C:\NodeRed\node_modules\node-red-contrib-string
16 Jun 15:25:44 - [debug] Module: node-red-contrib-watchdirectory 1.0.14 C:\NodeRed\node_modules\node-red-contrib-watchdirectory
16 Jun 15:25:44 - [debug] Module: node-red-dashboard 2.29.1 C:\NodeRed\node_modules\node-red-dashboard
16 Jun 15:25:45 - [debug] Module: node-red-node-email 1.12.1 C:\NodeRed\node_modules\node-red-node-email
16 Jun 15:25:45 - [debug] Module: node-red-node-feedparser 0.1.16 C:\NodeRed\node_modules\node-red-node-feedparser
16 Jun 15:25:45 - [debug] Module: node-red-node-mysql 0.0.17 C:\NodeRed\node_modules\node-red-node-mysql
16 Jun 15:25:45 - [debug] Module: node-red-node-rbe 0.2.9 C:\NodeRed\node_modules\node-red-node-rbe
16 Jun 15:25:45 - [debug] Module: node-red-node-tail 0.3.1 C:\NodeRed\node_modules\node-red-node-tail
16 Jun 15:25:45 - [debug] Module: node-red-node-twitter 1.2.0 C:\NodeRed\node_modules\node-red-node-twitter
16 Jun 15:25:50 - [info] Dashboard version 2.29.1 started at /ui
16 Jun 15:25:50 - [info] Settings file : C:\NodeRED\node-red_home\settings.js
16 Jun 15:25:50 - [info] Context store : 'storeInFile' [module=localfilesystem]
16 Jun 15:25:50 - [info] Context store : 'memoryonly' [module=memory]
16 Jun 15:25:50 - [info] Context store : 'default' [module=memory]
16 Jun 15:25:50 - [info] User directory : C:\NodeRed\node-red_home
16 Jun 15:25:50 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Jun 15:25:50 - [info] Flows file : C:\NodeRed\node-red_home\flows_M010SX03121801B.json
16 Jun 15:25:50 - [info] Creating new flow file
16 Jun 15:25:50 - [debug] loaded flow revision: d751713988987e9331980363e24189ce
16 Jun 15:25:50 - [debug] red/runtime/nodes/credentials.load : no user key present
16 Jun 15:25:50 - [debug] red/runtime/nodes/credentials.load : using default key
16 Jun 15:25:50 - [debug] red/runtime/nodes/credentials.load : keyType=system
16 Jun 15:25:50 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

16 Jun 15:25:50 - [trace] runtime event: {"id":"runtime-state","retain":true}
16 Jun 15:25:50 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"d751713988987e9331980363e24189ce"},"retain":true}
16 Jun 15:25:50 - [info] Starting flows
16 Jun 15:25:50 - [debug] red/nodes/flows.start : starting flow : global
16 Jun 15:25:50 - [trace] [flow:global] start flow [global]
16 Jun 15:25:50 - [trace] runtime event: {"id":"runtime-state","retain":true}
16 Jun 15:25:50 - [info] Started flows
16 Jun 15:25:50 - [info] Server now running at https://127.0.0.1:1880/
16 Jun 15:26:08 - [audit] {"event":"auth.invalid-token","level":98,"timestamp":1623849968132}
16 Jun 15:26:11 - [trace] utils.writeFile - written content to C:\NodeRed\node-red_home\.sessions.json.$$$
16 Jun 15:26:11 - [trace] utils.writeFile - renamed C:\NodeRed\node-red_home\.sessions.json.$$$ to C:\NodeRed\node-red_home\.sessions.json
16 Jun 15:26:11 - [audit] {"event":"auth.login","username":"admin","client":"node-red-editor","scope":"*","level":98,"timestamp":1623849971408}
16 Jun 15:26:11 - [audit] {"event":"plugins.list.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/plugins","ip":"127.0.0.1","timestamp":1623849971663}
16 Jun 15:26:11 - [audit] {"event":"plugins.configs.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/plugins","ip":"127.0.0.1","timestamp":1623849971782}
16 Jun 15:26:11 - [audit] {"event":"nodes.list.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/nodes","ip":"127.0.0.1","timestamp":1623849971788}
16 Jun 15:26:11 - [audit] {"event":"nodes.icons.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/icons","ip":"127.0.0.1","timestamp":1623849971825}
16 Jun 15:26:11 - [audit] {"event":"nodes.configs.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/nodes","ip":"127.0.0.1","timestamp":1623849971835}
16 Jun 15:26:12 - [audit] {"event":"comms.open","level":98,"timestamp":1623849972267}
16 Jun 15:26:12 - [trace] comms.open ehZFs9VcNkv2zHsf/z6DZDUwpm4YL86zJuPelhVdgHE=
16 Jun 15:26:13 - [audit] {"event":"flows.get","level":98,"user":{"username":"admin","permissions":"*"},"path":"/flows","ip":"127.0.0.1","timestamp":1623849973206}
16 Jun 15:26:13 - [audit] {"event":"comms.auth","user":{"username":"admin","permissions":"*"},"level":98,"timestamp":1623849973745}
16 Jun 15:26:20 - [audit] {"event":"flows.set","type":"full","level":98,"user":{"username":"admin","permissions":"*"},"path":"/flows","ip":"127.0.0.1","timestamp":1623849980227}
16 Jun 15:26:20 - [trace] utils.writeFile - copied C:\NodeRed\node-red_home\flows_M010SX03121801B.json TO C:\NodeRed\node-red_home\.flows_M010SX03121801B.json.backup
16 Jun 15:26:20 - [trace] utils.writeFile - written content to C:\NodeRed\node-red_home\flows_M010SX03121801B.json.$$$
16 Jun 15:26:20 - [trace] utils.writeFile - renamed C:\NodeRed\node-red_home\flows_M010SX03121801B.json.$$$ to C:\NodeRed\node-red_home\flows_M010SX03121801B.json
16 Jun 15:26:20 - [debug] saved flow revision: 0a6409b0ab15fb1a3f36cb3405f8a78b
16 Jun 15:26:20 - [info] Flows werden gestoppt
16 Jun 15:26:20 - [debug] red/nodes/flows.stop : stopping flow : global
16 Jun 15:26:20 - [trace] [flow:global] stop flow
16 Jun 15:26:20 - [info] Flows sind gestoppt
16 Jun 15:26:20 - [info] Flows werden gestartet
16 Jun 15:26:20 - [debug] red/nodes/flows.start : starting flow : global
16 Jun 15:26:20 - [debug] red/nodes/flows.start : starting flow : 74e636d3.1fa3f8
16 Jun 15:26:20 - [trace] [flow:global] start flow [global]
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] start flow [74e636d3.1fa3f8]
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] ------------------|--------------|-----------------
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] id | type | alias
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] ------------------|--------------|-----------------
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] 8afb576.7c5a5a8 | inject |
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] dfd5ab47.5857d8 | debug |
16 Jun 15:26:20 - [trace] [flow:74e636d3.1fa3f8] ------------------|--------------|-----------------
16 Jun 15:26:20 - [trace] runtime event: {"id":"runtime-state","retain":true}
16 Jun 15:26:20 - [info] Flows sind gestartet
16 Jun 15:26:20 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"0a6409b0ab15fb1a3f36cb3405f8a78b"},"retain":true}```

Only by restarting node RED I can continue working (but I cant deploy the code to the function).
If I Import a flow from another pc (with functions), the flow itself runs fine.

Do you have any idea?
````

---

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [16 June 2021 13:41 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/2 "2021-06-16T13:41:57Z")

</div>

If I open Chrome Debug (CTRL+SHIFT+C) and go to console I find this POST:

> JQMIGRATE: Migrate is installed, version 3.3.0  
> :1880/settings?\_=1623849967859:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)  
> red.min.js:16 Node-RED: 1.3.5  
> red.min.js:16 Versions  
> red.min.js:16 jQuery 3.5.1  
> red.min.js:16 jQuery UI 1.12.1  
> red.min.js:16 ACE 1.4.12  
> red.min.js:16 D3 3.0.3  
> red.min.js:16 Projects disabled  
> :1880/flows:1 Failed to load resource: net::ERR\_CERT\_AUTHORITY\_INVALID  
> DevTools failed to parse SourceMap: https:/localhost:1880/vendor/purify.min.js.map  
> DevTools failed to parse SourceMap: https:/localhost:1880/gridstack.min.map  
> DevTools failed to parse SourceMap: https:/localhost:1880/ui\_base/gs/gridstack.min.map  
> DevTools failed to parse SourceMap: https:/localhost:1880/gridstack.min.map  
> DevTools failed to parse SourceMap: https:/localhost:1880/ui\_base/gs/gridstack.min.map  
> 2vendor.js:2 POST https:/localhost:1880/flows net::ERR\_CERT\_AUTHORITY\_INVALID  
> send @ vendor.js:2  
> ajax @ vendor.js:2  
> s.ajax @ vendor.js:4  
> E @ red.min.js:16  
> (anonymous) @ red.min.js:16  
> dispatch @ vendor.js:2  
> v.handle @ vendor.js:2

---

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [16 June 2021 13:54 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/3 "2021-06-16T13:54:07Z")

</div>

I "fixed" this by deactivating user password in settings.js on this test case, but after using bigger blocks, I get similar behaviour:

> Chrome Error:  
> JQMIGRATE: Migrate is installed, version 3.3.0  
> DevTools failed to parse SourceMap: https:/localhost:1880/vendor/purify.min.js.map  
> red.min.js:16 Node-RED: 1.3.5  
> red.min.js:16 Versions  
> 2DevTools failed to parse SourceMap: https:/localhost:1880/gridstack.min.map  
> blob:https:/localho…a47e-780a4389dfcd:1 Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https:/localhost:1880/vendor/ace/worker-nrjavascript.js' failed to load.  
> at blob:https:/localhost:1880/f17b4be9-48c1-4a89-a47e-780a4389dfcd:1:1  
> (anonymous) @ blob:https:/localho…a47e-780a4389dfcd:1  
> blob:https:/localho…a1c6-875adb908f9e:1 Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https:/localhost:1880/vendor/ace/worker-nrjavascript.js' failed to load.  
> at blob:https:/localhost:1880/282cc7ae-16cc-48a1-a1c6-875adb908f9e:1:1  
> (anonymous) @ blob:https:/localho…a1c6-875adb908f9e:1  
> blob:https:/localho…9d52-337ada0ad300:1 Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https:/localhost:1880/vendor/ace/worker-nrjavascript.js' failed to load.  
> at blob:https:/localhost:1880/8457bea6-f38a-4caa-9d52-337ada0ad300:1:1  
> (anonymous) @ blob:[https://localho](https://localho)…9d52-337ada0ad300:1  
> :1880/red/images/typedInput/re.svg:1 GET https:/localhost:1880/red/images/typedInput/re.svg net::ERR\_CERT\_AUTHORITY\_INVALID  
> Image (async)  
> attr @ vendor.js:2  
> $ @ vendor.js:2  
> attr @ vendor.js:2  
> S.fn.init @ vendor.js:2  
> s.fn.init @ vendor.js:4  
> S @ vendor.js:2  
> (anonymous) @ red.min.js:16  
> \_createMenu @ red.min.js:16  
> (anonymous) @ vendor.js:10  
> types @ red.min.js:16  
> (anonymous) @ vendor.js:10  
> \_create @ red.min.js:16  
> (anonymous) @ vendor.js:10  
> \_createWidget @ vendor.js:10  
> t.. @ vendor.js:10  
> (anonymous) @ vendor.js:10  
> each @ vendor.js:2  
> each @ vendor.js:2  
> t.fn. @ vendor.js:10  
> oneditprepare @ VM699:21  
> r @ red.min.js:16  
> f @ red.min.js:16  
> open @ red.min.js:16  
> i @ red.min.js:16  
> show @ red.min.js:16  
> edit @ red.min.js:16  
> tt @ red.min.js:16  
> i @ vendor.js:35  
> vendor.js:2 POST https:/localhost:1880/flows net::ERR\_CERT\_AUTHORITY\_INVALID

---

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [17 June 2021 09:04 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/4 "2021-06-17T09:04:22Z")

</div>

It looks like a issue with certificates of node RED ... If I export the flow to clipboard, then close the broswer and then reopen node RED, i can import from Clipboard and then apply.

Any idea what's going wrong?

---

<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:** [17 June 2021 09:05 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/5 "2021-06-17T09:05:46Z")

</div>

How have you configured https in the settings file? As you say, looks like a certificate issue.

---

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [17 June 2021 09:17 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/6 "2021-06-17T09:17:46Z")

</div>

This is my config:

> var fs = require("fs");  
> module.exports = {  
> uiPort: process.env.PORT || 1880,  
> mqttReconnectTime: 15000,  
> serialReconnectTime: 15000,  
> debugMaxLength: 1000,  
> https: {  
> key: fs.readFileSync('node-red\_home/certificates/privkey.pem'),  
> cert: fs.readFileSync('node-red\_home/certificates/certificate.pem')  
> },  
> requireHttps: false,  
> functionGlobalContext: {  
> // os:require('os'),  
> require:require,  
> fs:require('fs'),  
> cryptojs:require('crypto-js'),  
> fm:require('array.prototype.flatmap')  
> },  
> editorTheme: {  
> projects: {  
> // To enable the Projects feature, set this value to true  
> enabled: true  
> }  
> } ,  
> contextStorage: {  
> storeInFile: { module: "localfilesystem"},  
> memoryonly : { module: "memory" },  
> default : { module: "memory" }  
> },  
> logging: {  
> console: {  
> level: "trace",  
> metrics: false,  
> audit: true  
> }  
> }  
> }

---

<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:** [16 August 2021 09:18 UTC](https://discourse.nodered.org/t/deploy-failing-no-response-from-server-node-function/47244/7 "2021-08-16T09:18:27Z")

</div>

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