Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 12-30-2025 10:58
    No replies, thread closed.

    Hi Everyone,

    Sorry if this has already been solved elsewhere, we use Edge in my company and didn't catch wind of this until this month! 😅

    If GCBA screen recording suddenly stopped working around early December 2025, you're not alone. Microsoft Edge 143 introduced new Local Network Access (LNA) security restrictions that block GCBA's loopback communication. This wasn't announced by Microsoft or Genesys ahead of time.

    Edge 143 now requires user permission for websites to connect to localhost applications like GCBA. When users dismiss or block this prompt, screen recordings stop working, and the prompt doesn't reappear.

    The Solution

    Deploy registry keys to bypass the LNA permission prompt. This prevents users from accidentally blocking GCBA.

    Registry Keys (use wildcards to cover all regions):

    For Microsoft Edge:

    Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\LocalNetworkAccessAllowedForUrls
Value Name: 1
Value Type: REG_SZ
Value Data: https://*.pure.cloud/*

Value Name: 2
Value Type: REG_SZ
Value Data: https://*.mypurecloud.com/*

    For Google Chrome (if applicable):

    Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\LocalNetworkAccessAllowedForUrls
Value Name: 1
Value Type: REG_SZ
Value Data: https://*.pure.cloud/*

Value Name: 2
Value Type: REG_SZ
Value Data: https://*.mypurecloud.com/*

    Note: Using wildcard patterns (.pure.cloud/ and .mypurecloud.com/) covers all Genesys regions automatically, making this future-proof and easier to maintain.

    PowerShell Deployment Script:

    $EdgeRegPath = "HKLM:\SOFTWARE\Policies\Microsoft\Edge\LocalNetworkAccessAllowedForUrls"
$GenesysUrl1 = "https://*.pure.cloud/*"
$GenesysUrl2 = "https://*.mypurecloud.com/*"

if (-not (Test-Path $EdgeRegPath)) {
    New-Item -Path $EdgeRegPath -Force | Out-Null
}
Set-ItemProperty -Path $EdgeRegPath -Name "1" -Value $GenesysUrl1 -Type String
Set-ItemProperty -Path $EdgeRegPath -Name "2" -Value $GenesysUrl2 -Type String

    Manual Fix for Individual Users:

    Edge: Go to edge://settings/content/localNetworkAccess → Find Genesys URL in "Not allowed" → Click three dots → Select "Allow"

    Chrome: Go to chrome://settings/content/localNetworkAccess → Same steps as Edge

    Hope this helps!


    #Omni-ChannelDesktop/UserInterface

    ------------------------------
    Chris Rodriguez
    Contact Center System Administrator
    ------------------------------


  • 2.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 12-30-2025 16:37
    No replies, thread closed.

    Thanks for sharing this! I was just working with one of our agents on this - Screen recording worked when using Chrome but not while using Edge. Updating the GCBA app didnt help. I will give this a shot



    ------------------------------
    Prasanna Shrestha
    ------------------------------



  • 3.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 01-02-2026 14:27
    No replies, thread closed.

    Hello Chris,

    Thank you for that info. This should help anyone else who is experiencing issues using Microsoft Edge.



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 4.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)
    Best Answer

    Posted 01-05-2026 11:50
    No replies, thread closed.

    Thanks for sharing, Chris. Just to tie this to a couple of related threads in the Community:

    • https://community.genesys.com/discussion/screen-recording-with-genesys-cloud-through-a-web-browser-action-needed-for-upcoming-browser-updates
    • https://community.genesys.com/discussion/action-needed-to-resolve-private-and-public-embeddable-framework-screen-recording-via-gcba



    ------------------------------
    Director, Product Management – Recording and Real-time Supervision
    Workforce Engagement Management (WEM)
    ------------------------------



  • 5.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 01-07-2026 09:13
    Edited by Keith Simmonds 01-07-2026 10:07
    No replies, thread closed.

    Brilliant this has been troubling us for days, logged a call with Genesys but they just said it wasn't them it was our network...

    One observation is the edge link for the manual check / fix is different for us.

    edge://settings/privacy/sitePermissions/allPermissions/localNetworkAccess

    Will test and confirm with effected users and report back.

    Update 
    Tested with 2 agents manually with positive results. Thank you once again.

    Passing to our Deployment team to push out to Registry for all 



    ------------------------------
    Keith Simmonds
    Telecommunications, Audio Visual Specialist
    ------------------------------



  • 6.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 01-08-2026 10:09
    No replies, thread closed.

    @Chris Rodriguez - Thank you for your detailed reply.

    In my experience, these changes only resolve the issue for Genesys UI users. We have a group of users who are using the Genesys Embeddable Framework / Connector for MSFT Dynamics that haven't had screen recordings since October. After several weeks of finger pointing, we finally got Genesys engaged and they added the required explicit permissions to the connector iframe. However, they just "discovered" that the parent MSFT iframe may also need the explicit permissions added. Currently, both Genesys (and our company) have cases open w/ MSFT on this issue.

    Is there anyone out there that has a solution for user that are NOT using the Genesys UI for making / taking calls?


    Thanks!
    Mike



    ------------------------------
    Michael Rigney
    Sr. Contact Center Engineer
    ------------------------------



  • 7.  RE: Edge 143 Breaking GCBA Screen Recording? Here's the Fix (Local Network Access Registry Keys)

    Posted 01-08-2026 18:26
    No replies, thread closed.

    Hi Mike,

    This issue is related to recent browser security changes affecting GCBA screen recording in embedded frameworks. Genesys published an article that covers this behavior and the required iframe permissions:

    https://community.genesys.com/discussion/action-needed-to-resolve-private-and-public-embeddable-framework-screen-recording-via-gcba

    In iframe-in-iframe scenarios (like MSFT Dynamics), the documentation highlights that the required permissions must be properly propagated, otherwise screen recording may not start even if the Genesys iframe is updated.

    This might help support the ongoing investigation with both Genesys and Microsoft.



Related Content