Skip to main content
A
AW_132999367-Bedrock
7-Bedrock
April 17, 2025
Solved

Accessing localhost by port

  • April 17, 2025
  • 2 replies
  • 864 views

We are using Thingworx EMS to connect to local VMs in order to support them.

 

Each VM runs several containerized web applications. Typically these are accessed by support personnel at https://127.0.0.1:differentport#

 

We have applications listening at 8443, 3001, 3003 etc.

 

Support users SSH in over port 22 and have access to port 443. Even with NFT port forwarding from 443 to 8443 we cannot get any of these applications to come up. All come up if you connect to the machine directly on a local network instead of through Thingworx.

 

Any ideas on the correct configuration? We could potentially use DNS, but prefer not to require a DNS entry if we can just use 127.0.0.1 or localhost.

Best answer by AW_13299936

The issue was that the remote OS had SSH port tunneling disabled as part or our OS Hardening scripts applied to the remote.

Once we enabled port tunneling in /etc/ssh/sshd_config.d/oo- we were able to create port tunnels in ThingWorx that worked.

2 replies

P
PEHOWE17-Peridot
17-Peridot
April 21, 2025

Hello @AW_13299936 ,
Can you provide some more information on your issue?
Because this is was working at on point. What changes have taken place to the environment ?
What version of ThingWorx and ThingWorx EMS are you using?
Have you reviewed the ThingWorx and the EMS logs for any error messages?

Regards,

Pehowe

A
AW_132999367-BedrockAuthor
7-Bedrock
April 21, 2025

The Thingworx platform is version 9.4.3

The EMS agent is version 5.4.11. Nothing of interest in the logs.

 

As a simple step we are just trying to make a tunnel on port 443 so we can use https://127.0.0.1:443 to access a server on the remote from the local while we have an active SSH connection. To our knowledge, this was not working before.

A
AW_132999367-BedrockAuthorAnswer
7-Bedrock
April 23, 2025

The issue was that the remote OS had SSH port tunneling disabled as part or our OS Hardening scripts applied to the remote.

Once we enabled port tunneling in /etc/ssh/sshd_config.d/oo- we were able to create port tunnels in ThingWorx that worked.

Terms & ConditionsCookie settingsAccessibility statement