Hi, I use the "tcp request node" because host/port will change and this node allows to pass in both via flow. I see the following effect and believe its a bug: node ist not connected I pass in an empty msg with host and port correctly set the node connects as expected (I use the mode "keep connec…

To be honest, it's hard to say. There have been a number of fixes made to the TCP Request node since 0.18.5 was released. Are you able to upgrade to 0.19.4 and see if you can still reproduce?

I have now made a fresh 0.19.4 installation (still the same problem) and reduced the example (below) showing the error clearly IMHO. There are two triggers, one passes correct msg.host and msg.port to the tcp node (node connects successfully), the other passes a port that won't work (tcp node shows…

Hello, I can't import the flow! Missing backslash at IP: \"192.168.178.2\" If tcp-request could not connect - no response after "SYN_SENDED" - it will close with error after some seconds. If you can get a connection, then the tcp-node will show green connected. When you send an other IP:Port, the…

@Mumin you need to edit your last post and insert a line contianing three backticks before the flow and another such line after the flow. Then it will be importable.

thanks Colin, have edit and done as suggested

Wolfgang, works perfect with your added code snippet, thanks! You should add a note to the info part in the .html and make a pull request from both changes. From my point of view its a necessary enhancement to be able to disconnect. Torsten

@Mumin if you can recreate on 0.19.4, then please raise an issue on github - https://github.com/node-red/node-red/issues/new - and provide the information you gave in the comment earlier today. The ability to explicitly disconnect an existing session that @karamo proposes is a separate enhancement …

Hi @Mumin - just tried your flow above. And...for me... it mostly works... the status is indeed slightly incorrect - in that it shows error from the second inject - and remains showing that when the first inject is hit again...(which it should not). But the first connection is still connected as th…

Hi @dceejay - if this is the case it's even better. I thought a displayed connection error really means it does not work. Others e.g. @karamo seems to think in the same way. However, as I am also using the "status" node to monitor the tcp node and show on dashboard, I guess its not cosmetic only, …

Node-RED

Node-RED Forum

Tcp request node, host/port via flow works only once

General

Mumin 19 October 2018 07:03 3

Thanks Nick
will try with 0.19.4 and come back with an info

Topic		Replies	Views
Problem with TCP requests General	12	529	27 September 2023
Tcp request node issue General	7	517	25 July 2022
Tcp msg is reassigned to the next data before debug output General http-request , function-node , possible-bug	19	540	12 October 2023
NodeRed TCP OUT Node Success Response General	16	627	13 September 2023
TCP Host Address via msg.payload? Dashboard	25	6556	25 November 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Tcp request node, host/port via flow works only once

Related topics