Closed syedaminulhaq closed 3 years ago
Hi,
this looks exactly like a error I fixed in V1.3.2. But I saw, that V1.3.2 was not pushed on the GitHub repro (I don't know if Node-RED installs the nodes from npm or from GitHub...).
Can you check if you installed V1.3.2? If no, please update. If yes, can you please uninstall my nodes and reinstall?
Do i need to check node red version or any other
I mean the version of the Remote-RED nodes installed on your Node-RED. Thats inside "Manage pallete":
Hi i have updated remote access node to 1.3.2 but problem is same can u suggest how to solve kindly see setting in picture
I just released the node version 1.3.3. Here I changed the method to get the path for package.json. Maybe this works better on your Windows environment.
how can i update there is no update buton active in manage pallet
now i have updated the node but still not connecting kindly see pic for reference. do i need to install openssh or some thing like
The logs looks fine. The "s7 endpoint" error is something other not Remote-RED related.
The most actual Windows Versions have already OpenSSH installed.
Hi, Thanks a lot after updating the problem is resolved and now , i can connect with remote red app, now can i connect node red dash board on my mobile with another network
Hi, install node-red-contrib-remote from manage pallet and did basic setting but it is not connecting with the network, i have seen on my command prompt that node-red-contrib-remote when i start flows see pic for reference