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,
WAPT Self-Service: Error 666
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
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
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
PA DEQUIDT
- Messages: 16
- Registration: Oct 27, 2025 - 4:18 p.m.
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
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
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Pierre-Alexis,
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
-> 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?.However, if we try to authenticate with an administrator type account, is the connection to Selfservice functional?.
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
PA DEQUIDT
- Messages: 16
- Registration: Oct 27, 2025 - 4:18 p.m.
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,
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,
