Troubleshooting

Use this guide to resolve the most common issues with the Robost browser extension. Work through the relevant symptom below before opening a support ticket.

Extension installed but not showing alerts

Cause: The device is not enrolled. The extension will not submit alerts until it holds valid credentials.

Fix:

1. Click the puzzle icon in the Chrome toolbar and open the Robost options page.
2. Check the Status section — if Enrolled shows No, the extension has no credentials.
3. For MDM-deployed devices, verify the managed config policy is correctly applied (see below).
4. For manually installed devices, enter the Server URL and enrollment token on the options page and click Save & enroll, then reload the extension from chrome://extensions.

”Not enrolled” state after MDM deployment

Cause: The managed configuration JSON pushed by your MDM uses incorrect key names or the policy has not propagated to the device.

Fix:

1. Open chrome://policy on the affected device and click Reload policies.
2. Find the ExtensionSettings entry for extension ID gefljjkloapnkdffchpnakeplfmfiggh and inspect the managed_configuration block.
3. Confirm the keys are exactly api_base_url and enrollment_token (snake_case, no camelCase variants). Any deviation — for example apiBaseUrl or enrollmentToken — will cause the extension to fall through to the unenrolled state.
4. Correct the policy JSON in your MDM console and wait for propagation (10–30 minutes depending on the MDM), or trigger a manual sync on the device.

Extension auto-disabled by Chrome

Cause: A Chrome enterprise policy is blocking third-party extensions that are not explicitly allow-listed.

Fix:

1. Open chrome://policy and look for ExtensionInstallBlocklist or ExtensionAllowedTypes.
2. If a blanket block is in place, add the extension ID gefljjkloapnkdffchpnakeplfmfiggh to the ExtensionInstallAllowlist policy, or use ExtensionInstallForcelist (which implicitly allow-lists the extension).
3. Re-apply the policy and confirm the extension is listed as Installed by your administrator in chrome://extensions.

Options page won’t open

Cause: The MV3 background service worker is in a cold-start state. The browser may show a blank page or fail to open the options page if the service worker has not yet initialized.

Fix:

1. Navigate directly to chrome://extensions.
2. Find Robost in the list and click Details, then click Extension options from the detail page. This wakes the service worker before opening the page.
3. If the options page still fails to open, click the circular refresh icon on the extension card to reload the service worker, then try again.

Alerts not delivered to the dashboard

Cause: The device cannot reach the Robost API. The extension queues alerts locally and retries every five minutes, so a connectivity block will silently stall delivery.

Fix:

1. On the affected device, confirm that api.robostai.com (or your self-hosted server URL) is reachable: open a browser tab and navigate to the server URL — you should get a valid response rather than a connection error.
2. If the server is unreachable, check whether a firewall rule, proxy, or network policy is blocking outbound HTTPS to the Robost API host.
3. For self-hosted deployments, verify that the api_base_url value in your MDM policy matches the actual server URL exactly, including the scheme (https://) and without a trailing slash.
4. Once connectivity is restored, queued alerts will flush automatically within five minutes. You can also reload the extension to trigger an immediate flush attempt.