# Deploy failed: no response from server - even after trying from "scratch"

**URL:** <https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369>\
**Category:** General\
**Created:** [27 January 2022 20:45 UTC](https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369 "2022-01-27T20:45:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![calixtoemilio](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@calixtoemilio](https://discourse.nodered.org/u/calixtoemilio)\
**Post date:** [27 January 2022 20:45 UTC](https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369/1 "2022-01-27T20:45:18Z")

</div>

All of the sudden after editing a node, this started happening. No the first time, but this time is more frustrating

I have restarted the nodered docker, restarted the computer, deleted the data volume and imported whole flow.json, then imported few nodes, then added nodes manually from the beginning

In the second node, a function one, after adding this lines on the top, specially the buf.slice operator

function sliceBuf(buf, start, end) {  
return buf.slice(start,end).readInt32BE();  
}

" Deploy failed: no response from server"

Bit frustrated by the lack of logs indicating anything

Suggestions?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 January 2022 21:33 UTC](https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369/2 "2022-01-27T21:33:10Z")

</div>

Welcome to the forum @calixtoemilio

If you look at the processor usage is node red using one of the cores completely? If so then probably you have introduced an infinite loop in the code or a flow. You should be able to start node-red in safe mode (adding --safe to the command line) which will start the editor but not start the flows until you Deploy. Then you can change stuff to work out where the problem is. In a non docker system you would use  
`node-red --safe`  
but I don't use Docker so you will have to look up how to it in that environment.

---

<div class="post-metadata">

**Author:** ![calixtoemilio](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@calixtoemilio](https://discourse.nodered.org/u/calixtoemilio)\
**Post date:** [28 January 2022 14:22 UTC](https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369/3 "2022-01-28T14:22:46Z")

</div>

Thanks. I basically gave up, decided to spin a new VM and start again. Now is working after adding one node at the time.

Will try later out if curiosity to the original VM

Again, thanks!

---

<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:** [29 March 2022 14:23 UTC](https://discourse.nodered.org/t/deploy-failed-no-response-from-server-even-after-trying-from-scratch/57369/4 "2022-03-29T14:23:08Z")

</div>

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