WAPT 2.3 glpi-plugin-export-to-glpi10 problem

[chris2b]

Good morning,
I just installed GLPI 10.0.0.7 and I just updated my WAPT server to version 2.3.
I wanted to deploy the glpi-plugin-export-to-glpi10 package, but when I do the operation the Audit Status is in error and I admit I don't understand the error.
Furthermore, at no point is the address of my glpi server requested, I still modified the waptserver.ini file which is in the conf folder.

Error message:

Code: Select all

"Auditing eplborgo-glpi-plugin-export-to-glpi10
Audit aborted due to exception: HTTPSConnectionPool(host='mywapt.mydomain.lan', port=443): Max retries exceeded with url: //api/v3/hosts?columns=host_audit%2Fglpi%2Fupload%2Fvalue%2Flastid,host_audit%2Fglpi%2Fupload%2Fvalue%2Fhash&limit=10000 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x013C59E8>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))"

Has anyone else experienced this problem and perhaps found a solution or at least a lead on how to resolve it?
THANKS

[sfonteneau]

Hello,

on the machine that has the glpi-plugin-export-to-glpi10 package

, go to: The files in /opt/wapt or C:\Program Files (x86)\wapt\private depending on the OS

, then edit the glpi.ini and wapt_api.ini files

[chris2b]

Hello,
thank you for your reply.
The problem is that the glpi.ini and waptapi.ini files were missing from the wapt/private folder. I found them in a private folder at the root of C:/ and copied them, but it didn't change anything, even after modifying them.
My second issue is that the Wapt folder is on C: and not in C:/Program Files/.
So I'm wondering if it wouldn't be better to start with a clean server and a clean installation, making sure to back up the certificate beforehand.
Since the agents are correctly installed on my client machines, they will be uploaded to the server, right?
Thank you.

[dcardon]

Hello Christophe,

actually the new GLPI synchronization module is no longer included in the WAPT server but as a WAPT package which is installed and run by the agent. On the Windows server, the WAPT agent is in the same directory as the server, so in c:\wapt. If you install the synchronization package on a WAPT client, then the agent will be installed by default in c:\program files (x86)\wapt.

Regards,

Denis

[dcardon]

Hi Christophe,

were you finally able to resolve your problem? Can I close the thread now?

See you soon,

Denis

[chris2b]

Hello,
no, sorry, I've had other problems.
The server is malfunctioning, and I'm wondering if starting with a clean machine and reinstalling the WAPT server wouldn't be a better idea for me.
Especially since I have training in May.
My only question is, if I start with a clean machine and a clean WAPT server, will my client workstations be able to connect properly, given that they have the agent installed?

[sfonteneau]

The only question I have is if I start again on a clean machine and a clean WAPT server, will my client workstations be able to connect to it properly since they have the agent?

To avoid problems:

You need to use the same certificate that signs the packets.
The same prefix
The same DNS name (and HTTPS certificate if verification is enabled)

[chris2b]

Hello,
okay, thank you very much.
I'll go with this solution so I can start the training on a clean slate.
You can close the topic
Thank you.