Skip to content

Nexus Repository: mandatory telemetry + read-only lockout from 3.97.0 — allowlist nxrm.telemetry.sonatype.com #5271

Open

Description

Summary

Starting with Sonatype Nexus Repository 3.97.0 (released 2026-10-14), Sonatype introduced required base telemetry. If an instance cannot successfully upload this telemetry, it enters read-only mode after a grace period.

This affects any AzureTRE deployment running sonatype/nexus3 (or Nexus Repository in general) that gets upgraded to 3.97.0+, particularly in network-restricted / air-gapped environments where outbound calls aren't normally allowlisted.

Details

  • An administrator must acknowledge the required base telemetry requirement during onboarding — applies to new installs and instances upgraded to 3.97.0+.
  • Telemetry includes daily repository request counts and current component totals (used for entitlement/usage reporting).
  • If telemetry fails to upload, a grace period starts (length varies by edition — CE vs Pro). During the grace period the instance continues operating normally but shows a "Baseline Telemetry Upload Issue" warning.
  • If the grace period expires with no successful upload, the instance flips to read-only (blocks writes/deploys) until telemetry succeeds.
  • A new "Baseline Telemetry" health check surfaces acknowledgement/upload status.

Telemetry endpoint (needs firewall/proxy allowlisting)

Host: nxrm.telemetry.sonatype.com (HTTPS/443)

  • Community Edition: /production/oss/ingest, /production/oss/v2/ingest
  • Pro Edition: /production/ingest, /production/v2/ingest

Action items

  • Add nxrm.telemetry.sonatype.com to the egress allowlist / firewall rules for the Nexus VM/service (NSG, Azure Firewall rules, proxy config — wherever AzureTRE currently scopes Nexus egress)
  • Decide policy on upgrading the Nexus image past 3.97.0 given this new hard dependency on external connectivity
  • If AzureTRE workspaces are intended to run air-gapped, evaluate contacting Sonatype Support re: entitlement options for restricted environments, per their docs

References

Activity

  1. BHughesCGI commented on Oct 22, 2026

    @BHughesCGI
    Collaborator

    Thanks for raising this and for providing the detailed context and references. We’re reviewing the impact of the Nexus 3.97.0 telemetry requirement on AzureTRE, including the necessary firewall allowlisting and implications for restricted or air-gapped deployments.

    At this stage, it looks likely that access to the telemetry endpoint will need to be permitted when we move to a Nexus version affected by this change, unless security updates require an earlier upgrade. We’ll also review the upgrade policy and update the relevant guidance as needed.

  2. JayDoubleu commented on Oct 28, 2026

    @JayDoubleu
    Collaborator

    Pull request #5278 updates Nexus to 3.97.2 and acknowledges the required base telemetry. The code is ready for review. The maintainers have not approved it yet, and the change can still change after further discussions.

    #5278 is a breaking change. The upgrade to Nexus bundle 4.0.0 is one-way, and Nexus 3.97 must send telemetry to nxrm.telemetry.sonatype.com. If the telemetry uploads fail for 10 days, Nexus becomes read-only. Read the PR description and the upgrade section in the docs before you use it.

    Tests of #5278:

    • Local tests: unit tests, pre-commit, mkdocs build --strict, and an upgrade from Nexus 3.94.0 to 3.97.2 on the same data volume.
    • A live upgrade in a CI environment in another fork: the Nexus shared service upgraded from 3.94.0 to 3.97.2, and the Linux VM E2E test passed against the upgraded Nexus.
    • Not tested : a new installation in Azure, the upgrade request with force_version_update=true, and a TRE with forced tunnelling or a proxy that inspects TLS.

    If you need only the fix for the compromised eMudhra intermediate CAs (#5276), use #5279. It updates Nexus from 3.94.0 to 3.94.3, which Sonatype lists as a fixed version. It does not add telemetry, and it is not a breaking change. Local tests of #5279 passed. The shared service test in Azure is running now.

    If you keep your own fork of AzureTRE, you can apply the commits of either PR before the merge. The maintainers can still change both PRs during the review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions