Product: Kryon RPA
Product Version: 19.1.3 and below
Components: Kryon Robot;Kryon Studio
Prerequisites: N/A
Symptom: Unable to connect Kryon Studio or Robot to the application server with SmartInspect error:
Metadata contains a reference that cannot be resolved: 'http://hostname:port/KryonDiscoveryServices/mex'.
Metadata contains a reference that cannot be resolved: 'http://hostname:port/KryonDiscoveryServices/mex'.
Cause: Some of you may be attempting to use port forwarding when running Kryon Studio/Robot from an outside network. If the port numbers are different you will encounter the error below in SmartInspect logs on the client end and the connection will fail:
Metadata contains a reference that cannot be resolved: 'http://hostname:port/KryonDiscoveryServices/mex'.
Metadata contains a reference that cannot be resolved: 'http://hostname:port/KryonDiscoveryServices/mex'.
Resolution: Port forwarding in Kryon is supported only where the client ports match the ports configured on the application server.
For example this will not work:
Studio appSettings.config file:
"NetComPort" value="11002"
"HttpComPort" value="11001"
"HttpsComPort" value="11002"
Application server ports:
NetTCP: 443
HTTP: 80
HTTPS: 443
Your port forwarding rules in your router are:
11002 --> 443
11001 --> 80
However, what will work is this:
Studio appSettings.config file:
"NetComPort" value="443"
"HttpComPort" value="80"
"HttpsComPort" value="443"
Application server ports:
NetTCP: 443
HTTP: 80
HTTPS: 443
Your port forwarding rules in your router are:
443 --> 443
80 --> 80
Finally, even when you connect using the settings above you should also ensure that if the application server was installed using a hostname rather than IP, the hostname of the server is resolvable from the client machine.
For instance, if the application server was installed using "myHost" with internal IP 192.168.0.100 and external IP 82.55.34.22, a Studio or Robot client outside the network will not be able to resolve it to an IP address. Here you will need to create a DNS entry pointing "myHost" to 82.55.34.22, either in your DNS server, or in the hosts file.
For example this will not work:
Studio appSettings.config file:
"NetComPort" value="11002"
"HttpComPort" value="11001"
"HttpsComPort" value="11002"
Application server ports:
NetTCP: 443
HTTP: 80
HTTPS: 443
Your port forwarding rules in your router are:
11002 --> 443
11001 --> 80
However, what will work is this:
Studio appSettings.config file:
"NetComPort" value="443"
"HttpComPort" value="80"
"HttpsComPort" value="443"
Application server ports:
NetTCP: 443
HTTP: 80
HTTPS: 443
Your port forwarding rules in your router are:
443 --> 443
80 --> 80
Finally, even when you connect using the settings above you should also ensure that if the application server was installed using a hostname rather than IP, the hostname of the server is resolvable from the client machine.
For instance, if the application server was installed using "myHost" with internal IP 192.168.0.100 and external IP 82.55.34.22, a Studio or Robot client outside the network will not be able to resolve it to an IP address. Here you will need to create a DNS entry pointing "myHost" to 82.55.34.22, either in your DNS server, or in the hosts file.
Workaround:N/A
More Information:N/A