By default, two sites are available: one is of the Wialon Web type and the other is of the CMS Manager type. You can find the list of the purchased modules on the License tab.
To log in for the first time, use the root user's login and password.
There are seven types of sites:
- CMS Manager (the management system where accounts, users, units, retranslators are created);
- Wialon Web (the main monitoring interface where the end users monitor their units, generate reports, and so on);
- Wialon Mobile (a simplified monitoring interface for mobile devices);
- Fleetrun (the service for managing vehicle maintenance);
- NimBus (the service for monitoring passenger transportation);
- Logistics (the service for working with orders);
- Hecterra (the service for controlling agricultural works).
If you activate additional Wialon Web sites (the Extra site module), you can change their type to CMS Manager. You can also add several Wialon Mobile sites. Each of the additional sites should have its own DNS. The sites of the Wialon Web type can have a personal design (paid option).
For running the applications of the Nimbus, Hecterra, and Fleetrun type, access to https://app-local.wialon.com (port 443) should be provided on the side of Wialon Local.
The Sites section is a table where the DNS and type of each site are specified. To open the required site, click on its DNS link.
To open the site settings, click on the Edit button next to its name.
To the right of the Edit button, there is a button to start/stop the site. If you stop the site, the users cannot log in to the system.
After starting (restarting) Wialon Local, all sites are loaded (reloaded) regardless of their previous state.
If a site works using the https protocol, a lock icon is displayed next to its name. In the tooltip of the icon, you can see the information about meeting the requirements for the certificate parameters and the name of the certificate authority (the Issuer line). The colour of the icon depends on the reliability of the SSL certificate.
|The SSL certificate is valid because the requirements for all the parameters are fulfilled: the SSL certificate corresponds to the key, the MD5 hash of the certificate and the key is the same, the DNS of the certificate corresponds to that of the site, the validity period has not expired, the chain is complete.|
|The SSL certificate is self-signed (that is, not received from a certificate authority and loaded by the user, but generated by the server) or the certificate chain is not complete while the other requirements are fulfilled. In the latter case, you can try to restore the chain using the Fix button displayed in the SSL certificate line in the advanced settings.|
|The SSL certificate is invalid for one or several reasons: the SSL certificate does not correspond to the key, the MD5 hash of the certificate and the key is not the same, the DNS of the certificate does not correspond to that of the site, the validity period has expired.|