Skip to content
  • There are no suggestions because the search field is empty.

Chrome shows "no receivers for this room" error

Chrome now requires a permission called Local Network Access before a website can connect to devices on the same network as your computer. Ditto Connect for Web at connect.goditto.com connects straight from the browser to the Ditto receiver in the room, so it needs this permission. When the permission is missing or set to Block, Chrome refuses the connection and Ditto reports that it could not find a receiver.

What's happening

If Ditto Connect for Web accepts your room code and then shows "No receivers for this room were found on your network. Please contact your IT administrator.", Chrome is most likely blocking the browser from reaching the Ditto receiver on your local network.

Chrome now requires a permission called Local Network Access before a website can connect to devices on the same network as your computer. Ditto Connect for Web at connect.goditto.com connects straight from the browser to the Ditto receiver in the room, so it needs this permission. When the permission is missing or set to Block, Chrome refuses the connection and Ditto reports that it could not find a receiver.

Chrome introduced the permission in version 142 (October 2025) and extended it to the type of connection Ditto uses in version 147. Enforcement reached most Chromebooks with Chrome OS 152 in September 2026, which is when many schools first ran into it. Microsoft Edge and other Chromium-based browsers use the same permission.

The Ditto Connect apps for macOS, Windows, iOS and Android are not affected because they do not run inside a browser. The Ditto receiver and the room code lookup are not affected either.

Using managed Chrome device? Skip ahead →

Allow the permission when Chrome asks

Most of the time Chrome asks for the permission the first time you connect, and clicking Allow is all it takes.

  1. Go to connect.goditto.com, enter the room code and click Connect.
  2. Chrome shows a prompt near the address bar that reads "connect.goditto.com wants to access other devices on your local network".
  3. Click Allow.
  4. Ditto finds the receiver and continues to the connection screen.

Chrome remembers the answer for connect.goditto.com, so you will not be asked again on that computer unless you clear site data or change the setting.

If you have dismissed permission prompts on other sites before, Chrome may show a quieter version: a small icon in the address bar instead of a full prompt. Click that icon and choose Allow.

If Chrome did not ask, or you chose Block

Chrome will not ask again once a site has been blocked, and sometimes the prompt never appears at all. You can change the setting yourself in either of two places. Skip to the next section if your computer or Chromebook is managed by a school or company, because the setting may be locked.

From the Ditto page

  1. On connect.goditto.com, click the icon at the left end of the address bar (the site information icon).
  2. Find the local network permission in the list. Until you change it, it reads "Can ask to access other devices on your local network". If it is not shown, click Site settings to open the full list.
  3. Set it to Allow.
  4. Reload the page, enter the room code and connect again.

From Chrome settings

  1. Paste chrome://settings/content/localNetwork into the address bar and press Enter. Older Chrome builds used chrome://settings/content/localNetworkAccess; if one address shows nothing, try the other.
  2. Check the default at the top. It should read "Sites can ask to access other devices on your local network". If it is set to "Don't allow sites to access other devices on your local network", change it back.
  3. Look under "Not allowed to access other devices on your local network". If connect.goditto.com is there, remove it or change it to Allow.
  4. To skip the prompt entirely, click Add next to "Allowed to access other devices on your local network" and enter https://connect.goditto.com.
  5. Reload the Ditto page and connect again.

Managed Chromebooks and managed Chrome

On Chromebooks and Chrome browsers managed by a school or company, the permission prompt usually never appears, and users cannot change the setting themselves. Site permissions on managed devices come from policy, so a Chrome administrator needs to allow connect.goditto.com for everyone. This is a one-time change that covers every user and device in the organizational unit.

Google Admin console (Chromebooks and enrolled Chrome browsers)

  1. Sign in at admin.google.com.
  2. Open the menu and go to Devices, then Chrome, then Settings, then Users & browsers.
  3. Select the organizational unit that contains your staff and student accounts. Selecting the top-level organization applies the change to everyone.
  4. In the search box at the top of the settings page, type "Local network".
  5. In the setting that allows local network access on specific sites, add https://connect.goditto.com, and if you're using a custom URL, enter the custom URL too.
  6. Click Save.

While you are there, make sure connect.goditto.com does not also appear in the blocked list for the same organizational unit. A blocked entry wins over an allowed one.

Devices apply the change at their next policy refresh, which normally happens within minutes. Signing out and back in, or restarting the Chromebook, applies it right away. To confirm on a device, open chrome://policy and look for LocalNetworkAllowedForUrls (Chrome 146 and newer) or LocalNetworkAccessAllowedForUrls (Chrome 139 and newer) with https://connect.goditto.com and your custom URL as its value. Chrome honors both, and the newer name takes precedence when both are set.

Managed Chrome on Windows and macOS

The policy is LocalNetworkAllowedForUrls on Chrome 146 and newer, or LocalNetworkAccessAllowedForUrls on older builds. Set it through whichever tool manages your browsers: Chrome Browser Cloud Management uses the same Admin console page as above, Group Policy has it under Google Chrome, then Content settings, and Mac device management tools set it in a managed preferences profile for com.google.Chrome. The value is a list with at least one entry, https://connect.goditto.com. Also add your custom connect page URL if you're using one.

Two things not to do

  • Do not add connectstream.link addresses to the policy. The permission belongs to the site making the request, which is connect.goditto.com. The connectstream.link names are the addresses Ditto connects to, and they do not go in this list.
  • Do not rely on the LocalNetworkAccessRestrictionsTemporaryOptOut policy. Google describes it as temporary and plans to remove it in a future Chrome release. The allow list above is the permanent fix.

Still seeing the error?

If the permission is allowed and Ditto still cannot find the receiver, the browser is being stopped somewhere else on the path to the receiver.

  1. Confirm the permission took effect. On a personal device, chrome://settings/content/localNetwork should list connect.goditto.com as allowed. On a managed device, chrome://policy should show LocalNetworkAllowedForUrls or LocalNetworkAccessAllowedForUrls with the Ditto address.
  2. Check the network requirements in Configuring your network for Ditto. Ditto Connect for Web reaches the receiver through an address ending in connectstream.link, which points at the receiver on your local network, over TCP port 55202. A content filter or DNS setting that blocks connectstream.link produces the same "no receivers" message.
  3. Make sure the computer and the receiver are on the same network, or on networks that are allowed to talk to each other. A guest Wi-Fi network is a common culprit.
  4. Try the Ditto Connect app on the same computer. If the app connects and the browser does not, the problem is in the browser and this article applies.

If none of that resolves it, contact Ditto support with the Chrome version from chrome://version, whether the device is managed and a console log from a failed attempt. To capture the log: right-click the Ditto page, choose Inspect, open the Console tab, set the log level to Verbose, try to connect, then right-click in the console and choose Save as.

Background

Google added Local Network Access to stop websites from silently probing printers, routers and other devices on private networks. Screen mirroring from a browser is one of the legitimate uses the permission is designed to cover, which is why Chrome offers an allow prompt rather than a flat block.