[RESOLVED] 502 socket.io error after updating to 2.6
Published: Dec 30, 2024 - 10:15
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:
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,
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,
