On this page, you can start/stop Wialon Local manually, install updates, adjust mail server, and set important limitations.


Updates can come from two sources: either you have purchased something on the License page or Gurtam has published a new release for Wialon Local.

You can choose to install updates manually or automatically. If you enable the Auto install updates option, the system will automatically detect the availability of updates and install them immediately. If the option is disabled, you will be informed about updates in the log, and a corresponding phrase (such as 3 updates available instead of Everything is up to date) will appear near the checkbox. To see the list of available updates, click on the Release notes link. In the opened window, press the row with the date and time of the update to expand the list.

You can install updates manually either in the List of available updates window (the Install button) or in the System tab (the Install now link). Click the Installed lately link to see the list of adjusted updates.

No matter how you install updates, manually or automatically, Wialon Local will be restarted. This will cause restarting of sites, modems, etc., and all active sessions will be forcibly finished.

The currently used version of Wialon Local is indicated in the appropriate row.

Upon the arising of any failures connected with modules, you can change the situation by reinstalling them. To do so, click on the Update all button located on the System tab and then install the uploaded update.

Mail System

Here you can also indicate your email (the Administrator's email field​) which is used for the following: ​ - to reset the password in case you lose it; - to send system reports about available updates, occurring errors, deficient disk space, etc.

Among the additional software provided and installed together with the operational system Debian there is postfix specially adjusted for Wialon Local. It is used for sending mail (either to the administrator about Wialon Local operation or to end users with reports and notifications).

Sender's address is chosen in the following order (if one is empty, the following is taken):

  1. email from billing plan
  2. administrator's email (from the System page)

You may also adjust another SMTP server. In this case, all mail will go through it. When using a non-standard port, enter it in the host:port format.

Enter your SMTP server address. It may prove to be enough if you have your own SMTP server. However, if you use an external server for sending mail, you will need authorization. In this case, you enter your login and password you obtained in that mail system.

:!: When connecting to a third-party SMTP server, use the authorization without plain text encryption.

When finished, press Save and restart Wialon Local. To check if the mailing system is configured properly, you can press Verify. A test message will be sent to the administrator's email. You can also see the results of this check in the Log below.

Most mail systems perform special checks for spam messages. They compare the original IP address from which the messages go with the MX record of the sender's domain. If the MX record is not found, sending messages might be suspended, or the sender's address might be added to the grey list (this eventually might lead to total denial of processing and sending messages). To avoid such situation, when you register your sites related to Wialon Local, make sure that external IP address of the server is included in the MX records of the domain.


In the Process history for X days field, indicate the number of days valid for Events module. For example, if 5 days is indicated in this field, and your device sends messages older than 5 days (stored in the black box), then events are not recalculated.

If the module is not activated (the Active checkbox is not marked),

  • the Info tab of the mobile application displays only online data, and the History of movements is empty;
  • the Info tab of the mobile application does not display the information about sensors;
  • drivers' activities based on their assignment to units are not be formed;
  • notifications on fuel filling and theft do not work.

:!: The maximum number of days for history processing corresponds to 365 days. Though a large amount of information requires the corresponding time for processing, it is recommended not to exceed the value of several days.

Backup Servers

In this section, for each backup server, specify the DNS, port, and access key. These parameters are checked with the ones specified in the config.txt file of the backup server.

Settings and Limitations

In order to provide actual data, all the online queries have their execution time. If it is exceeded, the browser does not wait for an answer from the server and the query's execution stops. This restriction is 3 minutes for the reports and 5 minutes for the scripts.

To ensure a stable operation of the server and to prevent it from overloading you can adjust the limitations listed below.

Report execution timeout, s
If the execution of a report on the server exceeds this value, it is aborted. The recommended value is 300.

Script engine timeout, s
If the execution of scripts on the server exceeds this value, it stops. The recommended value is 600.

Loaded messages per user
The number of messages that can be loaded by a user into all user's sessions. If this limit is met, this user may have difficulties in executing reports, building tracks, importing messages, etc. The recommended value is 15,000,000.

Active sessions for IP
The maximum number of active sessions of one user from one IP address. The recommended value is 100.

Simultaneous heavy requests
By heavy requests, we mean message loading, report execution, etc. In this field, you indicate how many heavy requests can be processed simultaneously in a session. The recommended value is 3.

Failed logins for IP per minute
Maximum unsuccessful logins from one IP address in a minute. The recommended value is 10.

Successful logins for IP per minute
Allowed successful logins from one IP address in a minute. If these two limits are met, the IP address will be temporarily blocked. It can cause difficulty to log in to the system. The recommended value is 120.

Video server URL
Address of the video server.

ACL update timeout, s
The interval of recalculation of users's access rights to their units. The smaller the interval is, the higher is the load on the server. The recommended value is 500.

Hardware IP IP-address of the server to which the data from the units should be sent. It is displayed in the properties of all units in the Server address field.

Allowed advance in messages, s
Allowed timing advance in messages at which their delayed registration is carried out (values from 0 to 84600 are available). Applicable in cases when the device time is ahead of the server time.

Max size for uploading files
The maximum size of the uploaded files (the default value is 200 MB, the maximum allowed value is 2 GB).

Store registration time
An option that allows to store the time of message registration.

:!: If you leave these fields empty or fill them in with zeroes, there will be no restrictions.

Flespi MQTT Broker

The section is displayed if the applications that use flespi are purchased.

Enable the Active checkbox to work with such applications.

Flespi token is a key designed to connect to the flespi services and transfer the data of applications that use it. Flespi token is created automatically and provided free of charge, that it, there is no need to register it yourself. Token renewal is also automatic.

Was this helpful?
Thank you!