Tranquil IT Forum

WAPT Self-Service: Error 666

Good morning,

We are encountering the following error on a number of our client workstations:

When the self-service is launched on the user's workstation, it displays "No results". If the user attempts to log back in, the following message appears: "666 Client Error: for url:" https://127.0.0.1:8088 :
If this message is confirmed, the self-service then changes to: "Authentication on the WAPT Local service has failed"
However, if we try to authenticate with an administrator type account, is the connection to Selfservice functional?.

Do you have any suggestions for resolving this problem?

Thank you in advance.

Best regards,

Hello Pierre-Alexis,

which version of Wapt are you using?

Do you have a value defined for the `service_auth_type` parameter [1] in `wapt-get.ini`?

Are the machines experiencing the problem in an Active Directory domain?

Denis

[1] https://www.wapt.fr/fr/doc/wapt-self-se ... lf-service

Hello,

Thank you for your feedback.

We are using the following version of WAPT: 2.6.1.17705.

All of our workstations have this value defined in: service_auth_type=filetoken.

The machines experiencing problems are indeed in our Active Directory and connected via Ethernet.

Best regards,

Pierre-Alexis DEQUIDT

Hello Pierre-Alexis,

However, if we try to authenticate with an administrator type account, is the connection to Selfservice functional?.

-> Is it via login/password on the self-service or is it by opening a session as a local administrator, then launching the self-service?.

The error message implies that the self-service client failed to contact the waptservice running locally on the machine.

Do you have any messages in the antivirus console that might indicate it has blocked access to 127.0.0.1?

Sincerely,

Denis

Thank you for your feedback.

Is this a login/password issue on the self-service portal? ==> Yes, it's from the user session. When you open the self-service portal, error 666 appears. You try to log in with your account (Authentication on the local self-service portal failed). Then, with an admin account, access to the self-service portal works fine.

This is where I have doubts about whether it's actually access at 127.0.0.1:8088 that's being denied, because that would be the case for all connections, not just the user's.

I'll try to get the logs from a machine experiencing the problem, but since we can't reproduce the bug, I have to troubleshoot with other sites in parallel.

Best regards,