TrueCommand Cloud cannot access added systems if they have the Listen Interface customized

Description

After days of troubleshooting why TrueCommand wasn't able to connect to only certain of my systems, I figured out that it's because I had specified specific IPs for the Web UI to listen on (i.e. not 0.0.0.0).

This makes sense, because the UI does not present the wireguard IP address as an option, and setting that in the configuration before Wireguard has successfully connected will cause nginx to fail to start.

When the TrueCommand Cloud connection is enabled and working, the listen directive should be adjusted if and only if it is not set to zeroes and reload the service.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Bug Clerk 
March 27, 2021 at 11:03 AM

Bug Clerk 
March 24, 2021 at 5:20 PM

Ken Moore 
March 23, 2021 at 2:45 PM

No - there are all sorts of other routines that need to access/interact with the NAS besides the middleware socket itself. One good example is the UI proxy support feature. This nginx error blocks all access to the NAS functionality when that UI IP is specified, and we cannot "work around" it.

William Gryzbowski 
March 23, 2021 at 2:35 PM

 Can't you use NASIP:6000 ?

Complete

Details

Assignee

Reporter

Labels

Impact

Components

Priority

More fields

Katalon Platform

Created March 23, 2021 at 5:49 AM
Updated July 1, 2022 at 5:12 PM
Resolved April 15, 2021 at 3:36 PM