Failed Original WebX Client or XML Client - System Connections
ATTENTION: This section and associated topics apply to the Original WebX client only.
If you attempt to access your system from an Original WebX or XML client and it is unable to establish a connection, the web browser application that you are using will display a ‘connection failed’ message.
Original WebX and XML clients use the built-in Web Server to connect to the Geo SCADA Expert server. The settings for the Web server are configured using the Server Configuration Tool, see WebX Server Settings (Original WebX).
If your web browser displays a connection failed message, it may be because:
- The user of the Original WebX or XML client has entered an incorrect port number in the Address field on the browser (if the default port is not used).
- The network connection between the client PC and server PC is unavailable. This may be due to failed hardware or a temporary loss of connection. If you suspect that there is no network connection, please contact your network administrator.
- There is a firewall blocking the connection between the client PC and the server PC. If a firewall is being used between an Original WebX or XML client and the web server, you need to configure it to allow the ports that are being used. For more information on configuring your firewall, please refer to the manufacturers’ documentation supplied with the firewall software or hardware.
The Geo SCADA Expert web server is built into each Geo SCADA Expert server instance. Typically, a local IIS reverse proxy performs TLS negotiation on behalf of the Geo SCADA Expert server. The local proxy itself is configured in IIS, with settings in the Server Configuration Tool being used to inform the Geo SCADA Expert server of the IIS configuration. By default, the local proxy listens for HTTPS connections on HTTPS port 443. Ensure that the firewall is not blocking this port.
- The configuration that enables the Original WebX and XML client to communicate with Geo SCADA Expert via a proxy server or proxy firewall is incomplete or incorrect. For example, the proxy settings in Geo SCADA Expert differ to those configured in the proxy application in which the actual port mapping occurs, or the mapping is configured incorrectly in that application. (This scenario only applies if your system uses a proxy server or proxy firewall between the Geo SCADA Expert Web server and Original WebX clients, and the Original WebX clients are set up to communicate with Geo SCADA Expert via the proxy.)
- A third-party web server on the Geo SCADA Expert server is using the ports that the Geo SCADA Expert web server is configured to use. For example, if the Apache web server is installed on the Geo SCADA Expert server and is using port 443, it will stop the Geo SCADA Expert web server from using port 443. In this situation, there are two possible solutions:
- You can reconfigure the Geo SCADA Expert server so that the Geo SCADA Expert web server uses different ports for the connection with Original WebX
Or:
- You can reconfigure the third-party web server to use different ports.
- You can reconfigure the Geo SCADA Expert server so that the Geo SCADA Expert web server uses different ports for the connection with Original WebX