Debug tab in Node Red editor stops showing messages

[Piptan]

Hi,

Just recently that this strange thing happens to me. Debug tab in Node Red editor stops showing messages. I have checked to ensure that all debug nodes are activated (green - not greyed out) and they are. I opened browser's developer tools and found the following errors accumulating every time the debug message supposed to be displayed in the debug panel -

  WebSocket connection to 'ws://xxxxxxxxxx.mybluemix.net/red/comms' failed: Error during WebSocket handshake: Unexpected response code: 404

Yes, it is running on Bluemix.

Also, in Bluemix console (Logs), I guess I found its relevant 404 error shown -

xxxxxxxx.mybluemix.net - [22/02/2016:03:37:48 +0000] "GET /red/comms HTTP/1.1" 404 0 22 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" 108.168.250.156:44915 x_forwarded_for:"180.183.176.140" x_forwarded_proto:"http" vcap_request_id:14e572ca-10c0-4c2e-5287-08004eb477f8 response_time:0.008339623 app_id:66a033a9-cd16-4f94-b733-00d520107ce1 x_global_transaction_id:"4049478201"

I tried both stop/restart and redeploy it on Bluemix but it did not help. It used to be working fine. My flows still work well except that the debug nodes stop showing messages.

Any way I can fix it ?  Thanks.

[Piptan]

Just now, I restarted my nodered apps on Bluemix (no matter how hard I tried to restart it many times in the past few days) and found that debug nodes now work fine.

Nothing changes from my side. Don't know what 's wrong but it is all good now.

Thanks.

เมื่อ วันจันทร์ที่ 22 กุมภาพันธ์ ค.ศ. 2016 11 นาฬิกา 11 นาที 44 วินาที UTC+7, Piptan เขียนว่า:

[Nigel Dodd]

Strangely, when I run node-red on a Chrome browser on the Raspberry Pi that is actually running node-red, the debug tab does not display anything. However, when I look at node-red on another networked computer, again running Chrome, the debug tab shows the messages sent to it. The url in both cases is http://192.168.123.19:1880/#flow/83fda1ce.266b3

[Colin Law]

Does it make a difference if you use localhost:1880 rather than the ip address?

Colin

> --
> http://nodered.org
>
> Join us on Slack to continue the conversation: http://nodered.org/slack
> ---
> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to node-red+u...@googlegroups.com.
> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/node-red/5f71ec88-0127-4eb4-8e1c-8569d35f5f63%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Nigel Dodd]

Yes it does! Then it works just the same as on another machine. 

Do you know what is causing this, Colin?

Nigel

[Colin Law]

Actually I haven't much idea what might be the cause, it was just the
fact that using localhost is the normal way to do it that made me
suggest that. I guess it must be to do with the fact that the
connection is made in a different way (websocket?) or something.
Hopefully someone who knows more about the inner workings of node-red
will chip in. In the meantime it might be helpful to look in the
browser console in Chrome (Ctrl-Shift-I and the Console tab) to see if
it shows any errors. All my Pis are headless servers so I can't test
it here.

Colin

> https://groups.google.com/d/msgid/node-red/5ca2620a-5550-471c-b230-1fd7726a3c2f%40googlegroups.com.

[Dave C-J]

Was the Pi actually live on the network at the time of failure ? You may get that result if the physical Ethernet is not actually up at that address (even though you have defined it a static address)

[Julian Knight]

Or possibly you are getting a routing artifact - if you are using the external address, your router may be doing the dirty on you.

[Colin Law]

That is a very good point from Dave, the flow tabs may be coming from the cache and not node red. If you get to the point where the debug is not working and then hit the browser refresh button what happens?

Colin

On 18 Dec 2017 11:07 p.m., "Dave C-J" <dce...@gmail.com> wrote:

Was the Pi actually live on the network at the time of failure ? You may get that result if the physical Ethernet is not actually up at that address (even though you have defined it a static address)

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwLbaY60r6-29FZt1AS2jgz%3DyhcsJXiNmF2Ap4r_JgrruQ%40mail.gmail.com.

[Julian Knight]

Or ctrl-f5 to force a cache update.

On Tuesday, 19 December 2017 07:55:15 UTC, Colin Law wrote:

That is a very good point from Dave, the flow tabs may be coming from the cache and not node red. If you get to the point where the debug is not working and then hit the browser refresh button what happens?

Colin

On 18 Dec 2017 11:07 p.m., "Dave C-J" <dce...@gmail.com> wrote:

Was the Pi actually live on the network at the time of failure ? You may get that result if the physical Ethernet is not actually up at that address (even though you have defined it a static address)

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Nigel Dodd]

"Was the Pi actually live on the network"  The Pi was booted up while connected by Ethernet cable to the router.  Does this answer the question?

On 18 December 2017 at 23:07, Dave C-J <dce...@gmail.com> wrote:

Was the Pi actually live on the network at the time of failure ? You may get that result if the physical Ethernet is not actually up at that address (even though you have defined it a static address)

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/ETn1ejB3g5c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwLbaY60r6-29FZt1AS2jgz%3DyhcsJXiNmF2Ap4r_JgrruQ%40mail.gmail.com.

[Nigel Dodd]

I reported the failure to write to the Debug tab on a version of Node-Red running on a fresh installation of Jesse running on a Raspberry Pi 2. This problem only existed when I used the full numeric local IP address. When I used localhost the problem was not there.

I have now rebooted the Pi and it seems the problem has gone away. The full IP address url works and the Debug tab is written to. 

As somebody said, above, this may point to a caching issue. 

[Colin Law]

Did you try refreshing the browser cache as suggested?

Colin

On 19 December 2017 at 11:09, Nigel Dodd <nige...@gmail.com> wrote:
> I reported the failure to write to the Debug tab on a version of Node-Red
> running on a fresh installation of Jesse running on a Raspberry Pi 2. This
> problem only existed when I used the full numeric local IP address. When I
> used localhost the problem was not there.
>
> I have now rebooted the Pi and it seems the problem has gone away. The full
> IP address url works and the Debug tab is written to.
>
> As somebody said, above, this may point to a caching issue.
>
>
>
> On 19 December 2017 at 10:11, Nigel Dodd <nige...@gmail.com> wrote:
>>
>> "Was the Pi actually live on the network" The Pi was booted up while
>> connected by Ethernet cable to the router. Does this answer the question?
>>
>>
>>
>> On 18 December 2017 at 23:07, Dave C-J <dce...@gmail.com> wrote:
>>>
>>> Was the Pi actually live on the network at the time of failure ? You may
>>> get that result if the physical Ethernet is not actually up at that address
>>> (even though you have defined it a static address)
>>>
>>> --
>>> http://nodered.org
>>>
>>> Join us on Slack to continue the conversation: http://nodered.org/slack
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Node-RED" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/node-red/ETn1ejB3g5c/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to

>>> node-red+u...@googlegroups.com.

>>> To post to this group, send email to node...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/node-red.
>>> To view this discussion on the web, visit
>>> https://groups.google.com/d/msgid/node-red/CACXWFwLbaY60r6-29FZt1AS2jgz%3DyhcsJXiNmF2Ap4r_JgrruQ%40mail.gmail.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>

> --
> http://nodered.org
>
> Join us on Slack to continue the conversation: http://nodered.org/slack
> ---

> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.

> To unsubscribe from this group and stop receiving emails from it, send an
> email to node-red+u...@googlegroups.com.

> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/node-red/CAHhgtwOb40xnSwLPmy5_r5WABwqhh9bYiGiNHLezP-T8eqkG3A%40mail.gmail.com.

[Nigel Dodd]

Not explicitly. I needed to reboot because the Pi had frozen. Presumably the cache is refreshed after a reboot?

Nigel

>>> node-red+unsubscribe@googlegroups.com.

>>> To post to this group, send email to node...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/node-red.
>>> To view this discussion on the web, visit
>>> https://groups.google.com/d/msgid/node-red/CACXWFwLbaY60r6-29FZt1AS2jgz%3DyhcsJXiNmF2Ap4r_JgrruQ%40mail.gmail.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>
> --
> http://nodered.org
>
> Join us on Slack to continue the conversation: http://nodered.org/slack
> ---

> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to node-red+unsubscribe@googlegroups.com.

> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/node-red/CAHhgtwOb40xnSwLPmy5_r5WABwqhh9bYiGiNHLezP-T8eqkG3A%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/ETn1ejB3g5c/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send an email to node...@googlegroups.com.

Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAL%3D0gLsT%3DJPQUp0yB_4J6MUtLGZxo%2Ben7Okq-OCxGGTVP-9weQ%40mail.gmail.com.