How can we help?

Each product has its own console, and they all share one sign-in (single sign-on) — log into one and you can switch between the others from the app switcher in the top-right without signing in again.

• Customer Portal (account, users, billing, support): portal.mantisops.net
• MantisRMM: rmm.mantisops.net
• Mantis360: 360.mantisops.net
• MantisNMS: nms.mantisops.net

Accounts are created for you when you start a trial or purchase — there is no public self-serve sign-up. If you need access, ask an administrator at your organization to invite you, or start a trial.

1. Confirm you're using the email your organization invited (the same address across all products).
2. Use Forgot password on the sign-in page to reset it. The reset link is time-limited — request a fresh one if it expired.
3. If you were recently invited, check for the activation email (including spam) and finish setting your password first.
4. Still stuck? Your account may be disabled or your subscription expired — an owner/admin at your organization can re-enable it, or email support.

MFA is required on every account. If your authenticator codes are rejected:

1. Make sure your phone's clock is set to automatic/network time — TOTP codes fail if the clock drifts.
2. Enter the current 6-digit code (they rotate every 30 seconds); if it's about to expire, wait for the next one.
3. Lost your device? An owner or admin at your organization can reset MFA for your user under Portal → Users, after which you'll re-enroll on next sign-in.
4. Some accounts use email one-time codes instead of an app — check your inbox for the code.

Owners and admins manage users centrally in the Customer Portal: portal.mantisops.net → Users. From there you can invite a user, assign a role (which controls what they can see and do), scope them to specific companies/sites, and enable “Can answer live chat” for support agents. Removing a user immediately revokes their access across all products.

1. In MantisRMM → Agents (or the Portal), choose Deploy agent and copy the installer for your platform.
2. Windows: run the signed installer as Administrator. macOS: open the notarized .pkg and approve the system extension when prompted. Linux: run the provided install script with sudo.
3. The agent installs a background service that starts on boot and checks in automatically — no inbound firewall rules needed (it dials out over 443).
4. The endpoint appears in your fleet within a minute or two of install.

See the full RMM getting-started guide for mass-deployment (GPO/RMM/MDM) options.

1. In Mantis360 → Probes, download the probe for the network you want to scan and install it on a machine that can reach that subnet.
2. The probe registers itself and appears online in the console. Give it a name and assign it to a site.
3. Create a scan targeting a CIDR range (e.g. 10.0.0.0/24). One probe can scan the subnets it can route to.
4. For the most accurate OS/service fingerprinting, allow the probe outbound access and don't block it at an internal firewall/IPS.

Full steps: Mantis360 getting-started guide.

1. In MantisNMS → Collectors, download and install the collector on a host inside the network you want to monitor.
2. Once it's online, add sensors — ping/ICMP, SNMP (device health, interfaces), HTTP, TCP port, and 50+ other types.
3. For SNMP sensors, store the community string or SNMPv3 credentials in the credential vault and assign them to the device.
4. Enable NetFlow/IPFIX export on your routers/switches pointed at the collector to see traffic-flow analytics.

Full steps: MantisNMS getting-started guide.

An agent goes offline when it can't check in. Work through:

1. Is the machine on and awake? Sleeping/hibernating or powered-off endpoints report offline until they resume.
2. Is the service running? On Windows check the MantisRMM Agent service; on macOS the launch daemon; on Linux systemctl status the agent service. Start it if stopped.
3. Outbound 443: the agent needs outbound HTTPS to *.mantisops.net. A proxy or egress firewall that blocks it will show the agent offline — allow-list the domain.
4. Reinstall: if it stays offline, re-run the installer on the endpoint. Re-installing the same machine reattaches to its existing record (no duplicate, no extra charge).

1. Confirm the agent is online first — remote desktop needs an active connection.
2. macOS black screen: the agent needs Screen Recording permission and an active user session. Grant System Settings → Privacy & Security → Screen Recording to the MantisOps agent, then reconnect.
3. Windows lock/login screen: capturing the secure desktop (Ctrl-Alt-Del / UAC prompts) is supported — if the screen appears frozen right at lock or login, disconnect and reconnect to rebind the session.
4. If the picture is connected but not updating, a reconnect re-establishes the video stream. Persistent issues on one monitor: try selecting a different display in the session toolbar.

1. Latency is dominated by distance to the endpoint and its upload bandwidth. A wired connection on the remote side helps most.
2. Lower the session quality/framerate in the toolbar for slow links — it trades sharpness for responsiveness.
3. Brief freezes right as you type are usually a momentary capture stall; they self-recover. If it persists, reconnect the session. Keep the agent updated — capture reliability improvements ship regularly.

1. Confirm the endpoint is online and not pending a reboot from a prior update — some updates only complete after a restart.
2. On Windows, updates run through the OS update stack; a machine that can't reach its update source (WSUS/Windows Update) won't install. On Linux/macOS the agent uses the native package manager (apt/dnf/yum/zypper / softwareupdate).
3. Use Install all and allow the endpoint to reboot when prompted — large update sets can require multiple reboots to fully apply.

1. Check the job/activity log for the endpoint — it records whether the action dispatched, ran, and its output.
2. The endpoint must be online at dispatch time; offline agents pick the job up on their next check-in only if it's still queued.
3. Scripts run as SYSTEM/root by default. If a step depends on a user context or mapped drive, account for that in the script.

1. Confirm the probe is online and assigned to a network that can route to the target subnet.
2. Check the CIDR is correct and actually contains live hosts (e.g. 10.0.0.0/24, not a host address).
3. Firewalls/IPS between the probe and the targets can silently drop scan traffic — run the probe on the same segment where possible, or allow it through.
4. Hosts that only respond to certain protocols may need the right scan profile; very quiet hosts (no ARP, no open ports) can be missed on routed scans.

1. Check the machine hosting the probe is on and the probe service is running.
2. The probe needs outbound 443 to *.mantisops.net to report results — allow it through any egress filter/proxy.
3. Restart the probe service, or reinstall it if it doesn't recover.

Fingerprinting infers the OS and services from network responses, which security devices can distort:

• A firewall/TLS proxy in the path can make a host look like it's running services it isn't (e.g. a “443” that's really the firewall). Scanning from inside that boundary gives cleaner results.
• Hosts behind a SYN-proxy or IPS may show phantom ports. Where possible, place the probe on the same subnet as the targets to avoid the middlebox.
• If a specific asset is mis-identified, open a ticket with the asset and scan details and we'll tune the fingerprints.

1. Findings update on the next scan — re-run the scan (or wait for the schedule) so the asset is re-evaluated.
2. Enable auto-resolution so findings that are absent from the latest scan are closed automatically.
3. Assets removed within 7 days of first discovery, or marked out-of-scope, are excluded from findings and billing.

1. Confirm the collector is online — sensors report through it, so a down collector takes its sensors with it.
2. Check the target device is reachable from the collector (ping it from that host).
3. SNMP sensors: verify the community string / SNMPv3 credentials in the vault are correct and that SNMP is enabled on the device and permits the collector's IP.
4. Confirm the poll interval and that no firewall blocks the sensor's protocol (ICMP, SNMP/161, the TCP port, etc.).

1. Check the collector host is on and the collector service is running.
2. It needs outbound 443 to *.mantisops.net to report — allow it through egress filtering.
3. Restart the service, or reinstall the collector if it doesn't come back.

1. Tune the sensor's thresholds and add a “must breach for N intervals” condition so a single blip doesn't alert.
2. For availability, alerts are based on state transitions (up↔down), so brief recoveries won't spam you — widen the interval if a link is genuinely marginal.
3. Set notification schedules/escalation so the right people are alerted at the right times.

1. Enable NetFlow/IPFIX export on the router/switch and point it at the collector's IP.
2. Make sure the exporter's flow packets can reach the collector (no firewall blocking the flow UDP port).
3. Flow data populates once the device starts exporting — allow a few minutes for the first window to appear.

Billing is a monthly subscription charged automatically to your card on file:

• MantisRMM — per managed endpoint (agent) under management during the month. Removing an agent takes effect next cycle; re-installing the same machine doesn't double-count.
• Mantis360 — tiered by asset count in scope (deleted/out-of-scope assets aren't billed).
• MantisNMS — tiered by sensor count.

Bundle all three for a discount. Manage everything under portal.mantisops.net → Billing.

When a trial ends or a subscription lapses, access is paused (your data is retained during the grace window). Add or update payment under Portal → Billing to restore access, or email support if you think this is a mistake.

Go to portal.mantisops.net → Billing to update your card, view invoices, and see your current usage against your plan. For a refund or credit question, email billing@mantisops.net.