Issues Loading Node-Red on MCDT-LAT1 with 1.6.2 firmware

Home Forums Conduit: AEP Model Issues Loading Node-Red on MCDT-LAT1 with 1.6.2 firmware

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #26513
    bdbuysse@gmail.com
    Participant

    Hello,

    I just upgraded a MCDT-LAT1 aep to firmware 1.6.2 and am having issues getting Node-Red to launch. I validated that the inbound firewall is enabled, and the app seems to be running. When I try and access Node-Red the page seems to just reload over and over. The /var/log/messages has some errors:

    2018-10-12T17:13:51.013815+00:00 mtcdt stunnel: LOG5[260]: Service [node-red] accepted connection from 192.168.193.67:55028
    2018-10-12T17:13:51.042567+00:00 mtcdt stunnel: LOG6[259]: s_connect: connecting 127.0.0.1:1882
    2018-10-12T17:13:51.046567+00:00 mtcdt stunnel: LOG5[259]: s_connect: connected 127.0.0.1:1882
    2018-10-12T17:13:51.047682+00:00 mtcdt stunnel: LOG5[259]: Service [node-red] connected remote server from 127.0.0.1:53137
    2018-10-12T17:13:51.054586+00:00 mtcdt stunnel: LOG6[259]: SSL socket closed (SSL_read)
    2018-10-12T17:13:51.057277+00:00 mtcdt stunnel: LOG5[259]: Connection closed: 0 byte(s) sent to SSL, 0 byte(s) sent to socket
    2018-10-12T17:13:51.136283+00:00 mtcdt stunnel: LOG6[260]: SSL accepted: previous session reused

    Additionally when ssh’d into the gateway I’m seeing an additional error:
    Message from syslogd@mtcdt at Oct 12 17:15:44 …
    SMSD: Exeption was detected

    Is anyone else having this issue, or know what might be going on?

    Thanks much!
    Brad

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.