github akkadotnet/akka.net 1.5.75
Akka.NET v1.5.75

one hour ago

1.5.75 November 16th, 2026

Akka.NET v1.5.75 adds restart-free TLS certificate rotation for the DotNetty transport, fixes two certificate-validation gaps that silently disabled security checks, backports two Akka.Persistence ordering fixes, and brings Akka.Reminders to the 1.5 line as Akka.Reminders.* packages.

Upgrading from Aaron.Akka.Reminders? The package IDs are now Akka.Reminders, Akka.Reminders.Sql, Akka.Reminders.SqlServer, Akka.Reminders.PostgreSql and Akka.Reminders.Sqlite, and the module shares the Akka.NET version number. Change your package references; stored data is read-compatible, proven by a golden-database spec against data written by the released Aaron.Akka.Reminders 1.5.73 packages.

Two behavior changes to check before upgrading. CertificateValidation.ValidateHostname(expectedHostname) and SslOptions.CustomValidator now actually enforce what they were configured to enforce. Both were silently no-ops in earlier versions, so a peer that used to connect may now fail the TLS handshake. See the Akka.Remote / TLS section below.

Akka.Remote / TLS

  • Rotate DotNetty TLS certificates without a restart - A node can now pick up a renewed TLS certificate with no restart. Set akka.remote.dot-netty.tcp.ssl.certificate.common-name to find the certificate in a store by name, or point ssl.certificate.path at a folder of PKCS#12/PEM files, and place the renewed certificate beside the old one. New connections use it within about 10 seconds; open connections keep the certificate they started with. In code, use DotNettySslSetup.FromSource with TlsCertificateSource, or SslOptions.CertificateSource in Akka.Hosting. Existing TLS setups are unchanged. Behavior change: a certificate source checks that the certificate is allowed for the role. With require-mutual-authentication = true (the default) the certificate must allow both client and server authentication. X509Certificate, a single-file Path and a Thumbprint are not checked this way, so a certificate that worked before may be skipped with a warning when moved to a source, and a node with no other usable certificate does not start.
  • Add TlsCertificateSource for TLS certificate rotation - The new Akka.IO.TlsCertificateSource resolves a certificate from a store common name, a thumbprint, a single file, or a folder of files, and re-checks it once a minute. A certificate that cannot be used is judged again at the next look-up, so granting access to a private key later is picked up. The source never disposes a certificate it has published. PEM files need the net6.0 target; the netstandard2.0 build skips them and logs why.
  • Security fix: CertificateValidation.ValidateHostname(expectedHostname) now enforces the expected hostname - In v1.5.74 and earlier this validator logged a warning and did not compare expectedHostname with the certificate, so a node that used it to check inbound client certificates accepted every client certificate. It now rejects any certificate that does not match the name, by the rules of .NET's X509Certificate2.MatchesHostname. Behavior change: a certificate that does not match now fails the TLS handshake, and on the dialing side that shuts the ActorSystem down with exit code 79. Only nodes that opt in are affected: validate-certificate-hostname defaults to false. A certificate whose subject alternative name extension holds a malformed entry is rejected, as in 1.6. ValidateHostname() without an argument is unchanged.
  • Security fix: SslOptions.CustomValidator in Akka.Remote.Hosting now applies when the certificate is set by file path or thumbprint - In earlier versions the validator only ran when SslOptions.X509Certificate was set, and was otherwise ignored without a warning. Behavior change: the validator now runs, so a peer it rejects fails the TLS handshake. A CustomValidator with no certificate in the options now fails at startup with a ConfigurationException, and the certificate loads when WithRemoting runs rather than when the ActorSystem starts.
  • Log an unexpected failure of the once-a-minute TLS certificate check - The check's catch block swallowed any unexpected exception without a trace. The source already logs every failure it expects, so anything reaching this catch is a bug, and it now logs a warning. The node keeps its current certificate, as before.

Akka.Reminders

  • Port Akka.Reminders to v1.5 - Akka.Reminders now ships on the 1.5 line, dual-targeted at netstandard2.0 and net10.0 so it reaches .NET Framework 4.8 through .NET 10. This is a port rather than a backport: the module is new to 1.5, so the whole thing was re-targeted onto the branch. It ships five packages — Akka.Reminders, Akka.Reminders.Sql, Akka.Reminders.SqlServer, Akka.Reminders.PostgreSql and Akka.Reminders.Sqlite — renamed from Aaron.Akka.Reminders* and now sharing the Akka.NET version number. A golden-database spec proves the new packages read data written by the released Aaron.Akka.Reminders 1.5.73 packages. AOT is not supported on Akka.NET 1.5, so the module carries no AOT annotations here. The module ships no reference.conf and no MultiNode specs; serializer registration goes through the Akka.Hosting API, so HOCON-only users have no configuration surface for it.
  • End every older live occurrence when a newer one is sent - A recurring reminder could deliver an older occurrence after a newer one when its interval was well below MaxSlippage and its shard region was missing for a while and then came back. The recipient got the newer occurrence and then the older one, and both acknowledgements succeeded. When the newest occurrence of a series moves to AwaitingAck, every older live occurrence of that series now expires in the same storage commit. Fixes #8965.
  • Cap the older occurrences one send ends at 256 - The fix above expires ceil(earliness / interval) older occurrences per early send with no upper bound, and Reminders accepts any interval above zero. A 1 ms interval put about 5,000 expiries in one commit, and a sub-millisecond interval could put millions into the scheduler's memory. The cap is 256 per send, nearest first. No interval of about 20 ms or more at the default 5 s MaxSlippage can reach it. Below that, during a shard region outage, an older occurrence more than 256 intervals back can still be sent after a newer one; failure-modes.md documents the limit.

Akka.Persistence

Docs

  • TLS certificate rotation article - New article covering how a node picks its certificate and when a renewed one is used, how to rotate, changing an existing setup, trust by CA and name, loading from Azure Key Vault, rotating with a rolling restart, and troubleshooting. It leads with Akka.Hosting, then HOCON, then code. security.md now says which certificate options can rotate without a restart, and no longer claims that revocation is checked, which the DotNetty transport does not do. A follow-up (#8970) corrected the article's note about CustomValidator, which does apply to thumbprint and single-file certificates since #8963.

Build and tests

  • Skip the simultaneous-disassociate graceful-close spec on .NET Framework - On net48 the tests load Akka.Remote's netstandard2.0 build, where HalfClose falls back to a full close. When both sides disassociate at once, one side can close while the other's frames are still unread and its kernel sends an RST, so the spec failed intermittently. The two sibling "no reset" tests in the class already skip on .NET Framework for the same reason. This changes no product code.
  • Akka.Reminders CI lane - The new module adds a Linux-only net_tests_reminders_linux lane with its own Incrementalist config, because Akka.Reminders.Migration.Tests starts SQL Server and PostgreSQL containers unconditionally and the Windows agents have no Docker. src/contrib/reminders/** is excluded from the Windows test configs.

1 contributor since release 1.5.74

COMMITS LOC+ LOC- AUTHOR
13 40157 552 Aaron Stannard

To see the full set of changes in Akka.NET v1.5.75, click here.

Don't miss a new akka.net release

NewReleases is sending notifications on new releases.