Common Browser Errors

To view Chrome browser logs, see WebRF logging section above.

Chrome: WebSocket connection to 'ws://mylocalsce.infor.com/scp11_webrf' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

This error means the device or computer cannot see the server listed in the mobile-web-client.json file. Likely the server value in the json file is incorrect.

Chrome: WebSocket connection to 'ws://mylocalsce.infor.com/scp11_webrf' failed: Error during WebSocket handshake: Unexpected response code: 503

This error with the response code 503 means WebRF is communicating with Apache but Apache is failing to complete the proxy connection. Possible causes include:

• SocketServer is not running.
• SocketServer is running with errors and not listening on the WebSocket ports.
• Apaches httpd.conf file has been changed but Apache has not been restarted.
• The ProxyPass statement in httpd.conf is incorrect and does not point to the running SocketServer.
• The ProxyPass statement in httpd.conf is using port numbers that are different from the SocketServer configuration