This article applies to IceWarp EPOS and newer (14.0.0.0)

After releasing IceWarp EPOS, loads of new features have been added. One of them is a short informational window, which informs the user in case some IceWarp microservice is unavailable.

In case an informational window is shown during login into an IceWarp webclient (see the figure below) or/and some of the microservices are not reachable, there are several configurational steps which need to be checked.

Check if your license is valid

To do that, login into a remote console and check license status. Or you can use web administration. For more information about management tools, please visit the IceWarp documentation portal.

Check network connection

For the proper function of IceWarp microservices, network configuration must be set properly. The following table shows network ports which need to be opened.

For a full list of communication ports, see the appropriate article. 

General description of IceWarp microservices

Dashboard

1. The user’s browser requests the server to open Dashboard/Notes in the WebClient.
2. Dashboard/Notes Interface is uploaded from the Interface Microservices Cloud.
3. API Microservice Cloud requests data from the server and transforms it to a form readable for Dashboard.
4. As soon as the data received from the server is transformed, API Microservices sends it to the user’s browser.

Problems can occur in Step 3, namely in communication between the server and the API of the Microservices. If the latter cannot access the server because of some network issues, the application icon is not visible.  Since the data is stored on the server in a format, which is not readable for the user’s interface (downloaded from the Interface Microservices), it needs to be transformed by the API Microservices. Any changes made by users go to the API Microservices, which transforms them into a form suitable for storage and sends them back to the server.

The dashboard is a cloud microservice; however, it does not store any user's data on the on-prem server except the background images.

Documents

When the user wants to change any of his documents, the file is sent to Microservices Cloud via an encrypted channel. In the Cloud, it is unpacked and presented as a WebClient application with all functionality. As soon as the changes are made, the file is sent back to the server and stored there.

1. The user’s browser sends a request to open WebDocuments in the WebClient. Which are stored on the IceWarp server (on-premise or in-Cloud). The server directly sends the documents to the user’s browser.
2. If the user is making changes in the documents, the server forwards the request to WebDocuments Interface Microservices Cloud and sends the documents there for processing. In the Microservices Cloud, the document is unfolded and shown to the user in the window together with all functionality.

The server loads the Webclient interface and transforms the data to be displayed in the user's browser.

There is a firewall on the server’s side, which controls the incoming traffic. In some cases, it can prohibit the incoming connection between the server and Microservices. Server and Microservices Cloud communicate via HTTPS. Thus the port which receives the incoming traffic has to be open for it. As communication is initiated by the server and not by Microservices, the connection is more likely to be established.

Conferences

1. The browser sends a request to open Conferences in the WebClient. The latter is stored on the IceWarp server (on-premise or in-Cloud).
2. The server addresses Cloud Microservices as a database, and a totally new application is opened to the user’s browser. No data is processed in Microservices Cloud; it works only to open a new app.

Conferences are scheduled on the server. All user interactions are held in the Microservices Cloud; only the user interface is stored there. However, all information on the meetings, contacts, history, etc., is stored on the server.