How connections work

What happens between your question and your systems, where credentials live, and how proxy gateways reach networks Opsaido can't.

The flow of a request

YouChat, Telegram, Teams, Slack or voice
question
OpsaidoPicks the tools · asks for approval · uses the stored login · logs everything
API · SSH · WinRM
Your systemsServers, hypervisors, DNS, firewalls, cloud…
AI providerGets your question and the results to explain them. Never passwords, keys or tokens.
  1. You ask in plain English.
  2. Opsaido chooses the tools for the systems you’ve connected and sends the question, with those tools, to your AI provider.
  3. The AI picks a step, for example “list the VMs on the Proxmox cluster”.
  4. Opsaido checks the step. A read runs straight away; a change waits for your approval (see Approvals and dry runs).
  5. Opsaido connects to the system with the connector’s stored login, runs the step and records it in the audit log.
  6. The result goes back to the AI, which takes the next step or writes the answer for you.

Logins are stored encrypted in Opsaido‘s database and only decrypted for the moment a connection is made. The AI sees what a step returned, never how Opsaido signed in.

What uses a connector

UseWhenApproval
Test connectionWhen you press the button; pins the SSH host key the first time—
MonitoringEvery few minutes: CPU, memory, disk, status, alerts—
AssistantWhen you ask something about that systemReads: none · changes: yes
Scheduled jobsOn their scheduleAs set on the job
Remote accessSSH terminal or RDP desktop in the browserNeeds the remote access permission

How each kind of system is reached

Connects withSystemsThrough a gateway?Through an HTTP proxy?
SSHLinux, KVM / libvirt hosts, Docker over SSH, Terraform and Ansible hosts✓—
WinRMWindows, Hyper-V, Exchange, Windows DNS, AD CS, MECM✓—
Web API (HTTPS)Proxmox, Xen Orchestra (XCP-ng), Docker API, firewalls, NAS, backups, DNS providers, Microsoft 365, Azure…—✓
Native protocolsActive Directory (LDAPS), databases, VMware——

Web APIs in another network can usually be reached through an HTTP proxy instead of a gateway. Set the default in Settings → General → Outbound proxy, and choose default, direct or a custom proxy on each connector. Private addresses skip the default proxy unless you change the bypass list.

Proxy gateways (jump hosts)

Use a gateway when Opsaido can’t reach some hosts directly: a DMZ, another site, an isolated VLAN or a customer network. The gateway is a machine that can reach them, and Opsaido goes through it.

Your network
OpsaidoUses the gateway's login, then the target's
SSH or WinRM
Can reach both
GatewayLinux (SSH) or Windows (WinRM). No admin rights needed.
SSH · WinRM
Isolated network
Linux hosts
Windows hosts

Set one up

  1. Add the gateway: Settings → Connectors → Add connector → Proxy gateways. Choose Linux gateway (SSH) or Windows gateway (WinRM) and give it a login.
  2. Test it. The test checks the login and pins its SSH host key. On a Windows gateway it also checks the OpenSSH client is installed (needed for Linux targets).
  3. Point hosts at it: on each Linux or Windows connector behind it, choose the gateway in the Proxy gateway field.
  4. Test each host. From now on everything for that host — tests, monitoring, assistant steps, jobs — goes through the gateway.

What happens for each target

TargetThrough a Linux gateway (SSH)Through a Windows gateway (WinRM)
LinuxSSH is tunnelled through the gateway (ProxyJump). Both host keys are pinned. The browser terminal works too.The gateway’s own OpenSSH client (ssh.exe) connects. Key login only; the target’s host key is pinned on the first test.
WindowsWinRM runs over a SOCKS tunnel on the gateway. Names resolve on the gateway’s side, so Kerberos works.Invoke-Command runs on the gateway with the target’s own login.

What the gateway needs

GatewayNeeds
Linux (SSH)SSH access and TCP forwarding allowed (AllowTcpForwarding yes, the default). The account needs no sudo.
Windows (WinRM)WinRM access. For Linux targets: the OpenSSH Client feature. For workgroup Windows targets: those hosts in TrustedHosts.
NetworkIt must reach the targets on SSH (22) or WinRM (5985/5986); Opsaido must reach it on SSH or WinRM.

The gateway holds no logins of its own for the targets: Opsaido sends each target’s login through it for that connection only. Still, treat a gateway like any jump host — patch it and limit who can sign in to it.

Good to know

QuestionAnswer
Can one gateway serve many hosts?Yes, as many as you like. Use tags to keep them grouped.
Can I disable a gateway?Yes; its hosts then show “Proxy gateway is disabled” until you turn it back on.
Can I delete a gateway in use?No. Move its hosts to another gateway, or clear their field, first.
Do gateways chain?No, one gateway per host. Pick a gateway that can reach the target directly.
What about web APIs behind it?Use an HTTP proxy for those (see the tip above).