henrygd/beszel · error

no info in response

Error message

no info in response

What it means

unmarshalLegacyResponse returns this when a GetContainerInfo response has resp.String == nil, so the agent provided no container info payload. Like the logs case, the response was decoded but the expected field is empty.

Source

Thrown at internal/hub/transport/transport.go:86

		*d = *resp.Fingerprint
		return nil
	case common.GetContainerLogs:
		d, ok := dest.(*string)
		if !ok {
			return fmt.Errorf("unexpected dest type for GetContainerLogs: %T", dest)
		}
		if resp.String == nil {
			return errors.New("no logs in response")
		}
		*d = *resp.String
		return nil
	case common.GetContainerInfo:
		d, ok := dest.(*string)
		if !ok {
			return fmt.Errorf("unexpected dest type for GetContainerInfo: %T", dest)
		}
		if resp.String == nil {
			return errors.New("no info in response")
		}
		*d = *resp.String
		return nil
	case common.GetSmartData:
		switch d := dest.(type) {
		case *map[string]smart.SmartData:
			if resp.SmartData == nil {
				return errors.New("no SMART data in response")
			}
			*d = resp.SmartData
			return nil
		case *smart.SmartDataResponse:
			if resp.SmartData == nil {
				return errors.New("no SMART data in response")
			}
			d.Data = resp.SmartData
			d.Complete = resp.SmartComplete
			return nil

View on GitHub (pinned to b38fb7dafa)

Solutions

1. Confirm the container exists (docker ps / podman ps) on the host
2. Update the agent to a hub-compatible version
3. Check agent logs for container-runtime errors
4. Retry after the container is running

// confirm the container exists before requesting info
if !containerExists(host, containerName) {
    return nil
}

if err := UnmarshalResponse(resp, common.GetContainerInfo, dest); err != nil {
    if strings.Contains(err.Error(), "no info") {
        return nil // container gone or unsupported
    }
    return err
}

When it happens

Trigger: UnmarshalResponse on a GetContainerInfo request where the legacy AgentResponse lacks the String field.

Common situations: Querying info for a stopped/removed container; agent too old to support GetContainerInfo; agent-side runtime errors that leave the payload nil.

Related errors

• no logs in response
• no system data in response
• no fingerprint in response
• no SMART data in response
• system exists

AI-assisted analysis of henrygd/beszel@b38fb7dafa (2026-08-31). Data as JSON: /api/errors/aaf9f666961be571. Report an issue: GitHub.