NetLock RMMNetLock RMM Docs
V — Appendix

Troubleshooting

Symptom-cause-fix entries for the most common failure modes across the agent, policy pipeline, notifications, sign-in and SSO, remote control, and content surfaces.

Troubleshooting

This appendix lists common failure modes with a short cause and fix for each. It is organised by area rather than by error code; start with the area your symptom belongs to.

Most entries below assume a working baseline: you can sign in to the Console, the server process is running, and the database is reachable. When any of those is in doubt, check the Logging page first (see A.9); most deeper problems show up there before they show up in the UI.

X.3.1 Agents and devices

The agent never appears in the Console after installation

Symptom. You installed the agent on a device, the installer reported success, but the device is not in the Devices list.

Likely cause. The agent is waiting in the Unauthorized queue. Unapproved devices do not appear in the main inventory.

Fix. Open Devices → Unauthorized Devices at /unauthorized_devices. Confirm the hostname, operating system, and the target tenant / location / group. Approve the entry. If the device is not in the Unauthorized queue either, see the next entry.

The agent does not show up even as unauthorized

Symptom. Installation completed but the device never reaches the Console: there is no entry in Devices and none in Unauthorized Devices.

Likely cause. The agent cannot reach the server. The three common reasons are a wrong server URL in the installer configuration, a network or firewall block between the device and the server, and TLS validation failure against the server certificate.

Fix. On the device, confirm the agent service is running (NetLock_RMM_Agent_Comm on Windows; the netlock-rmm-agent-comm systemd unit on Linux). From the device, verify TCP reachability to the server URL and port. A device whose only route to the internet is a forward proxy has no direct TCP route, so a failing test there does not mean the device is misconfigured; see the next entry.

Switch server logging on at /logging, then download the server logs there and look for rejected connection attempts. The source IP on the rejection is the device's apparent source IP, which helps when a NAT or reverse proxy is in the path. For a detailed on-device view, enable debug logging on the agent and collect its log files, as described in Debug an agent.

The device is behind an HTTP proxy and never comes online

Symptom. The device has no direct route to the internet and reaches everything through a forward proxy. The installer aborts at the connectivity check, or the installation succeeded but the device stays offline: the Comm agent works in offline mode, the Remote agent never connects to the command hub, and remote control, remote shell and tunnels are unavailable.

Likely cause. The agents determine the server address they talk to from a reachability check. Without a proxy configuration that check has no route to take, so the address stays empty and nothing downstream can connect. Proxy settings from the environment do not help by themselves: the three services run as LocalSystem on Windows and therefore see no per-user internet settings, and on Linux a systemd system unit inherits neither /etc/environment nor a login shell.

Fix. Install the agent with the proxy parameters of the Standard Installer, or with a proxy object inside the server_config.json you hand to clean; both are described in Devices behind an HTTP proxy. On Windows the machine-wide WinHTTP proxy written by netsh winhttp set proxy is picked up automatically as a fallback when no direct connection works, and on Linux the same is true for HTTPS_PROXY / HTTP_PROXY / NETLOCK_PROXY placed in /etc/default/netlock-rmm.

An authenticating proxy that answers with 407 is called out separately by the installer. It means the network path is fine and only the credentials were refused. Check --proxy-user / --proxy-pass, or use --proxy-auth default on a domain-joined machine.

A device behind a proxy that runs an agent before 3.3.0.3 cannot update itself; install the agent once again with a current installer.

Once the device is online, patch downloads are a separate matter: Patch Management drives the Windows Update Agent, which takes its proxy from the machine-wide WinHTTP configuration or from a WSUS and not from the NetLock proxy setting. A device that reports patches but never downloads them needs netsh winhttp set proxy or a WSUS as well; see What the proxy setting does not cover.

A device turns up under Unauthorized Devices although nobody deauthorized it

Symptom. A device that was authorized and working appears in Devices → Unauthorized Devices again, sometimes repeatedly, and the audit log holds no matching deauthorize entry.

Likely cause. The server deauthorizes a device on its own in two cases: a reinstall of the agent was detected (the device then waits for approval again, reason "Reinstall detected"), or the license limit was exceeded and the newest devices were deauthorized.

A changed hardware ID does not take the authorization away: the server stores the new ID and the device stays authorized; the authentication log shows "Hardware ID changed: new ID stored, device stays authorized", and a server sensor of the kind "Unauthorized device" with that trigger selected writes an event.

A device that appears as a second, unauthorized entry next to an authorized one of the same name was reinstalled (new operating system, new access key, new hardware ID); the entry carries the chip "Name already exists" and is continued with the row action "Adopt as reinstall" rather than approved as a duplicate.

Fix. Use the Authentication log row action on the device's row in Unauthorized Devices (permission "Authentication log"). The rows name the reason, the endpoint, the remote address and both hardware IDs, so the case is visible at a glance; the reasons and what to do about each are listed in Debug an agent, and what the hardware ID is and when it changes is described in Hardware ID. Re-authorize the device, or adopt the new entry as a reinstall of the existing device.

A device reports Offline despite the agent running

Symptom. The device shows Offline in the Console, but the agent service is running on-device.

Likely cause. The sync interval on the device's policy is longer than you expected, the agent is running but unable to reach the server (intermittent network), or the agent service stopped. A device that shows a red Blocked until … chip next to its name is refused by rate limiting on the server; see the next entry.

Fix. Check the Agent tab on the device's assigned policy for the configured sync interval (valid values are 5 to 1440 minutes). A shorter interval shows an offline device sooner and causes more check-ins. Restart the agent service on the device; when the agent comes back up it emits a fresh check-in that moves the Console to Online. If the problem recurs, look at the agent logs on the device and at the server logs (download them from the /logging page) for the device's identifier around the transition window.

A device appears offline or the agent logs 429 — it is blocked by rate limiting

Symptom. A device goes Offline although the agent is running and the network is fine. The devices list shows a red chip Blocked until <time> next to its name, the agent log on the device shows answers with status 429 and the body blocked or rate_limited, and /events has an event of the type Rate limiting for the device.

Likely cause. The device exceeded one of the request limits of rate limiting for several minutes in a row and rate limiting is in Enforce mode. Typical triggers are a reinstall or restart loop of the agent, a script or sensor that produces events at a high rate, a collector that outgrew the daily data volume, or a second agent that shares the device's identity. In Observe mode nothing is refused; a Blocked until chip only appears for enforced blocks.

Fix. Open Settings → Security → Rate limiting. The Blocks table names the class, the reason and the measured rate of the block, and the event of the type Rate limiting on /events carries the same details; Top subjects (24 h) shows whether the device is still over a limit. Unblock releases the block; the server applies it within thirty seconds and does not block the device again for fifteen minutes. A device block ends by itself after at most 60 minutes.

Then remove the cause on the device; the agent logs show which endpoint was refused. When the traffic is legitimate (a large SNMP collector, for example), raise the daily volume, choose the sensitivity Relaxed or add the device to the Exemptions.

If many devices behind one site are affected and the Rate limiting tab warns that most devices share one private address, the reverse proxy in front of the server does not pass the client addresses on; fix Kestrel:ForwardedHeaders before you keep the protection in Enforce mode.

Download from a device fails: the agent must be updated

Symptom. Download in the file browser of a device, or the public API action POST /v1/devices/{id}/files/actions/collect, fails. The file browser shows The agent on this device needs to be updated before files can be downloaded from it.; uploads to the device work.

Likely cause. The agent on the device is older than 3.3.0.6. Its upload is refused with 403 and nothing is stored. Devices whose policy has the automatic agent update turned off keep the old agent until they are updated by hand.

Fix. Update the agent on the device (through the automatic agent update or by installing the current agent package) and repeat the download.

A device shows no policy

Symptom. The device detail view shows - in the policy field.

Likely cause. No automation's condition matches the device and no default policy is set, so no policy has been selected for it. Policies do not attach to devices, locations, or groups directly; they are routed through Automations, with the default policy as the only fallback.

Fix. Open Automations and review the list for an enabled rule whose conditions all hold for this device (device, tenant, location, group, internal IP, domain, platform or a device attribute); Check matching devices in the rule's dialog shows whether it matches. Create a new automation if none exists.

Among the matching rules, the one with the lower priority number wins. If the wrong automation is winning, raise its number, narrow it, or give the rule you want a smaller number (a Device rule for the single machine gets 100 by default). Automation changes force an immediate re-evaluation on the affected devices. See Chapter 5 — Automations.

Alternatively, mark a default policy on the Policies page (Set as default policy in the actions column); it applies to every device that no automation reaches (see Chapter 6.2).

A policy edit has not taken effect on a device

Symptom. You edited a policy, saved, and the device has not picked up the change.

Likely cause. The device has not synced since you saved. Policy changes apply on the agent's next sync cycle.

Fix. If the delay is unacceptable, use the Force Sync action on the device detail page (requires devices_force_sync). Check the Events page for the policy deployment record of the device.

X.3.2 Notifications

Email notifications never arrive

Symptom. Events that should trigger an email produce none; nothing arrives in the recipient's inbox.

Likely cause. The global SMTP configuration has not been saved with a passing test, a maintenance window is suppressing sends, or the recipient's severity threshold is filtering the events out.

Fix. Open Notifications → E mail → SMTP settings and re-run Test. The dialog's Confirm action is gated behind a passing test. Until the test passes, no email notification is sent. Check the recipient's Severity dropdown: Any delivers every event, every other value delivers only events of exactly that severity (see A.8). Confirm no maintenance window is currently suppressing notifications. See A.8.2.

Microsoft Teams or ntfy.sh notifications do not arrive

Symptom. The Teams channel receives nothing, or the ntfy.sh topic shows no messages.

Likely cause. The webhook URL or topic URL is wrong, the workflow behind a Teams webhook is turned off or fails on the body it receives, or the recipient's tenant scope does not include the tenant the event belongs to.

Fix. Open the channel tab and run Test on the suspect recipient. For Teams, check that the URL still belongs to a live workflow. A URL on webhook.office.com is a classic Office 365 connector, which Microsoft retired in May 2026; create the workflow as described in H.10 and paste the new URL over the old one.

A Teams test that passes while the channel stays empty points at the workflow rather than at the connector: its run history names the failing step, and a post step that cannot read the body it was handed means Payload format does not match how the flow is built.

For ntfy.sh, verify the topic URL is still current on the receiving side. Check that the recipient's Tenants / Selected tenants scope includes the relevant tenant: an empty Selected tenants list means "all tenants", but a single selected tenant excludes events from others. See A.8.

X.3.3 Sign-in and SSO

You forgot your password or no admin can sign in

Symptom. Sign-in fails with Incorrect user name or password., and no other account that can manage users is able to reset your password.

Likely cause. The password is wrong or forgotten. The same message also appears when the account is set to SSO-only or is suspended, so the login screen does not show which of these applies.

Fix. If another account with users_edit can sign in, reset the password from Users (see Chapter 14). Otherwise, on a self-hosted deployment, set a temporary password in the database and change it at the next sign-in. See Recover access to the Web Console. On cloud, contact NetLock RMM support.

SSO sign-in fails with "User is not authorized"

Symptom. A user completes the identity provider's sign-in flow but the Console rejects them with an authorization error.

Likely cause. The user has not been pre-provisioned in Users, their Auth Mode does not include SSO, or the email the identity provider returns does not match the username on the NetLock account.

Fix. NetLock RMM does not auto-provision accounts on first SSO sign-in. Open Users, create the account, set Auth Mode to SSO or Password & SSO, and make sure the Name field matches the email claim your provider returns exactly. Save. Ask the user to try again. See A.4.2.

Saving the SSO configuration restarts the Console

Symptom. You toggled SSO settings and saved, and the Console restarted and signed out every user.

Likely cause. SSO configuration changes restart the Web Console so that the new identity configuration is loaded.

Fix. No fix needed. Plan SSO changes during a maintenance window if signing out all users is a problem, and confirm you can still sign in via the old method from a separate browser before you make the change, so you are not locked out if the configuration is wrong. See A.4.2.

SSO button missing on the login page

Symptom. The SSO tile does not appear on the sign-in page even though you configured a provider.

Likely cause. No provider is currently enabled, or the saved configuration failed to load at startup. The SSO tile does not depend on the licence plan; SSO is available on every deployment.

Fix. Re-open Settings → SSO, confirm exactly one provider tab has its Enable switch on, and save. Only one provider can be active at a time; switching one on turns the others off. If the page shows the red SSO Configuration Error! banner, the stored configuration could not be loaded at startup; correct the provider fields and save again.

SSO sign-in fails with Invalid parameter: redirect_uri in the log

Symptom. Clicking the SSO button returns to the login page with the SSO error message, and the Web Console log contains Message contains error: 'invalid_request', error_description: 'Invalid parameter: redirect_uri'.

Likely cause. Keycloak rejected the redirect URI the Console sent. It checks the URI when the Console pushes the authorization request to it, before the browser is redirected, and uses the same message for any mismatch in scheme, host, port or path. Either the client's Valid redirect URIs do not match the Console's public address and callback path, or the Console builds the URI from the internal scheme or host because the reverse proxy is not trusted.

Fix. Open Settings → SSO; the Keycloak tab shows the sign-in and post-logout redirect URI to register. Compare them with the log line SSO | Keycloak challenge, which names the URI that was actually sent, and with the client's Valid redirect URIs, then register the exact value. If the log line shows forwarded_headers_applied=False, add the reverse proxy address to Kestrel:KnownProxies in the Console's appsettings.json, or enable Force https in redirect URLs and save. See A.4.2.

X.3.4 Remote control

Relay session stuck in Device offline state

Symptom. A relay session you initiated stays in an offline state indefinitely.

Likely cause. The device is offline, or the Remote agent on the device is not running.

Fix. Confirm the device status on the Devices page first. If the device is online, the Remote agent may be stopped or stuck; trigger a Force Sync on the device to reset its side of the relay connection. Check the Relay Server page for the session's state and for errors. See Chapter 9.2.

Remote Control disconnects on a device behind a strict corporate network

Symptom. The remote control session connects, runs for a minute, and drops, again and again.

Likely cause. A middlebox (firewall, proxy, or deep-packet-inspection appliance) is terminating long-lived WebSocket connections or the relay stream.

Fix. Verify the device and the viewer can maintain persistent outbound connections to the server. Review the middlebox's session-timeout policy for WebSocket traffic. After a short loss the viewers reconnect on their own (A.7.9); a session that keeps dropping points to the middlebox.

The Remote agent logs INADEQUATE_SECURITY in Service.Setup_SignalR

Symptom. Remote control, screen sessions and tunnels are unavailable on a device, but the device shows as online in the Console and syncs normally. The Remote agent's Logs\Error.txt (see Debug an agent) contains entries from Service.Setup_SignalR with Failed to start SignalR and a message containing HTTP/2 error code 'INADEQUATE_SECURITY'.

Likely cause. The device runs Windows 8.1, Windows Server 2012 R2 or older, and the server is reached through a reverse proxy that enforces the HTTP/2 cipher-suite rules, such as Traefik in the setup from the Docker install guide, Caddy, or Apache with mod_http2. These Windows releases have no cipher suite that such a proxy accepts for HTTP/2, so the proxy refuses the HTTP/2 connection the Remote agent opened for its SignalR connection setup. The Comm agent uses plain HTTP/1.1 requests and is not affected, so the device still reports online.

Fix. Update the agent. Current agents use HTTP/1.1 for the SignalR connection setup and are not affected.

Symptom. A link or a service of a service network stays in the status Port not available on the NetMesh page. The link details show the operating system's message and, from agent 3.3.0.11, a hint with the reason.

Likely cause. The agent on the client device cannot open the local port of the link. Usually another program or service on the client device already listens on that port. On Windows the port can also be in an excluded port range (reserved by Hyper-V, WinNAT or Docker), and Windows' own file sharing always holds 445 and 139. A jump host does not help here: it only changes where the service device connects to.

Fix. Choose a different local port. With the netmesh_edit permission, the hint offers Change local port; for a service network the port applies to all consumers of the service. Afterwards the application on the client device must connect to the new port. On Windows, list the reserved ranges with netsh int ipv4 show excludedportrange protocol=tcp. For file shares (SMB, port 445) see Reach a file share (SMB) over NetMesh.

X.3.5 Collections

A custom field value does not populate on the device detail page

Symptom. A custom field renders but its value is blank or stale.

Likely cause. The Job that feeds the field failed on the device, or the Job has not run since the field was created.

Fix. Identify the Job feeding the field on Manage Custom Fields. Review its last execution on the device. If the Job is marked Hidden, its outcomes do not appear on the Events page. Run it manually from the device detail page's Job list or from the Jobs management page to see the failure. Fix the Job's Script or parse regex, then let it run again. See Chapter 8.4.

Application Control is not blocking an application I expected it to

Symptom. A user launched an application that is not whitelisted in any attached ruleset, and Application Control did not stop the launch.

Likely cause. The ruleset is not attached to the device's policy, the policy has not synced since the ruleset was attached, or Application Control itself is disabled on the policy.

Fix. Open Policy Settings → Windows → Application Control on the device's policy. Confirm the ruleset is attached and the master switch is on. Force-sync the device. If Application Control is attached and synced, check the Blocked Applications tab on the ruleset for the launch attempt. If the attempt is not recorded there either, the agent is not enforcing yet. Enforcement starts once the ruleset holds rules and the auto-whitelist period of the policy has ended.

App Hub browse shows no apps for a catalogue

Symptom. The Winget, Flathub, or Chocolatey browser is empty.

Likely cause. The catalogue has not been refreshed yet on this deployment, or the server cannot reach the upstream service.

Fix. Click Refresh catalogs on the App Hub page. The refresh runs server-side and pulls the catalogue to the local database. Check the server logs (download them from /logging) for network failures against the upstream catalogue. See Chapter 8.5.

X.3.6 Ticket System

Inbound emails are not creating tickets

Symptom. Customers reply to a department mailbox but no new tickets or replies appear.

Likely cause. The department's IMAP credentials are wrong, the mailbox is unreachable, or the Ticket System is disabled globally.

Fix. Open Tickets → Departments: the Last poll column shows whether the latest poll of each department failed, and hovering over it names the cause. Open the department, review its mailbox configuration and click Test connection. Check that Settings → Ticket System → General → Ticket System Enabled is on. Confirm the mailbox is reachable from the server. Note that Blocked File Extensions strips attachments during ingestion; it does not prevent the ticket from being created. If attachments are being stripped but the ticket still does not appear, the issue is not the blocklist. NetLock RMM's own notification mails in that mailbox are skipped and stay unread; they do not indicate a broken intake.

The connection test reports that the revocation status of the certificate could not be checked

Symptom. Test connection of a department, or a test in the global e-mail settings, succeeds with a warning that names the mail server and a second host from which the revocation list could not be retrieved. The web console log (for notification mails sent by the server: the server log) contains a warning The revocation status of the certificate of <server> could not be checked.

Likely cause. With Full validation (recommended) or Encrypt, but ignore a host name mismatch, NetLock RMM checks whether the certification authority has revoked the mail server's certificate. The revocation list is downloaded over plain HTTP (port 80) from the host named in the certificate. The machine or container running NetLock RMM cannot reach that host: outbound port 80 is blocked, the host name cannot be resolved, or the network only allows outbound traffic through a proxy.

Fix. Mail is still fetched and sent; only the revocation check is skipped, and the warning is repeated at most once per server and hour. To have the revocation checked, allow outbound HTTP (port 80) from NetLock RMM to the host named in the message. On a Docker installation, test from the network of the containers, for example sudo docker run --rm --network <network> curlimages/curl -sI http://<host>/. Switching to Encrypt, accept any certificate is not needed for this warning and turns off every certificate check. A certificate the authority has revoked is always refused, whatever the network allows.

Department notification mails do not arrive

Symptom. The recipients listed under the department's Notifications get nothing although the event is ticked.

Likely cause. The ticket has no department (the console's New Ticket dialog defaults to None; the API's departmentId was left out), the global e-mail settings under Settings → Notifications → E-Mail were never saved with a passing test (the department's own SMTP is not used for these mails), the event is not ticked, or the recipient list is empty or invalid.

Fix. Check the ticket's Department on the Details tab. Run the global SMTP test. Re-tick the events and save. Download the Console logs from /logging and search error.log / debug.log for Tickets.NotificationMailDispatcher (for events raised through the public API: the server logs, Public_Api.Ticket_Notification_Mail_Dispatcher); every skipped or failed send writes one line naming the reason. A notification that lands in the polled mailbox stays unread and is not imported. See Chapter 10.10.

Ticket list refreshes too slowly

Symptom. New replies arrive by email but the list lags behind.

Likely cause. The background refresh runs every 60 seconds. The real-time toasts are an additional notice and do not replace the refresh.

Fix. Click Refresh on the page, or reload the page. If toasts are not arriving either, the Console's persistent connection has dropped; reload to re-establish it. See Chapter 10.3.

X.3.7 Dashboards, Reports, and content surfaces

A dashboard panel shows no data

Symptom. The panel renders but the value area is empty or shows zero.

Likely cause. The panel's SQL query returns no rows, or the MySQL user for SQL access cannot read a table or column the query uses.

Fix. Open the panel in the Panel Builder and check the underlying query; the query builder lists only the tables and columns the SQL access user can read. Widen that user's SELECT grants in MySQL if the panel needs another table. See Chapter 2.

Widgets, panels or custom fields show "SQL access not configured"

Symptom. Report widgets with custom SQL show SQL access not configured (in generated output [SQL access not configured]), dashboard SQL panels are locked with a notice, SQL custom fields show (SQL access not configured), and the Widget Editor, Panel Builder and Custom Field Builder show a notice instead of the query builder and the SQL field. Saving a report template with custom SQL is refused; the public API answers 403 sql_access_not_configured.

Likely cause. No MySQL user is configured under Settings → SQL access, or the configured user was refused. Built-in report templates and SQL panels added from the shipped panel templates keep working, because their unchanged statements run without SQL access. On cloud instances SQL access is not available.

Fix. Open Settings → SQL access and read the status line. If it says Not configured, create the user and enter it as described in Set up SQL access. If it says Off with a reason, fix the grants as listed under Refusal reasons and save again. SQL access also switches off by itself when the periodic check (every 15 minutes) finds wider grants; it returns within a minute after the grants are fixed.

A duplicated built-in report stops working after an update

Symptom. A copy of a built-in template showed data before the update; afterwards some widgets show SQL access not configured.

Likely cause. The release changed the built-in statement. The copy still carries the old statement, which no longer matches the shipped one and is therefore treated as custom SQL.

Fix. Configure SQL access, or duplicate the current built-in template again.

A report generation fails with a SQL error

Symptom. Generating a report returns an error mentioning an unknown table or column, or an access-denied error.

Likely cause. The SQL access user cannot read the table or column (for example a table added by an update after the per-table grants were created, or a credential column left out by the generated grants), or the schema changed between releases.

Fix. Run the GRANT statements from Settings → SQL access again after an update. If the schema changed, edit the template and rewrite the query against the current columns. On save, the console checks the statement with EXPLAIN and shows MySQL's message.

AI answers are not grounded in the documentation

Symptom. AI Chat answers questions about NetLock RMM from general knowledge (menu paths or setting names that do not exist in the product), and no Sources line appears under the answer. Or the answer says the documentation does not cover a question that the manual clearly does.

Likely cause. There are three possible causes. The Use the product documentation to answer questions about NetLock RMM toggle on Settings → AI/LLM is off. The installation was built without the documentation snapshot; the status line under Product documentation on the same page then reports that no snapshot was found. Or a model with a short context window (a local Ollama or LM Studio model at its default context length) received more prompt than it can hold and truncated it from the start, which drops the instructions and the documentation sections before the question arrives.

Fix. Turn the toggle on and save. If the status line reports a missing snapshot, pull the current web console image; the published images carry the documentation. For a small local model, lower Documentation excerpt budget (characters) to 2000 or 3000, or raise the model's context window (for Ollama OLLAMA_CONTEXT_LENGTH or num_ctx in a Modelfile) and keep Max Tokens well below it. See A.11.5.

X.3.8 When the answer is "look at the logs"

Two Console pages cover most deeper diagnostics.

  • Logging at /logging: switch logging on or off for the Console and the server without a restart, and download the log files of both as ZIP packages. Self-hosted only. See A.9.
  • Audit at /audit: the record of configuration changes, including who changed what, from which IP, and when. When something used to work and now does not, the Audit log usually names the change that broke it. See Chapter 12.

Together they answer most "what changed and when" questions.

On this page

TroubleshootingX.3.1 Agents and devicesThe agent never appears in the Console after installationThe agent does not show up even as unauthorizedThe device is behind an HTTP proxy and never comes onlineA device turns up under Unauthorized Devices although nobody deauthorized itA device reports Offline despite the agent runningA device appears offline or the agent logs 429 — it is blocked by rate limitingDownload from a device fails: the agent must be updatedA device shows no policyA policy edit has not taken effect on a deviceX.3.2 NotificationsEmail notifications never arriveMicrosoft Teams or ntfy.sh notifications do not arriveX.3.3 Sign-in and SSOYou forgot your password or no admin can sign inSSO sign-in fails with "User is not authorized"Saving the SSO configuration restarts the ConsoleSSO button missing on the login pageSSO sign-in fails with Invalid parameter: redirect_uri in the logX.3.4 Remote controlRelay session stuck in Device offline stateRemote Control disconnects on a device behind a strict corporate networkThe Remote agent logs INADEQUATE_SECURITY in Service.Setup_SignalRA NetMesh link shows "Port not available"X.3.5 CollectionsA custom field value does not populate on the device detail pageApplication Control is not blocking an application I expected it toApp Hub browse shows no apps for a catalogueX.3.6 Ticket SystemInbound emails are not creating ticketsThe connection test reports that the revocation status of the certificate could not be checkedDepartment notification mails do not arriveTicket list refreshes too slowlyX.3.7 Dashboards, Reports, and content surfacesA dashboard panel shows no dataWidgets, panels or custom fields show "SQL access not configured"A duplicated built-in report stops working after an updateA report generation fails with a SQL errorAI answers are not grounded in the documentationX.3.8 When the answer is "look at the logs"Related chapters