If problems concerning the Node.JS component arise, it is necessary to verify:
- from the GENERAL tab of BooleBox On-Premises control panel that the IP address or FQDN with the relative port of the server on which the component was installed has been inserted correctly. To do this, carry out a connection test using the CONNECT button. If the connection test fails, make also sure that the server hosting the Node.JS service is reachable via the specified TCP/IP port;
- in case of SSL connection, that the certificate is installed correctly and still valid;
- that the Node.Js: Server-side Java Script process is active and present in the Microsoft Windows Server Task Manager where the component is installed. If not, restart the BOOLEBOX SERVER SERVICE service on the machine hosting the component.
Note: if the controls listed in the previous points are not sufficient to solve the problems concerning the Node.JS component, it could be useful to check the service status of the same component through the following links: http://serveripaddress:3000/getpush or https://serveripadress:3500/getpush if the SSL/TLS certificate is used. On the displayed page, if the service is working correctly, a string containing all the parameters of the connected user will appear; if the certificate has expired, a warning message indicating that the SSL/TLS certificate is not valid will be displayed. In the case of a blank page, the causes of the fall of the service are to be found in the Windows event viewer.