Settings

Settings search

The Settings page has a unified search bar at the top. Type at least two characters to search across every settings sub-page (titles, options, and descriptions) and jump directly to the page that contains the option. Results are ranked by relevance and can be navigated with the arrow keys and Enter.

General

• FQDN used for Let's Encrypt
• Global webhook URL, secret, mode, and thresholds
• Test result retention in days (0 disables TTL cleanup, default 180)
• Webhook log retention

Security

• REST API and MCP tokens
• Allowed actions for external integrations
• TLS certificate management on the /cert page
• Admin password change on the Change Admin Password page (requires the current password; minimum 8 characters)

License

The License page shows the cached license state - plan, maximum Probes, validity, expiration date, and last validation time - and lets you paste a new license token. The Core validates the token against the Linknesis Panel periodically.

Notifications

The Notifications Configuration page controls test-completion notifications in the GUI: native browser popups (which require browser permission) and the navbar bell with an unread-notification dropdown.

AI

Configure AI providers, models, and analysis prompts. Test connectivity to each provider and set failover order. Providers are tried in priority order until one returns a valid response.

Map

Enable or disable the map, configure MaxMind GeoIP key, and set thresholds that color map links and trigger webhook alerts. Two related settings control GeoIP positioning: Auto positioning of new Probes (off by default) geolocates a Probe automatically the moment it first connects, and GeoIP cache expiration controls how long an auto-obtained position is kept before it's re-queried. Neither setting affects Probes you've positioned manually - those never expire or get overwritten. See Map for the full positioning workflow, including bulk-locating existing Probes.

Database maintenance

The Settings page includes database maintenance tools:

• Optimize and Restart Database - reclaims disk space and memory used by the database. Use this after deleting a large amount of test data to actually free up RAM, not just disk space.
• Delete All Tests - bulk-delete tests and correlated data by date range. Running tests in the range are stopped first, and orphaned results/webhooks/AI chats/shared records are purged in batches.
• System Logs Rotation - controls how long the Core's own system logs are kept (default 180 days) and what time of day rotation runs, so log files don't grow unbounded on the host over time.

Core and Probe Updates

The Core Update card shows the running Core version and controls automatic Core updates. When enabled, the Core checks the channel-specific manifest (https://linknesis.com/core-versions-stable.json or https://linknesis.com/core-versions-beta.json) daily and the host-side updater pulls a new image when available. Use the Channel selector to choose between the stable and beta update channels. Clicking Update now starts the update immediately and shows live progress until the Core restarts.

The Probe Updates toggle controls whether connected Probes are allowed to update automatically. When enabled, Probes whose binary version differs from the Core version request the matching binary, download it from the Core API update endpoint, verify its SHA-256 hash, and self-replace. Older Probes that do not support the URL-based path fall back to receiving the binary over WSS. Disabling this toggle stops new automatic updates but does not affect Probes already in the middle of an update.