Hide navigation sidebar
Hide table of contents sidebar
Skip to content
Quickstart Official documentation Setuphelpers Changelog FAQ
Back to top
View this page
Toggle table of contents sidebar

# 3. FAQ - Console Issues

## 3.1. Error message about package on the WAPT Console

### 3.1.1. Error when uploading package

Window showing that the uploaded package has signer certificate issue

The WAPT Console shows this error : `Error when uploading package : EWaptForbidden('Host matching package UUID_HOST does not trusted signer certificate)`.

You have this error when you try to upload a WAPT package but the used certificate which signed package is not present in your computer’s ssl WAPT install location folder. Be reminded, if you have a WAPT Server running on Windows to not lauch the WAPT Console on the server. Add the WAPT certificate which signed the package in your computer’s ssl WAPT install location folder then retry.

### 3.1.2. Error locale

Window showing that the WAPT Console does not find a package

The WAPT Console shows this error in two situations.

#### 3.1.2.1. Package does not exist in the repository anymore, yet a host needs it

There are two possible solutions:

- Try to get package anew from Tranquil IT’s store.

- Delete the package from the host dependencies.

#### 3.1.2.2. When you try to install a package with a locale that is unknown to the host

There are two possible solutions:

- Download the WAPT package having the matching locale from Tranquil IT’s store.

- Edit your WAPT package and set in the `control` file the option `locale` with the correct locale (`locale=en,fr`).

## 3.2. Error message when opening the WAPT Console

### 3.2.1. Version check

The WAPT Console version is not the same as the version of the WAPT Server. Upgrading the WAPT Console to the same version of the WAPT Server is the recommanded course of action.

### 3.2.2. Connection refused

The WAPT Console can not contact the WAPT Server on port 443:

- Check whether the Nginx web service is running on the WAPT Server.

    systemctl status nginx

- If Nginx is not running, restart the Nginx service.

    systemctl restart nginx

- If Nginx still does not start, you will need to analyze the journal logs in:

  - `/var/log/nginx/` on Linux;

  - `C:\Program Files (x86)\wapt\waptserver\nginx\logs` on Windows.

### 3.2.3. Service unavailable

It is possible that the WAPT Server service is stopped:

- Check whether waptserver is running.

    systemctl status waptserver

- If the command returns an error, then start the waptserver.

    systemctl start waptserver

### 3.2.4. Error connecting with SSL … verify failed

The WAPT Console seems not to be able to verify the WAPT Server’s HTTPS certificate.

Attention

Before doing anything, be sure that your are not facing a MITM attack!

Note

If you have just rebuilt your WAPT Server and that you use a self-signed certificate, you can recover the old keys of your old WAPT Server in `/opt/wapt/waptserver/apache/ssl`.

- Close your WAPT Console.

- Delete the folder `%appdata%\..\Local\waptconsole`.

- Launch the command `wapt-get enable-check-certificate`.

- Be sure that the previous command has gone well.

- Restart the WAPT service with `net stop waptservice && net start waptservice`.

- Restart the WAPT Console.

In case you do not use the certificate pinning method, this tells you that the certificate sent by the WAPT Server can not be verified with the python certifi bundle of certificates. Be sure to have the full chain of certificates on the WAPT Server.

### 3.2.5. I can’t do anything in the WAPT Console, everything is greyed

The WAPT Console seems locked, you can not execute any action, everything is greyed.

If you are connected with another user than the Superadmin, the ACL rules applied to your profile may not be set properly.

To fix this, close the WAPT Console and open it with the Superadmin account. Then, go to Tools ‣ Manage Wapt users and rights. Here, you will see the user in the list, give the user the appropriate permissions, then save and close the WAPT Console. Re-open the WAPT Console using your login.

## 3.3. Managing the location of machines in WAPT: Updating the Organisation Unit (OU)

The WAPT server does not automatically determine the location of a newly deployed machine. This information is transmitted by the WAPT agent (installed on the machine) to the server, based on the data available at the time of communication.

The key on the machine is here : HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionGroup PolicyStateMachineDistinguished-Name

Case of a machine moved to a new OU

If the machine has not yet received the information indicating that it belongs to a new OU, it transmits to the WAPT server the location that it knows at that time (generally the old OU).

To check the location known by the machine :

- In the WAPT console, identify the machine concerned.

- Go to the Hardware Inventory tab.

- Look for the key computer_ad_dn its value corresponds to the location (OU) that the machine has communicated to the server.

How to correct the location of the machine

If the value of computer_ad_dn corresponds to the old OU, there are two solutions for forcing the update:

> Via the command prompt:

> Run the following command on the machine:

>     gpupdate /force

> Via the WAPT console:

> - Select the workstation concerned.

> - Right-click > Windows Computer Management.

> - Choose Update AD Group Policies on hosts.

Once the update has been performed, the machine should appear in the new OU in the WAPT inventory.