[RESOLVED] 502 socket.io error after updating to 2.6

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
impulse
Messages: 4
Registration: Oct 08, 2018 - 09:06

December 30, 2024 - 10:15 AM

Hello everyone,

After updating to version 2.6, access to the console is impossible; I am left with the following logs in the NGINX console:

Code: Select all

2024/12/30 09:58:54 [error] 14720#15060: *73 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 192.168.16.8, server: 192.168.16.5, request: "GET /socket.io/?uuid=6ECFF6E8-9416-419E-8BF5-01B8A7733630&EIO=3&transport=polling&t=1735549133419-0 HTTP/1.1", upstream: "http://127.0.0.1:8080/socket.io/?uuid=6ECFF6E8-9416-419E-8BF5-01B8A7733630&EIO=3&transport=polling&t=1735549133419-0", host: "192.168.16.5"
2024/12/30 09:59:27 [error] 14720#15060: *75 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 192.168.16.5, server: 192.168.16.5, request: "GET /ping HTTP/1.1", upstream: "http://127.0.0.1:8080/ping", host: "192.168.16.5", referrer: "https://192.168.16.5"
2024/12/30 09:59:27 [error] 14720#15060: *77 CreateFile() "D:/wapt/waptserver/repository/wapt/ping" failed (2: The system cannot find the file specified), client: 192.168.16.5, server: 192.168.16.5, request: "HEAD /wapt/ping HTTP/1.1", host: "192.168.16.5", referrer: "https://192.168.16.5"


I don't know why the server is trying to connect to port 8080; there's nothing listening on that port, and to my knowledge, Wapt doesn't use it

Does anyone have any ideas?
- Windows Server 2022 + Wapt Discovery 2.6.0.16174

Thanks in advance,
Last edited by impulse on 06 Jan 2025 - 07:54, edited 1 time.
High
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

January 3, 2025 - 5:16 PM

Hello,
Could you please verify that you have both Visual Code Redist x64 and x86 installed on your WAPT server?
Once installed, you can restart the WAPT server installation.

Sorry for the inconvenience!
Bertrand
High
impulse
Messages: 4
Registration: Oct 08, 2018 - 09:06

January 6, 2025 - 7:54 AM

blemoigne wrote: ↑January 3, 2025 - 5:16 PM Hello,
Could you please check that you have both Visual Code Redist x64 and x86 installed on your WAPT server?
Once installed, you can restart the WAPT server installation.

Sorry for the inconvenience!
Bertrand
Good morning,

Thanks, after updating the redistributables, I reinstalled the latest version and it works again :D

Good day,
High
Locked

Return to "WAPT Server"


  • To go further with WAPT