# Release Notes — 2.104 Covers the `2.104.x` Helm chart series. Most recent patch: **2.104.1**. _Unless a subsection says otherwise, changes apply to both Monad SaaS and self-hosted._ ## New features & improvements **SaaS only** - **Send OpenTelemetry data on port 443** — the per-pipeline ingest host now accepts OTLP over HTTP and gRPC on port 443, so senders behind firewalls that only allow HTTPS egress can reach Monad. Ports 4317 and 4318 keep working. [Docs →](https://app.monad.com/docs/inputs/monad/monad-otel) (2.104.0) - _How:_ point your OTLP exporter at `https://.data.monad.com`; gRPC clients add an explicit `:443`. **Self-hosted only** - **Built-in route for the per-pipeline ingest host** — the chart can now serve `.data.` for HTTP ingest and OTLP (HTTP and gRPC) on the same listener, so you no longer write that route by hand. Existing hand-written routes keep working. [Docs →](https://app.monad.com/docs/guides/self-managed/networking) (2.104.0) - _Access:_ off by default — set `http-input.routes.data.enabled: true`, usually with `parentRefs` naming the Gateway listener for the wildcard hostname. ## Fixes - **S3 input resumes where it stopped** — an interrupted run now picks up at the file it was reading instead of re-reading earlier files, and no longer reports a false invalid-JSON error. (2.104.1) ## Breaking changes None. ## Need help? See the [Monad docs](https://app.monad.com/docs) for setup guides and reference, or reach out to Monad Customer Support at [support@monad.com](mailto:support@monad.com) or via your dedicated Slack customer channel. :::note Self-hosted deployments upgrade to a `2.104.x` release with `helm upgrade`. Review the **Breaking changes** section above before upgrading; when it says "None," the upgrade is drop-in. :::