[Resolved] Machines not visible after 1.8 installation, OK after 1.8.1

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
jeancharles
Messages: 21
Registration: June 11, 2019 - 10:02

January 30, 2020 - 3:11 PM

Hello,
I updated WAPT from 1.7.4 to 1.8 on Windows without any issues. I can see all the existing machines without any problems.
The issue is that the new machines are not visible; they are created, but I can't install anything.


In the performance monitor, I can see the connections to the WAPT server via TCP/443 and TCP/80, but they don't appear in the console.
I also can't see the self-service packages.

The result of `wapt-get update-status` is: `
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
waptserver is not available or error in inventory. Update of status not properly sent`.

I can ping the WAPT server, and accessing the local WAPT site with Edge is OK.

C:\Users\> wapt-get update
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
Update package list from https://svwapt01/wapt, https://srvwapt01/wapt-host
2020-01-30 10:51:30,392 CRITICAL Error merging Packages from https://srvwapt01/wapt into db: HTTPError: 400 Client Error: Bad Request for url: https://srvwapt01/wapt/Packages
Total packages: 0
Added packages:

Removed packages:

Discarded packages count: 0
Pending operations:
upgrade:
additional:
install:
remove:
Repositories URL:
https://srvwapt01/wapt
https://srvwapt01/wapt-host

EDIT: resolved after migration to 1.8.1 server and agents.
Last edited by jeancharles on Feb 14, 2020 - 4:10 PM, edited 1 time.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 30, 2020 - 3:53 PM

Can you provide us with more information about your configuration?

- Registration method
- Windows or Linux server?
- Is access to the repository restricted (certificate authentication on the client)?
jeancharles
Messages: 21
Registration: June 11, 2019 - 10:02

January 30, 2020 - 4:52 PM

Agent deployed via GPO (always)

on a Windows 2012 R2 server

. No access restrictions to the repository.

If any logs would be helpful, please let me know.
jeancharles
Messages: 21
Registration: June 11, 2019 - 10:02

January 31, 2020 - 09:49

I uninstalled agent 1.8 and manually installed agent 1.7.4, and bingo, the applications are visible.
Something must be missing in agent 1.8 regarding machine registration or server connection?

I can use self-service in 1.7.4, but I still don't have a reachable status.
Locked