Installing Glovizor on Linux

Contents:

Supported Environment

This guide has been verified on Ubuntu Server 22.04 / 24.04 LTS and Debian 12 / 13 (x86_64, systemd). Ubuntu uses MySQL, while Debian uses MariaDB; Wine and the database server are installed from the standard repositories of the respective system.

For other Linux distributions, package names and installation commands may differ.

Note. It is recommended to install and run Glovizor under a dedicated Linux user account. You can use an existing user account. Run all Wine commands and perform the initial Glovizor configuration under the same selected user; use sudo only where explicitly indicated.

Back to Top

Installing MySQL / MariaDB

If the package list has not yet been updated after installing the system, run:

sudo apt update

Glovizor works with MySQL and MariaDB.

For Ubuntu:

sudo apt install mysql-server -y

For Debian:

sudo apt install default-mysql-server -y

Additional check.

To check the MySQL status:

systemctl status mysql --no-pager

The normal status is: Active: active (running).

Creating a MySQL User

Open the MySQL console:

sudo mysql

Create a Glovizor user for local connections. Replace <STRONG_PASSWORD> with your own password:

CREATE USER 'glovizor'@'localhost' IDENTIFIED BY '<STRONG_PASSWORD>';
GRANT ALL PRIVILEGES ON glovizor.* TO 'glovizor'@'localhost';
EXIT;

There is no need to create the glovizor database manually — it will be created through the Glovizor configurator.

Note. If the glovizor user already exists, you do not need to run CREATE USER again. If necessary, change the password of the existing user using the ALTER USER command.

Back to Top

Installing Wine

If apt update was already run in the previous step, you do not need to run it again.
Install Wine from the standard Ubuntu repository:

sudo apt install wine -y

Additional check.

To check the installed Wine version:

wine --version

On 64-bit Ubuntu, the command may additionally report that wine32 is not installed. If the Wine version is displayed, continue with the Glovizor installation.

Note. On a server without a graphical interface, Wine may display messages about DISPLAY/X server, tray window, or ntlm_auth. If the Glovizor console menu opens and the server components work, these messages by themselves do not require additional configuration.

Back to Top

Downloading and Extracting Glovizor

The Linux package can be downloaded from the Glovizor download page and uploaded manually to the home directory of the selected Linux user.

Alternatively, download the current package directly to the server:

cd ~
wget https://glovizor.com/files/glovizor.tar.gz

Create the working directory and extract the package:

mkdir -p ~/glovizor
tar -xzf ~/glovizor.tar.gz -C ~/glovizor
cd ~/glovizor

After successful extraction, the original archive can be deleted:

rm ~/glovizor.tar.gz

Additional check.

To check the main files:

ls -la

The directory should contain at least glovizorcfgc.exe, glovizorwebc.exe, glovizorgpsc.exe, install-service.sh, and uninstall-service.sh.

Back to Top

Configuring Glovizor

Run the console configurator without sudo:

cd ~/glovizor
wine glovizorcfgc.exe

Main Menu

=== Glovizor configuration ===

1. Database
2. Web
3. Logging
4. Win services
5. About
6. Exit

Database Connection

Open Database. The section menu is:

=== Database ===

1. Show settings
2. Edit settings
3. Test connection
4. Create database
5. Back

Open Edit settings and specify:

  • Server: localhost — leave the default value.
  • Database: glovizor.
  • User: glovizor.
  • Password: the password set when creating the MySQL user.

Save the settings and run Test connection.

During the initial installation, before the database has been created, the expected result is:

SQL server connection successful.
Database connection failed: #42000Unknown database 'glovizor'

Important. This result means that the MySQL connection and user account are working correctly. The error refers only to the missing glovizor database and is expected at this stage.

Run Create database, then run Test connection again. A successful result is:

Database created successfully.

SQL server connection successful.
Database connection successful.

Web and HTTPS

By default, Glovizor uses HTTP port 8080 and HTTPS port 443. In the Web section, enable Use HTTPS. There is no need to change the ports if the default values are suitable for the server. Leave HTTP enabled for the initial check.

Glovizor includes a self-signed TLS certificate. Therefore, when opening HTTPS for the first time, the browser will warn that the certificate is not trusted. Allow access to the site to continue. For permanent use, you can install your own trusted TLS certificate; its configuration is described separately and is not covered in this guide.

Note. Port 443 is a privileged Linux port. The install-service.sh script grants the Web service permission to bind to it using CAP_NET_BIND_SERVICE; running the entire service as root is not required.

Back to Top

Registering Glovizor Services with systemd

While in the Glovizor directory, run:

sudo bash install-service.sh

The script registers two Glovizor services:

  • glovizor-web.service — Web/HTTP/HTTPS server.
  • glovizor-gps.service — GPS tracker data reception server.

Both services start immediately and are enabled to start automatically when Linux boots.

After running the script, it should display:

Web: active
GPS: active

Verifying Operation

Service Status

systemctl status glovizor-web --no-pager
systemctl status glovizor-gps --no-pager

For both services, the normal status is Active: active (running).

Web Access

From another computer, open both addresses in a browser, replacing SERVER_IP with the IP address or domain name of the server:

http://SERVER_IP:8080
https://SERVER_IP

After the initial installation, the login page should open. Use the default account:

  • User: admin
  • Password: leave the field blank.

After the first login, it is recommended to set a password for the admin account immediately.

If both HTTP and HTTPS open successfully, the Web service is working correctly. After testing, you can disable HTTP in the Glovizor settings if necessary and restart the Web service:

sudo systemctl restart glovizor-web

Web Access Diagnostics

Use this section if the Glovizor Web interface does not open from another computer. The checks below help distinguish Glovizor operation issues from network or firewall restrictions.

Checking Web Access Directly on the Server

First, send an HTTP request to the local server address:

curl http://127.0.0.1:8080

Then check HTTPS. The -k option allows a connection using the self-signed certificate included with Glovizor:

curl -k https://127.0.0.1

If the Glovizor Web server is working, curl will return the page content — the HTML code of the Web interface. This means that Glovizor is accepting requests on the server itself.

Quick response code check. If you do not need to display the entire page, you can check only the HTTP response code:

curl -sS -o /dev/null -w "HTTP: %{http_code}\n" http://127.0.0.1:8080
curl -k -sS -o /dev/null -w "HTTPS: %{http_code}\n" https://127.0.0.1

Codes 200, 301, or 302 mean that the Web server is responding.

If It Works Locally but Not from Another Computer

If the local curl request returns the page or a valid HTTP response code, the Glovizor Web component is working. In this case, check access to ports 8080 and 443 in the server firewall, external firewall, or network/VPS control panel rules.

If the Local Request Fails

Check the Web service status and whether the required ports are listening:

systemctl status glovizor-web --no-pager
sudo ss -ltnp | grep ":8080"
sudo ss -ltnp | grep ":443"

If the service is active but the required port is not in the LISTEN state, check the Web settings in the Glovizor configurator and restart the service after making changes:

sudo systemctl restart glovizor-web

Additional automatic startup check.

Restart the server:

sudo reboot

After logging in again, check:

systemctl status glovizor-web --no-pager
systemctl status glovizor-gps --no-pager

Both services should start automatically.

Back to Top

Network Ports

The Web ports in use must be allowed in the server firewall and in any external firewall/VPS control panel. After adding GPS tracker models in the Web interface, also allow the TCP data reception ports configured for them.

Back to Top

Managing Services

Web

sudo systemctl start glovizor-web
sudo systemctl stop glovizor-web
sudo systemctl restart glovizor-web
systemctl status glovizor-web --no-pager

GPS

sudo systemctl start glovizor-gps
sudo systemctl stop glovizor-gps
sudo systemctl restart glovizor-gps
systemctl status glovizor-gps --no-pager

The Web and GPS services can be stopped and restarted independently.

Back to Top

Uninstalling Glovizor

First, remove the Glovizor services from systemd:

cd ~/glovizor
sudo bash uninstall-service.sh

The script will stop the Web and GPS services, disable automatic startup, and remove the registered service unit files.

After that, if the program files are no longer needed, delete the working directory:

cd ~
rm -rf ~/glovizor

If the installation archive was saved, you can also delete it:

rm -f ~/glovizor.tar.gz

Note. Removing the Glovizor services and directory does not delete the MySQL database or the Wine prefix ~/.wine. If necessary, they must be removed separately by the administrator.

Back to Top