0
 Followers
4
 Likes

Fix debugger so it works through NAT

Debugger
New

As we were told, the debugger (in cloud tenants) identifies the debugging instance of service studio by IP address. This then fails in NAT environments.

The debugger could work like most other infrastructures and use the port number of the debugger to identify the debugger.


Created on 6 Jun
Comments (3)

I am not sure I understand the issue here? I work from home (NAT environment, like almost all home networks) and I debug in the OutSystems cloud *all the time*.

J.Ja

Changed the category to Debugger


Hey J.Ja, the issue arises if there are multiple debuggers behind the NAT--sharing the same outside IP address--we have a team of 20 and the debugger does not function correctly when on Wi-Fi (NAT-ed), so we've had to switch over to wired connections to debug reliably.


views
307
Followers
0