Cannot login to Node-Red on WAN

[Mikael Grah]

I’ve been trying to connect to Node-Red using a WAN based on a cellular connection, but I can’t get it to work.

I’ve tried using ssh to create a tunnel and I’ve tried opening Node-Red to WAN connections in the MultiConnect Access Configuration (then accessing the public IP directly).

Regardless of which way I try I get a “Login Failed” message in the Node-Red login dialogue. The Node-Red log shows the following:

Attempting to log in as: admin
Error trying to log in: connect ECONNREFUSED

Maybe I need to configure Node-Red itself to accept WAN connections?

Anyone knows how to solve this issue or what might be going on?

Thank you!
/M

[Steve Kovarik]

Hello Mikael

Assuming your SIM card is provisioned to allow “mobile terminated data”
if you log into the Conduit web administration and select the “Administration” tab
then select “Access Configuration” you will see a Node-Red section and you
should enable the checkbox labeled “via WAN” then scroll to the bottom
and select “Submit” then “Save & Restart”. Also as a mobile terminated data
test, on the same screen (upper right) under HTTPS enable the checkbox
labeled “via WAN” (submit then save & restart) and you should be able to browse to the public IP address of the Conduit and get to the web
administration remotely.

-Best Regards

[Mikael Grah]

Thank you, Steve!

However, I’ve done all this, I have full access to the Conduit using both the web interface and ssh. Accessing port 1880 (https) gives me the regular Node-Red login dialogue (website), but I get “Login Failed” after entering the credentials. The same credentials work for the web interface and for ssh access and for Node-Red when I’m connnecting via LAN.

If I disable the Node-Red via WAN checkbox the conduit do not respond at all to (https://IPADDRESS:1880).

Are there any other logs to check or things I could try?

Best regards,
/M

EDIT:
Conduit version: MTCDT-H5-210A
Firmware: MTCDT 1.3.3

• This reply was modified 7 years, 7 months ago by Mikael Grah.

[Steve Kovarik]

Hi Mikael

What I suggested and what you have done should be all that is needed to
access Node-Red remotely. My only other suggestion would be to upgrade
the Conduit firmware to the latest version 1.4.3 and then factory default
the device by using a paperclip and holding in the micro switch “Reset”
button on the front panel for 30 seconds. Then reconfigure and see if the
issue persists. The latest AEP firmware is available at this link.

Downloads

[Mikael Grah]

OK, thanks. I’ll try doing a factory reset once the project is in a phase where we can experiement. I think that I’ve had the same issue with another unit as well, however that unit is in a position where we cannot experiment with it.

Anyway, I’ll try factory reset on this one and get back with the results (as soon as I get the time).

Thank you once again,
/Mikael

[Mikael Grah]

Upgraded to the latest Firmware (1.4.3), that didn’t change much. I will try a factory reset later on.

[Mikael Grah]

OK, so I finally got around to do a factory reset. All the Node-Red schematics were removed (naturally), the login credentials etc. were reset, but the DeviceHQ credentials were still registered. I assume that’s normal.

However I found another problem – I can’t log in via LAN either. I assume this was the case earlier as well… Is there another way to set (or reset) the credentials for Node-Red only?

[Steve Kovarik]

Hi Mikael

So after factory defaulting the device you can log into the Conduit web administration but still can not successfully log into Node-Red?
If so, I may encourage you to register and open a Support Portal case for next steps.
https://support.multitech.com/support/login.html

[Mikael Grah]

I was just about to register the support case when the same thing happened to one of the other gateways, this time I knew exactly what happened…

I had just changed the https port on the devices. This turned out to be the problem all along. Once I realized the issue, I checked the authentication script for Node-Red and realized that it uses the https-interface to authenticate the user.

Maybe this could help someone else in the future… 🙂

Thank you for your support!

[Author]

Posts