Skip to main content

​
Feedback

Help improve DataRelay Link by reporting reproducible problems and real workflows that would benefit from improvement.

Report a Bug

Report a reproducible problem with version, environment, steps, expected behavior, actual behavior, and redacted diagnostics.

Request a Feature

Describe the problem or workflow first, then the behavior you want.

​
Before you submit

  1. Search existing GitHub issues.
  2. Report the installed DataRelay Link version and diagnostic results.
  3. Include the Server or Agent Host role and affected feature.
  4. Provide the smallest reliable reproduction sequence.
  5. Remove secrets and customer data.
Never post passwords, private keys, enrollment tickets, OAuth/bearer tokens, API keys, or customer data in a public issue.

​
Useful bug-report fields

  • DataRelay Link version / release channel / diagnostics
  • Server or Agent Host platform and role
  • affected Managed Host public name
  • affected Remote Service, Object/Group, or Access Policy name
  • deployment mode / NAT / firewall context when relevant
  • expected and actual behavior
  • exact reproduction steps
  • relevant redacted show/status/test/system diagnostics output
  • whether reconnect, reboot, update, restore, or another lifecycle event is involved

​
Feature-request areas

  • Managed Host enrollment and lifecycle
  • Network / Service / Permission Objects and Groups
  • Remote Services and Remote Access
  • Internet Access
  • AI Identity, AI Access, and MCP
  • ConfigurationBundle and AI-assisted configuration
  • CLI and operator UX
  • update, backup/restore, diagnostics, and support bundle
  • Linux, macOS, and Windows Agent Host compatibility
  • documentation
DataRelay Link is built for small environments, from a few systems to a few dozen Managed Hosts. It is not intended for large-fleet orchestration or as a full SASE/SWG platform.
Last modified on October 28, 2026