System.InvalidOperationException: Insecure connection not allowed

[sentry]

Sentry Issue: UNITY-EXPLORER-QA9

System.InvalidOperationException: Insecure connection not allowed
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/SDKComponents/MediaStream/UrlResolverService.cs", line 97, in IsGetReachableAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/SDKComponents/MediaStream/UrlResolverService.cs", line 84, in ResolveDirectUrlAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/SDKComponents/MediaStream/UrlResolverService.cs", line 35, in ResolveAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/SDKComponents/MediaStream/UrlResolverServiceAnalyticsDecorator.cs", line 26, in ResolveAsync
  File "C:/workspace/workspace/p/Explorer/Assets/DCL/SDKComponents/MediaStream/Components/OpenMediaPromise.cs", line 59, in UrlReachabilityResolveAsync
...
(133 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Explorer Alpha Github Issue Creation

[github-actions]

Automated Triage

Issue type	bug
Affected area	MediaStream / Video Streaming
Feature category	Primary
Severity	SEV-2 → 1-high

Reasoning: This is an unhandled exception in the MediaStream component (UrlResolverService) affecting URL resolution and reachability checks for video streaming. Video Streaming is classified as a Primary feature. The crash impacts users attempting to resolve video URLs, but the platform remains partially functional for other users. This meets SEV-2 criteria: a Primary category feature broken for some users.

Labels applied: bug, 1-high, sdk, web-requests

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.

[github-actions]

This appears to be a duplicate of #8080, which tracks the same 'System.InvalidOperationException: Insecure connection not allowed' error occurring in the web request system.

Both issues stem from the same root cause related to HTTP vs HTTPS connections and how profile requests are being routed through peer-advertised lambdas URLs from local scene development sessions.

Please follow #8080 for updates on the fix.

Related duplicates: #10204, #10113, #8761, #8762, #7827, #3661