[Bug]: [2024/05/23 15:19:40:0909] W: [wsicli|5a|WS/h1/default/m-579da5db.kinesisvideo.ap-southeast-]: lws_client_ws_upgrade: got bad HTTP response '403' 2024-05-23 15:19:40.091 VERBOSE lwsWssCallbackRoutine(): WSS callback with reason 1 2024-05-23 15:19:40.091 WARN lwsWssCallbackRoutine(): Client connection failed. Connection error string: HS: ws upgrade response not 101

[123zhj]

Please confirm you have already done the following

• I have searched the repository for related/existing bug reports
• I have all the details the issue requires

Please answer the following prompt

• This issue is replicable using the unmodified sample application

Describe the bug

Problems occur when running./kvs_webrtc_demo demo1 on the development board after cross-compiling

Expected Behavior

View the video stream on the test site

Current Behavior

没有什么可预览的

Reproduction Steps

没有什么可预览的

WebRTC C SDK version being used

1.10.2

If it was working in a previous version, which one?

no

Compiler and Version used

arm-linux-gnueabihf-9.1.0

Operating System and version

Linux4.9.84 armv7

Platform being used

arm

[disa6302]

@123zhj ,

Could you provide full logs and details on how you are building this SDK? Are you building with dependencies ON/OFF? Are you using openssl or mbedtls?

[123zhj]

，

您能否提供有关如何构建此 SDK 的完整日志和详细信息？您是否使用依赖项 ON/OFF 进行构建？您使用的是 openssl 还是 mbedtls？

I'm use mbedtls.
CMakeLists.txt
CMakeOutput.log
demo_sigmaster.txt
CMakeLists.txt is my modified file, CMakeOutput.log is the Cmake compilation output file, demo_sigmaster.txt is ./kvsWebrtcClientMaster Run output log file

[disa6302]

Thank you for the details.

What is your cmake command? Are you running with BUILD_DEPENDENCIES=ON or BUILD_DEPENDENCIES=OFF? Are you using system libraries?

[123zhj]

谢谢你的细节。

你的 cmake 命令是什么？您是在 BUILD_DEPENDENCIES=ON 还是 BUILD_DEPENDENCIES=OFF 的情况下运行？您使用的是系统库吗？
I'm using the Cmake command which is cmake... But I modified the CMakeList.txt file.I didn't use either of these options.I think I'm using a system library.

[123zhj]

Thank you for the details.

What is your cmake command? Are you running with BUILD_DEPENDENCIES=ON or BUILD_DEPENDENCIES=OFF? Are you using system libraries?
Can you tell me the cause of this problem? Because I compile in the same way on other embedded platforms, it works.

[disa6302]

@123zhj ,

1. Does this embedded platform have any firewalls or proxy that could be blocking the WebSocket connection?
2. What is the difference between the embedded platforms where it works and the ones it does not?

[vasoyanikhil]

@disa6302 : I am having the same issue. Please find below the logs. Can you please help on this?

[2024/06/14 05:15:00:7903] W: [wsicli|4d|WS/h1/default/m-3bffc0cd.kinesisvideo.ap-south-1.am]: lws_client_ws_upgrade: got bad HTTP response '403'
2024-06-14 05:15:00.790 WARN lwsWssCallbackRoutine(): Client connection failed. Connection error string: HS: ws upgrade response not 101
[2024/06/14 05:15:00:7911] N: __lws_lc_untag: -- [wsicli|4d|WS/h1/default/m-3bffc0cd.kinesisvideo.ap-south-1.am] (0) 1.397s
2024-06-14 05:15:00.791 PROFILE executeConnectSignalingState(): [Connect signaling call] Time taken: 19761 ms
2024-06-14 05:15:00.791 ERROR signalingConnectSync(): operation returned status code: 0x0000000f

After I got the above error, I started the live stream, but I am not able to see the media stream on my mobile; it shows a blank screen. After I stopped the live stream from my mobile, I see still on device live stream running.

[Whatmam]

I also discovered the cause of the problem as described above.
The solution is to ensure your system time is set correctly.

[hassanctech]

@123zhj Can you please confirm if you have the same issue still after correcting your system time? I have also seen this same issue when the system time is incorrect, then the signature on the request will be outdate (it is valid only for 5-10 mins from the current time) so server will reject it. Make sure system time is correct please and report back if your issue is resolved so we can close out this ticket.

[github-actions]

This is a very old issue. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.