Hello. We have de following problem using NetZero 6.5 We deployed our application on IIS based on steps described in: https://docs.aspnetzero.com/documents/aspnet-core-angular/latest/Deployment-Angular-Publish-IIS
We enable websocket and all looks works ok. But when we try to open other tab with the same application or in other browser, one of these clients hang. Browser console shows:
WebSocket connection to 'ws:// test.xxxxxxx.cl:22742/signalr-chat?enc_auth_token=wNYmO41%2F48SHNstaLVXxHCCre29BZQl1NhC6NM3R3rzpXtPQxVzH6jEzA%2FQhXFN5tu6Fk7pO53uppm1mVXMZgxbyRVz26dnepi%2FFyB6axBY%2B6gq1GL%2BuRQgoiFUCjRN2p8w6LevViwKlHyWZZJZO1DGVSjAi1m2U%2Bog9pkHw9%2FR3sjOcoqJwt6m%2FiYjiV1p4dVM89FVKCqLU6LJBusZrJOaCMOgCGXb7hQBmhiuw8WjpBA0hh1B2jz%2FebTmrrY3zHzn%2BSnZg%2BAuaD3FKsq3p1apfLwtKjFt3DlAYGy2Hfapln5npL8uqqbLpjWgFs5chy08%2FNJtbGt4WPniE%2BPNRDVpahzGSNHldO24tCCahtBzs3z6C7o6maGvhbyafFzkIUSA9pTENS6IyAXPe%2Biv%2BtkmR56CT...y%2Fathk4KD6Nt5mAOl8PUk2DhG3%2BNSlT0e8rRKQtFbO0xxKsV7v41uQ5egYPaszPKePvid%2BQ7AUwyx2tXIhLBNITQ3VzDvCoBCK0s7aGoE3ELo%2FpZjuZWBC9%2FGlQ3uMcE1R10qjFZrw7ZbzHDrBss4d8%2B1lqLab0wDbl4W7IZDNRb753sG0lNCp8YO3lQ9NcWAhOYyB9BD7qOaQ4M12uBRfmKa8Z%2B56rxbb6J5LY58qw7hSFTFuJFMV%2FTP9hPmW%2BTtc3VXb5OiaAU2JVCBwdDtOUHCnm58mwdmsRau61qXhkj04RWVyrHICIMuqAgLu%2FJPtLAowZmKMhBfjwu9Hps43hhz%2FVfoDDh6A94CAjwWLiDQoLH9u7NH02x1B9kVsuGS5IbZaACQPv%2B%2FWo8lLhbaugH0v2SVaI42vVyjMb%2BEwf9eKXlNYbIIrv33KHDbIVqW53PPiNf&id=EP_qNm24YzNSbnDepvmzbw' failed: Error during WebSocket handshake: Unexpected response code: 404
Now, if we close one of these connections the other works OK again.
On local machine all work fine, but when we deploy to our test environment only one client works.
It looks like a websocket connection works only for one client connection. I we need that multiple clients use the application at same time.
Can anybody help us to find what configuration error we made?
Thanks in advance.
3 Answer(s)
-
0
What information in the application's log when
Error during WebSocket handshake: Unexpected response code: 404? -
0
Hello @maliming,
We also faced this same problem in our azure production environment. We get that 404 error code running signalR and we have multiple instances. We are getting thousands of 404 errors from it. We need to resolve this ASAP because we are in production and it is causing the servers to bug down during peak operations and we cannot afford a single minute of downtime. Please help. This is critical.
Btw we are on Angular + .NET Core v8.2
Thank you!
-
0
hi bitman
Please create a new question and shared some log of your application.
