Browser Permissions for Direct License Activation

Modern browsers are tightening the way websites can communicate with locally installed applications and services. Starting with Google Chrome Release 147, users must explicitly allow this type of local connection. The same behavior also applies to other Chromium-based browsers, including Microsoft Edge and Brave.

For CodeMeter users, this setting is relevant when a license is activated directly from the browser into a local CmContainer. CodeMeter License Portal and WebDepot need to communicate with the locally installed CodeMeter Runtime to complete direct license activation into a CmDongle, CmActLicense, or CmCloud Container. If the browser blocks this connection, the activation process may switch to file-based license transfer, or an error may appear on the direct license transfer page.

The tutorials below show how to check and correct the required browser permission in Google Chrome, Microsoft Edge, and Brave. In each case, the essential step is the same: The browser must be allowed to access apps and services on the device, so that it can establish the required local connection with CodeMeter Runtime.

You will learn how to identify when the connection is blocked, where to find the relevant site setting, how to change it to Allowed, and what to check if the connection still cannot be established. This includes verifying that CodeMeter Runtime is running and making sure that antivirus or endpoint protection software is not preventing the local communication.

Choose the video for your browser below and follow the steps to restore direct license activation.

How to allow local connections for direct license activation in Google Chrome.

How to enable the required browser permission for direct license activation in Microsoft Edge.

How to allow access to apps on your device for direct license activation in Brave.