nano SIEM
Releases

nano v2.0.30

Supported in:Self-hosted

nano v2.0.30: Vector native port 6000 always requires mutual TLS, with a certificate per sender. The installer checks the host before it asks anything, shows a review screen, and Self-run installs and upgrades log in to the registry themselves.

v2.0.30 includes everything in v2.0.29. It is a security release: the Vector native listener on port 6000 now requires a client certificate from every sender.

To upgrade, follow Upgrade a self-hosted deployment and the Upgrade notes below. v2.0.20 is a required stop: installs on a release older than v2.0.20 upgrade to v2.0.20 first.

Security

  • Vector native port 6000 requires mutual TLS. The Vector protocol has no token, so a client certificate is now the credential. Every connection must present one issued for your install, or the TLS handshake is refused before any event is read. Up to v2.0.29, the port was plaintext with no credential check. It was bound to 127.0.0.1 by default on a single server, and on a role-split cluster no ingest server published it. Now a single server listens on every interface, like 8080 and 8088, and NANO_VECTOR_NATIVE_BIND_ADDRESS narrows it to one address. On a role-split cluster each ingest server publishes it on its private cluster address; set NANO_VECTOR_NATIVE_BIND_ADDRESS (for example 0.0.0.0) for senders outside the private network.
    • One certificate per sender. scripts/nano vector-client-cert <name> issues it and prints a ready-to-paste Vector sink. --csr keeps the key on the sender. --list shows each sender as active, expiring, expired or revoked, and --renew re-signs a sender with no restart on nano.
    • Revoking one sender never affects the others. Each sender has its own trust anchor. --revoke <name> removes only that anchor and restarts Vector. No other sender needs new files.
    • Fails closed. If a TLS file is missing or unreadable, the port refuses every sender instead of falling back to plaintext. The other ingest lanes stay up.
    • Backups. scripts/nano backup now includes .nano-pki, and restore puts it back.
    • Kubernetes. The chart creates the listener CA and certificate, and keeps a sender anchor bundle that starts locked. See Vector-native client certificates.

Installer

  • Host minimums are checked first. Before any question or .env write, the installer refuses a single server with fewer than 2 vCPU, less than 8 GB RAM or less than 40 GB free on Docker's data disk. A host where ClickHouse shares the server with the other services and the enrichment feeds are on needs 16 GB. A host that already runs nano only gets a warning. NANO_SKIP_HOST_MINIMUMS=1 turns the refusal into a warning. Smaller floors apply to role-split hosts without ClickHouse. nano-api is never sized below what it needs to start.
  • A review screen before anything is written. Every question is asked first, then a numbered review screen lists the answers. Enter installs, a number changes that answer, and q quits. back (or <) at any prompt goes to the previous question. Nothing is written before you confirm: no .env, no secrets, no registry login, no container. Unattended runs skip the review.
  • Re-runs keep what you set. A NANO_COMPOSE_OVERLAYS you pass (for example the TLS overlay) is recorded in .env, so re-runs and scripts/nano upgrade keep HTTPS. NANO_BASE_URL on a re-run changes the base URL. A re-run that changes release says it upgrades and that database migrations can't be undone. In a terminal it asks first. n stops with exit code 3, and Enter or end of input with exit code 4; nothing is changed. NANO_CONFIRM_UPGRADE=1 answers yes in advance. Runs with no terminal proceed as before. With no .env but the old data volumes present, the installer stops and explains how to restore the old .env instead of starting over with new passwords.
  • Self-run installs log in to the registry themselves. Enterprise installs now use images.enterprise.customer.lock by default, and the installer logs in with the license values in .env before it pulls. scripts/nano upgrade does the same. The login lives in a private, temporary Docker configuration that is removed afterwards: your own ~/.docker is never written, and an existing login of yours for the registry is left alone. You no longer set NANO_IMAGES_LOCK or run docker login by hand. Air-gapped installs with images already loaded make no registry call.
  • Clear errors before the long steps. The installer stops early, with the fix, when:
    • the TLS overlay is on but the certificate is missing, expired, has a passphrase or doesn't match its key. On an existing install, where nginx may already be serving it, an expired or unreadable (for example root-owned) certificate only gets a warning. NANO_SKIP_TLS_PREFLIGHT=1 skips the check;
    • python3 is missing (it names the install command for your distribution);
    • your user isn't in the docker group, or .env belongs to root;
    • port 80, 8080 or 8088 is already in use (it names the process or container). Re-runs no longer report nano's own ports as in use.
  • Better failure reports. When a service fails to start, the installer shows ClickHouse's full error, logs from every failing or restarting service, and how many times nano-api was killed for running out of memory. A NANO_API_MEM_LIMIT set below the minimum is named with where it was set.
  • Upgrade fixes. scripts/nano upgrade no longer stops with exit code 141 on installs with many images, and --resume no longer says the install has no online license.

Fixes

  • HTTPS installs are healthy. With the TLS overlay, nginx's health check probed plain HTTP, which only redirects, so nginx stayed unhealthy and scripts/nano upgrade couldn't pass its edge check. The check now probes HTTPS on 443.
  • EKS egress policy. With networkPolicy.egress.enabled: true on EKS, api, search, jobs and the connector runner stayed in Init. The VPC CNI agent matches the kubernetes Service ClusterIP, not the API addresses. The chart now adds it with networkPolicy.egress.kubeApi.serviceIP (auto by default). See Egress NetworkPolicy.
  • Search autocomplete keeps hyphenated values. Choosing web-app-json for metadata.log_source=web-app-json no longer rewrites it to web-app-"web-app-json".
  • The rule test panel tests the rule you are editing. It used to keep the query from when it opened. It now follows the editor. A query you change in the panel is labeled, and Apply to editor asks before it replaces your rule.

Upgrade notes

  • Required stop at v2.0.20. See above.
  • No registry login step from v2.0.30. With an online license, the v2.0.30 installer and scripts/nano upgrade log in to the registry themselves. You can skip the login step in Upgrade a self-hosted deployment. Offline licenses still log in by hand or use the image bundle.
  • NANO_IMAGES_LOCK is no longer needed on Self-run. An install that recorded the internal image names after a failed v2.0.29 install, with no container created for them, switches to the customer registry (same digests) and says so.
  • Host minimums. An existing install below the new minimums gets a warning, not a refusal.
  • A low NANO_API_MEM_LIMIT is refused. If you pinned NANO_API_MEM_LIMIT in .env or the environment below 640 MiB (Self-run) or 384 MiB (Open), the installer now refuses instead of starting nano-api too small to boot. Raise it or remove the line so the installer sizes it.
  • Re-runs ask before an upgrade. A ./install.sh re-run in a terminal that changes release now asks [y/N]. Declining exits 3 (n) or 4 (Enter or end of input). If you drive the installer through a terminal from a script, set NANO_CONFIRM_UPGRADE=1.
  • A process holding port 6000. Before the rollout, scripts/nano upgrade checks that no other process on the host holds port 6000 on the address nano binds, and refuses with the cause if one does. Stop that process or set NANO_VECTOR_NATIVE_BIND_ADDRESS, then run the upgrade again.
  • Migrations run automatically. New PostgreSQL and ClickHouse migrations apply during the upgrade.

Vector native senders

If nothing sends to port 6000, there is nothing to do. To check before you upgrade, search source_type=vector_native over the last 24 hours. On a single server, an install.sh re-run also reports that count.

Otherwise, after the upgrade:

  1. On the nano server (role split: the first app server), issue one certificate per sender:

    cd ~/nano
    scripts/nano vector-client-cert edge-dc1

    This writes edge-dc1.crt, edge-dc1.key and ca.crt to ./nano-vector-edge-dc1/ and prints the sink config. Use --csr <file> to keep the key on the sender.

  2. Role split only: copy the first app server's .env to every server and update every ingest server, so they trust the new sender. See Vector native (port 6000).

  3. Copy the three files to the sender and add the TLS settings to its Vector sink:

    [sinks.nano]
    type = "vector"
    inputs = ["<your source>"]
    address = "nano.example.com:6000"
    version = "2"
    tls.enabled = true
    tls.crt_file = "/etc/vector/nano/edge-dc1.crt"
    tls.key_file = "/etc/vector/nano/edge-dc1.key"
    tls.ca_file = "/etc/vector/nano/ca.crt"
  4. Restart the sender's Vector and check that events arrive.

  • Port 6000 is now reachable from the network. On a single server it moves from 127.0.0.1 to every interface; to keep it on one address, set NANO_VECTOR_NATIVE_BIND_ADDRESS in .env (for example 127.0.0.1 if every sender runs on the server). Role-split ingest servers publish it for the first time, on the cluster address. Docker publishes it, so UFW doesn't filter it. Allow it only from your senders in your cloud firewall or Docker's DOCKER-USER chain. See Firewall.
  • Senders through NAT or a load balancer need that name or address in the listener certificate: add it to NANO_VECTOR_NATIVE_SANS in .env and re-run install.sh.
  • Plaintext lab clusters (allow_plaintext_private_network) have no listener: the port refuses every sender.
  • Kubernetes with vector.native.enabled: true: senders without a client certificate are refused from the upgrade on. Follow Vector-native client certificates.

Full details are in Vector native (mutual TLS).

On this page