- Subject
- Windows & PowerShell
- Filed
- Source
- [email protected] (Michael Becker)
- Loans
- 754
PRTG 128 Ends NATS for Multi-Platform Probes: Migrate to QUIC
PRTG 126 requires QUIC for new multi-platform probes; PRTG 128 disconnects probes still using NATS. Check migration steps, ports and TCP fallback.


PRTG 128 will disconnect multi-platform probes that still rely on NATS. Teams have a release cycle to move those probes to QUIC after upgrading to PRTG 126, which already requires QUIC for new multi-platform probe connections. That makes inventory and firewall checks part of the upgrade plan: an unmigrated probe stops sending monitoring data to the PRTG core server.

Two releases define the migration window
The change is staged across PRTG 126 and PRTG 128. PRTG 126 accepts new multi-platform probes over QUIC only, while existing probes using NATS continue to run. With PRTG 128, NATS connections are no longer supported. Any existing probe that has not been migrated will lose its connection to the core server.
| PRTG version | New multi-platform probes | Existing multi-platform probes |
|---|---|---|
| 126 | QUIC only | Continue to connect through NATS |
| 128 | QUIC only | Disconnected unless migrated to QUIC |
This gives administrators the period between the two releases to move existing probes while they still operate through NATS. The practical first step is to identify every multi-platform probe and note which ones have not yet moved to the 4.x software. PRTG also creates ToDo tickets to flag pending migrations, but teams should account for probes across remote sites and systems in their own upgrade planning.
What the disconnection means for monitoring
After PRTG 128 is installed, an unmigrated NATS probe will no longer connect to the PRTG core server. Its monitoring data will not reach PRTG until the probe is migrated to QUIC. Any dashboards or monitoring workflows that depend on those remote systems will therefore lack incoming data from the affected probes.
Schedule the work before the PRTG 128 upgrade, and check that each remote probe has completed the migration. Treat connectivity as part of the verification: a completed software update alone does not establish the new connection, since the process also requires running the Configuration Wizard and adding its access token in PRTG.
Migration steps and certificate choices
Paessler’s migration process uses multi-platform probe 4.x. Update each existing probe on its remote system, then run the Configuration Wizard there. The update process prints the command to start the wizard. Select QUIC or TCP as the connection type, then configure the certificate authority (CA) option.
- Update the existing multi-platform probe on the remote system to version 4.x.
- Run the Configuration Wizard after the update, using the command printed during the update process.
- Choose QUIC or TCP for the connection type.
- For the CA step, choose “Fetch it from the PRTG server and verify the certificate thumbprint” to use Paessler’s self-signed server certificate. Alternatively, use a certificate from the system store or specify a custom path.
- Copy the probe access token generated by the wizard.
- In PRTG, open Setup | System Administration | Probes and paste the token under Access Tokens in the Multi-Platform Probes section.
The migrated probe does not need to be approved again; the PRTG core server already knows it. Handle the token as part of the connection setup, and confirm it has been entered in the correct PRTG section. For exact commands and additional configuration details, refer to the guide to transferring multi-platform probes from NATS to QUIC and the multi-platform probe manual.
Check port access and the TCP fallback
QUIC uses port 23563/UDP between the probe and the PRTG core server. The TCP fallback uses 23563/TCP. Review external firewalls along that path and make sure the selected connection type is allowed. The PRTG installer removes the old firewall rules for port 23561, which NATS used; that does not, by itself, update external firewalls.
If the network cannot carry QUIC, select the direct TCP connection in the Configuration Wizard. It uses TLS 1.3 encryption and is described as offering comparable security. Teams that used a NATS server to isolate externally facing services in a DMZ should configure a firewall to provide the same separation. If that setup does not meet the environment’s requirements, Paessler directs customers to its support service.
Use the PRTG 126 period to close the gap
The move from NATS to QUIC was described as supporting simpler onboarding, Ed25519-based authentication with TLS 1.3, and better performance for roaming probes on ships or satellite links. Those are the stated reasons for the transition; for administrators, the immediate task is operational: find each NATS-connected probe, migrate it, register its token, and verify network access on port 23563.
PRTG 126 marks the point when new probes must use QUIC. PRTG 128 is the cutoff for existing NATS connections. Use the intervening release cycle to complete migration and check each remote connection before updating to PRTG 128.