Stretch Web Interface continuous loading

Recently, after updating my ROS workspace, I can no longer load the Stretch Web Teleop.

The ROS workspace had no issues updating. Here is the log: Defaulting to user installation because normal site-packages is not writeableR - Pastebin.com

Here is the log from stretch_system_check.py:

For use with S T R E T C H (R) from Hello Robot Inc.
---------------------------------------------------------------------

Model = Stretch 3
Tool = DexWrist 3 w/ Gripper
Serial Number = stretch-se3-3090


---- Checking Hardware ----
[Pass] Comms are ready
[Pass] Actuators are ready
[Pass] Sensors are ready
[Pass] Battery voltage is 13.4 V

---- Checking Software ----
[Pass] Ubuntu 22.04 is ready
[Pass] All APT pkgs are setup correctly
[Pass] Firmware is up-to-date
[Pass] Python pkgs are up-to-date
[Pass] ROS2 Humble is ready

Web Teleop is started using:
./launch_interface.sh -m ~/stretch_user/maps/demo_area.yaml

Trying to load the https://localhost/operator link, the web page just has a continuous loading symbol.

Looking into the console log of the web page, this error is continuously shown:

Created RTCPeerConnection webrtcconnections.tsx:126:15
Signaler ready! index.tsx:105:11
Hanging up webrtcconnections.tsx:152:13
Leaving. My role: undefined. LocalSignaling.ts:53:13
joining room as operator webrtcconnections.tsx:141:13
Connected to local socket LocalSignaling.ts:14:15
Operator failed to join robot room index.tsx:113:15
Hanging up webrtcconnections.tsx:152:13
Leaving. My role: undefined. LocalSignaling.ts:53:13
joining room as operator webrtcconnections.tsx:141:13
Operator failed to join robot room index.tsx:113:15
...

Let me know if any other logs are needed for debugging!

Hi @keshavshankar,

Thanks for sharing all the details.

Could you please follow the steps in the Troubleshooting section in the Stretch Web Teleop README? The main action there is to collect and send the two log files (Web Teleop logs and robot-side launch logs) to the Hello Robot Support team at support@hello-robot.com so we can further investigate.

Best regards,
Jason