Job registration error (Unable to register)

[silica]

Good morning,

I just updated my server to version 2.6.1.17576
I have a post that isn't showing up despite the new agent being installed.

I tried:
- Uninstalling the agent + deleting the files
- Deletion of the position (with deletion in the database) in the console
- Installation of the new agent

The installation is OK, but the device is not showing up in the console.

Result of wapt-get register :

Code: Select all

Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
Registering host against server: https://srvwapt.mon.domaine
FATAL ERROR : Unable to register: waptserver https://srvwapt.mon.domaine not available

What else can I do?

Sincerely

[sfonteneau]

Can you try launching it?

Code: Select all

wapt-get testperf

Simon

[silica]

Here is the result of wapt-get testperf:

Code: Select all

Server: https://srvwapt.mon.domaine
Authentication required for server:
Server CABundle: C:\Program Files (x86)\wapt\ssl\server\srvwapt.mon.domaine.crt
Server client certificate:
Server client key:

Waptserver https://srvwapt.mon.domaine Admin User: admin
Waptserver Password: xxx
********************
Unable to login with provided credentials: Http client error: THttpClientSocket.DoTlsAfter: TLS failed [EOpenSslNetTls TOpenSslNetTls.AfterConnection connect: OpenSSL 30500040 error 1 [SSL_ERROR_SSL (error:0A000086:SSL routines::certificate ve


Authentication on server failed

If I understand correctly, there's a problem with the certificate somewhere?

[sfonteneau]

The certificate present on the Windows machine:

Code: Select all

type "C:\Program Files (x86)\wapt\ssl\server\srvwapt.mon.domaine.crt"

definitely does not match the one present on the server:

Code: Select all

cat /opt/wapt/waptserver/ssl/cert.pem

Can you check?

[silica]

Okay, so... I'm completely lost. Let me start from the beginning:

I don't have a certificate in C:\Program Files (x86)\wapt\ssl\server.
It's in C:\Program Files (x86)\wapt\ssl\.

Indeed, it doesn't match /opt/wapt/waptserver/ssl/cert.pem.

What I don't understand is that on a working machine, the certificate doesn't match either.

The certificates on those machines match /opt/wapt/waptserver/ssl/cert.pem.bak, which is there for reasons I don't even remember.
I don't know how I managed to mess it up.

Furthermore, I've noticed that I have a third certificate in /opt/wapt/waptserver/ssl/, which isn't self-signed, unlike the other two. It's a certificate generated with my company's CA.

I'd like to get all this sorted out.
I imagine with just one (self-signed) certificate? Both on the server and the workstation side.

[sfonteneau]

Wapt verifies the HTTPS certificate with this parameter in wapt-get.ini:

Code: Select all

[global]
verify_cert=

If it is at 1, there is a check with the consumer bundles
If it is 0 there is no check
If a file is specified, then check with that file.

In your testperf (in the log) it checks with C:\Program Files (x86)\wapt\ssl\server\srvwapt.my.domain.crt

So you seem to have a verification with a "Pinner" certificate (verify with wapt-get.ini)

You indicated "This is a certificate generated with my company's CA."

The file mentioned in "verify_cert" should therefore be your company's CA. (I assume)