Chrome Extension Troubleshooting

Article author
Josh L
  • Updated

Roaming Client Chrome Extension Notice

For complete functionality, this Chrome extension must be deployed to managed G Suite users using Chromebooks. A managed G Suite domain and access to the Google Admin Dashboard is required. We intend to support additional deployment options in the near future.

This guide is for troubleshooting any issues associated with the Chrome extension Roaming Client.

Troubleshooting Steps

  1. Open the Extensions page by clicking the ellipsis More Tools > Extensions 
    Screenshot 2023-08-24 at 2.17.37 PM.png
  2. Enable Developer Mode by clicking the toggle in the top-right corner.   


  3. Next, click on** Background page **on the DNSFilter Chrome Extension card.
    Screenshot 2023-08-24 at 2.18.05 PM.png
  4. The Chrome debugger will open, select the Console tab and take a screenshot.f273e59-chrome_MQIjhfJTnj.png
  5. Attach the screenshot to an email to and include any relevant information.

[blank] Device name in the dashboard

There are a few reasons why your devices are named [blank] in the DNSFilter dashboard:

  1. The device is not provisioned.

  2. The hostname template is not set. This can be done by following Google’s guide:

Supported on Chrome version 65 and later

Allows you to specify the host name that is passed to the DHCP server with DHCP requests.

If this policy is set to a nonempty string, that string will be used as the device host name during the DHCP request.

The string can contain the ${ASSET_ID}, ${SERIAL_NUM}, and ${MAC_ADDR} variables. These variables will be replaced with values found on the device. The resulting substitution should be a valid host name per RFC 1035, section 3.1.

If this policy is not set or if the value after substitution is not a valid host name, no host name will be used in the DHCP request.

Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request



Article is closed for comments.