Closed Pinkbyte closed 1 year ago
Image build should be completed in a few minutes..
Tried new docker image (1.5.7). Log verbosity is reduced, but, unfortunately, it is still an issue:
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0257 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0257 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.3963 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.3963 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0278 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0278 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0508 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0508 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0261 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0261 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0569 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0569 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0360 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0360 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0540 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0540 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0190 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0190 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0893 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0893 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0260 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0260 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0559 ms
[14:53:41 INF] HTTP GET /_blazor responded 200 in 0.0559 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0277 ms
[14:53:41 INF] HTTP POST /_blazor responded 200 in 0.0277 ms
Hm, there is an error message in browser:
[2023-10-12T11:57:00.192Z] Error: Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
Websockets are definitely not enabled in my nginx frontend setup. It would be nice if websocket requirement is mentioned in README
Update: i confirm, that enabling Websockets on frontend fixes this issue.
Websockets are definitely not enabled in my nginx frontend setup. It would be nice if websocket requirement is mentioned in README
Done, thanks for the hint
Steps to reproduce:
1) Run command:
2) open LAPS-WebUI interface in browser(authorization is not required to see the issue, login prompt is enough);
3) see enormous amount of logs like this:
LAPS WebUI: 1.5.5, used from docker