Hello,
In addition to my support ticket created today (Ticket No. 0014174), I've noticed that my PC used for remote work (and the others on my network with the same configuration) is no longer communicating with the console.
The command `wapt-get register` returns the following error:
666 Client Error: for url:https://127.0.0.1:8088/login.
Testing for this URL , http://localhost:8088/, returns: no page is displayed , only: The connection has been reset.
Could you please help me?
Thank you in advance for your response.
wapt-get register: 666 client error
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
Hello,
Following our discussion, it seems the problem stems from the proxy.
WAPT agents are not using the proxy configured for the browser. They attempt to establish a direct connection with the WAPT server, which fails if the VPN network blocks direct connections or if a proxy is required.
The points to check are:
* DNS
* Firewall and network rules
* Logs (/var/log/waptserver.log) and proxy logs, if applicable.
Best regards
Following our discussion, it seems the problem stems from the proxy.
WAPT agents are not using the proxy configured for the browser. They attempt to establish a direct connection with the WAPT server, which fails if the VPN network blocks direct connections or if a proxy is required.
The points to check are:
* DNS
* Firewall and network rules
* Logs (/var/log/waptserver.log) and proxy logs, if applicable.
Best regards
