IP Server address of the ASP.net State Service session
If the connection check performed through the CONNECT button doesn’t work, you must verify:
- ASP.NET SERVICE STATUS – in order to guarantee the correct functioning of the platform, the ASP.NET service must be running; in addition, the settings relating to the service must impose automatic execution when the server is started: in the event of restarting it the service must indeed restart automatically. You can check the status of the service through the Windows services panel and, if it is not started, restart it manually.
- SERVER IP ADDRESS AND CONNECTION PORT – in order to guarantee the correct functioning of the platform, the server must be reachable on the network at the IP address specified through the indicated port. If the indicated server is protected by a specific firewall, it is necessary to open the TCP/IP ports according to the firewall rules, in order to allow in any case to reach the server. To make sure that all the prerequisites listed above are respected, check that in the GENERAL tab, in correspondence with the IP SERVER ADDRESS OF THE ASP.NET STATE SERVICE SESSION field, the IP address of the server and its port have been correctly indicated. Please note that the server to be specified corresponds to the one where the service was installed: more precisely, the format of the address to be indicated is serveripaddress:42424.
Public URL of BooleBox Server
If the connection check performed through the CONNECT button doesn’t work, you must verify:
- SERVER IP ADDRESS AND CONNECTION PORT – in order to guarantee the correct functioning of the platform, the server must be reachable on the network at the IP address specified through the indicated port. If the indicated server is protected by a specific firewall, it is necessary to open the TCP/IP ports according to the firewall rules in order to allow in any case to reach the server. To make sure that all the prerequisites listed above are respected, check that in the GENERAL tab, in correspondence to the PUBLIC URL OF BOOLEBOX SERVER field, the indicated IP address corresponds to that of the server on which the BooleBox Web App has been installed. The format of the IP address must be http://serveripaddress:80 if the HTTP connection protocol is used and https://serveripaddress:443 if the HTTPS connection protocol is used.
- IIS SERVER STATUS – in order to guarantee the correct functioning of the platform, it is necessary that the IIS server where the application was published is active. Then verify that the IIS server is activated, that the publication port is the correct one (80 for the http protocol, 443 for the https protocol) and that the website is online and running through the IIS management console in Windows Server.
URL SERVER ADDRESS OF SIGNAL R
If the connection check performed through the CONNECT button doesn’t work, you must verify:
- SERVER IP ADDRESS AND CONNECTION PORT – in order to guarantee the correct functioning of the platform, it is necessary to verify that, in correspondence with the URL SERVER ADDRESS OF SIGNALR field inside the GENERAL tab, the IP address and the relative port have been correctly indicated to allow the server to be reached at the IP address specified through the indicated port. In particular, the IP address must correspond to that of the server on which the component was installed; the IP address has to be specified in the format http://serveripaddress:80 if you are using HTTP protocol or http://serveripaddress:443 if you are using HTTPS protocol. Furthermore, if the server in question is protected by a specific firewall, it is necessary to open the TCP/IP ports in accordance with the rules of the same firewall to ensure in any case that the server is reached.
- IIS SERVER STATE – in order to guarantee the correct functioning of the platform, it is necessary that the IIS server where the application was published is active. Then verify that the IIS server is activated, that the publication port is the correct one and that the website is online and running through the IIS management console in Windows Server.
ADDRESS SERVER URL OF NODEJS
If the connection check performed through the CONNECT button doesn’t work, you must verify:
- SERVER IP ADDRESS AND CONNECTION PORT – in order to guarantee the correct functioning of the platform, the server must be reachable on the network at the IP address specified through the indicated port. If the indicated server is protected by a specific firewall, it is necessary to open the TCP/IP ports according to the firewall rules in order to reach the server in any case. To ensure that all the prerequisites listed above are met, check that in the GENERAL tab, in correspondence with the URL SERVER ADDRESS OF NODEJS field, the IP address indicated corresponds to that of the server on which the component was installed. The IP address format must be http://serveripaddress:3000 if the HTTP connection protocol is used and https://serveripaddress:3500 if the HTTPS connection protocol is used.
Note: in some cases, such as the failure of internal platform notifications, a reset of the NodeJS component may be necessary. In order to do this, perform the following actions:
- Access the server where the NodeJS component was installed.
- Open the task manager.
- End the process “Node.js: Server-side JavaScript”.
- Restart the BOOLEBOXSERVERSERVICE.EXE service from the Windows control panel.
- Click on the related CONNECT button in the GENERAL tab of the control panel of BooleBox to check the status of the component.
Note: in case of use of HTTPS protocol with TLS certificate supplied by the customer, it is necessary to configure the IIS bindings so that port 443 can be used. For the IIS configuration relating to port 443, please refer to this link.
Note: to proceed with the configuration of BooleBox On-Premises in accordance with the criteria imposed by the Common Criteria EAL2 + certification, it is necessary to configure the BooleBox On Premise site to listen only via the HTTPS protocol, by deactivating the HTTP port activated by default or by automatically upgrading the connection from HTTP to HTTPS.