Troubleshooting SeqOps Agent Connection Issues

If the SeqOps Agent appears offline, the platform may stop receiving data from that server. An agent may appear offline due to connectivity, configuration, or system issues. Work through the following steps to identify and resolve the problem.

Common Causes of Offline Agents

• •Network connectivity issues
• •Agent service not running
• •Firewall or outbound connection restrictions
• •Server configuration changes
• •Agent registration issues

Verify Agent Status

1. Check the SeqOps Agent service on the server.
2. Confirm the agent process is running. On Linux, use systemctl status seqops-agent. On Windows, check the Services console for the SeqOps Agent service.
3. Restart the SeqOps Agent service to restore communication with the platform if necessary.
4. Verify the agent appears online in the SeqOps platform.

Review the Agent Logs

The agent writes detailed logs that often reveal the root cause. You can find them at /var/log/seqops/ on Linux or C:\ProgramData\SeqOps\logs\ on Windows. Look for connection errors, authentication failures, or crash traces.

Verify Network Connectivity

Confirm that the server can reach the SeqOps platform endpoints required for agent communication. A quick test with curl or Test-NetConnection on port 443 will confirm whether the host is reachable.

Check Firewall Rules

Confirm that outbound HTTPS traffic is allowed through any local or network firewalls. Proxy configurations may also need updating to permit the agent's traffic.

Check the Registration Credentials

Each server registers with its own Tenant ID, Server ID, and Registration Token from View API Secrets. A credential set is valid for roughly 7 days and can be used once. If provisioning was attempted with an expired or already-used set, the agent can't register — contact support@seqops.io with the server name.

Restart the Agent

If everything else checks out, restart the SeqOps Agent service to restore communication with the platform. This often resolves transient connection issues.

When the agent is offline, the platform cannot receive updated metadata from the server.

When to Contact Support

If the agent remains offline after completing the steps above, contact the SeqOps support team and include:

• •Server operating system
• •Agent version
• •Time when the agent went offline
• •Any recent system changes

You can also run seqops-agent diagnose to collect a diagnostic bundle before reaching out.