Post-installation checklist

Once Wialon Local is successfully installed, several important steps are required to ensure stable, secure, and efficient operation of your system.
This checklist guides you through the essential configurations after installing Wialon Local and will help you establish a reliable environment for long-term use and smooth daily operation.

IPv6 must be disabled as it can interfere with Wialon Local operations. To check this:

1. Edit /etc/sysctl.conf and add these lines.
   Example. In this example, lo and eth0 are the network interfaces. Use interfaces displayed when using “ip a”.

   net.ipv6.conf.all.disable_ipv6 = 1
   net.ipv6.conf.default.disable_ipv6 = 1
   net.ipv6.conf.lo.disable_ipv6 = 1
   net.ipv6.conf.eth0.disable_ipv6 = 1

2. Run sysctl -p to apply those changes.

3. Edit /etc/hosts and comment out or remove the IPv6 localhost line: # ::1 ip6-localhost ip-6 loopback

4. Apply changes and restart services:

   service nginx restart
service wlocal restart

To indicate where to point the GPS devices:

1. In the administration system, navigate to System and go to the Settings section.
2. Enter the following information:

• Hardware IP: Your server’s static public IP address (for example, 192.168.1.100)
• Hardware DNS: A domain name pointing to your server (for example, devices.yourcompany.com)

3. Save the configuration.

This step is essential for monitoring server health and receiving critical alerts.

1. In the administration system, navigate to System and open the Mail system section.
2. Enter administrator email address.
3. Configure SMTP settings if using an external mail server.
4. Test email delivery to ensure notifications work.

To prevent unlimited data growth and manage storage costs:

1. In the administration system, navigate to Wialon and open the Default billing plan settings section.

2. Set History period (in days) for how long you want to keep the following information:

• Unit messages and tracks
• Reports and statistics
• Event history

This becomes the maximum limit for all subordinate billing plans.

This step is required if you want to use URLs instead of IP addresses.

1. Register or obtain at least 2 domain names:

• A name for CMS Manager (for example, cms.yourcompany.com)
• A name for Web Monitoring (for example, monitoring.yourcompany.com)

2. Create A-type DNS records for each domain:

• Point to your server’s public IP address
• Allow 24-48 hours for DNS propagation

3. In the administration system, navigate to Wialon and go to the Sites section.
4. Add domain names to corresponding sites.
5. Save the configuration.

To secure web traffic and enable HTTPS access, use the following options.

1. In the Sites section, go to Advanced settings and select Let’s Encrypt as certificate type.
2. Click Save.
3. Wait 1-2 minutes for automatic generation.
4. Verify that HTTPS access works.

1. Obtain SSL certificate from commercial provider.
2. Ensure you have the full certificate chain.
3. In the Sites section, go to Advanced settings.
4. Select the Custom certificate type.
5. Upload private key file.
6. Upload certificate chain file.
7. Save configuration.

Configuring the backup server protects against data loss and ensures business continuity.

1. Provide an identical server (same specs, OS version).
2. Configure as backup in the administration system.
3. Set up an automatic synchronization schedule.
4. Test failover procedure.
5. Document recovery process.

Establishing an account hierarchy organizes users and manages permissions effectively.

1. Create a top-level dealer account.
2. Set up client accounts under the dealer.
3. Define user accounts within each client.
4. Assign appropriate access rights:
   • Administrators: Full system access
   • Managers: Client management
   • Users: Unit monitoring only

This step prevents system overload from excessive API usage.

1. In the administration system, navigate to System and find the Limitations section.
2. Adjust from defaults:
   • Request execution time: Set based on expected load.
   • Active sessions for IP: Limit per user type.
   • Upload file size, MB: Prevent large downloads.
3. Monitor usage patterns and adjust as needed. Follow this verification checklist:
   • Server accessible via configured IP/domain.
   • Email notifications working.
   • SSL certificates active (if configured).
   • User can create and track units.
   • Backup system operational (if configured).

This step controls parameters of real-time data processing and allows recalculation of real-time data for any specific unit. Without this setting, events (trips, fuel fillings) will not be detected in the mobile application.

1. In the administration system, navigate to System and find the Events section.
2. Set the Process history for N days value:

• Recommended: 1-3 days.
• Must NOT be 0 or empty (processes entire history, causing extreme load).
• Values above 3 are not recommended (may cause high server load).

3. Save the configuration.

What this does: Messages older than the configured number of days will not be processed for real-time features, such as notifications, geofences, and others.

With the basic configuration complete, proceed to:

• Create your first units.
• Configure devices to send data to your server.
• Set up reports and notifications.
• Train users on the system.