PRTG Release Notes:
Preview Channel

We hardened PRTG against open redirect vulnerabilities where URL forwarding to external sites was possible.

We adapted our device templates so that they also contain the new v2 sensor types. Former deprecated sensors that have an according v2 sensor type as successor were removed from the device templates. For example, when you execute an auto-discovery with device template for Server DNS, the DNS v2 sensor will be added afterwards.

The VMware Datastore (SOAP) sensor now includes limits for the channel Free Space by default. The Lower Warning Limit (%) is set to 10 and Lower Error Limit (%) is set to 5. These thresholds are set by default when you create this sensor type new or when you did not have set custom limits before in a previous PRTG version for this sensor. When you have set custom limits before, those settings will be kept when you update to this PRTG version.

The Script v2 sensor now supports native executables. This means that the sensor can now run arbitrary executable files (Linux) or *.exe (Windows). The native executable file should be stored on the probe system. On Linux systems, executables require execute permissions to run. To run Python scripts, this sensor requires that Python 3 is within PATH.

We improved the error message text in the sensor status so you will receive a proper error message instead of a generic one when certain exceptions occur.

We improved our license handling and error messages on the License Information page in PRTG. For example, when you want to change your license and the key is not valid or wrong, you will receive an according error message Activation successful - using previous license key. PRTG will then use the previous key as stated in the message instead.

We improved the wording for sensors that is displayed in the sensor overview popup when you hover over a sensor in the device tree.

Various other minor fixes and improvements, updated user manual.

We updated the German and Spanish language files.

We fixed an issue for geo location information that was displayed in native language for the according country, region or city. The issue occurred because our location service provider updated their API which had impact on the location language. The locations in the Geo Map will be displayed in English again when you update to this PRTG version.

We fixed an issue that occurred when you have set your SMTP server settings to Continue delivery if session is disconnected by client in order to receive email notifications in certain cases. PRTG would cut the connection to the SMTP server before getting any confirmation in those cases. PRTG will now send a >em>QUITverb to the SMTP server before cutting the connection.

• We fixed an issue for the HTTP Transaction sensor that occurred in previous PRTG versions where the sensors went into Down state after updating to PRTG 22.2.77.2204 in certain cases. A possible workaround was to set the Monitoring Engine to use the Compatibility engine mode in order to monitor the URL what helped in certain cases. The issue happened because the HTTP request cookie was not transferred for all following requests in a non compatibility mode. In some cases the HTTP Advanced sensor was also affected by reporting that the connection was refused and it would work again with the Compatibility engine mode.
• We fixed an issue for the HTTP Transaction sensor that occurred when you chose the option Compatibility engine under the option Monitoring Engine section and you set a text value for example ccc in the option Response must not include field in the sensor settings. The sensor then would have displayed a down status with the message URL #1 Warning: RegEx does not match [ccc].

We fixed an issue for LDAP sensors that could not be created via device template in certain cases. The issue occurred when you created a device template for an LDAPS server with accordingly configured sensors before, that is LDAP Specific has to be set to Use LDAP over SSL in the Connection Security. The sensors would be created afterwards but the settings were configured wrongly to use LDAP (Port 389) for unsecure connections.

We fixed an issue for the NetApp SnapMirror v2 sensor that reported the error message The queried field "resnyc_failed_count" is empty in certain cases. The issue occurred, when you monitored a NetApp SnapMirror system that never had a failed resync or update.

We fixed an issue for OPC UA sensors that went into error state in certain cases when you have set the Security Mode in the Credentials for OPC UA of your device settings to None. The issue occurred, because the sensors still used a previously set client certificate although you disabled the Security Mode in the device settings.

We prevented a possible access violation that could happen in rare cases when a probe created too many sensors at once. The fix applies for classic remote probes as well as the Multi-Platform Probe. On Windows systems, the error could be displayed as Invalid access to memory location with error code 998.

The WMI Vital System Data v2 Sensor now offers the counter Memory:Cache Bytes when you add a new sensor under the section Vital System Data Readings Accessible Using WMI.

We fixed an issue that occurred when you had Single Sign-on configured in your PRTG and changed the license key to a Paessler PRTG Enterprise Subscription license type. In those cases, the Single Sign-on login would not work anymore and the Single Sign-On Settings under System Administration would be missing additionally after changing the license type.

The configuration file of this version is not downwards compatible with previous PRTG versions.

With this version we announce the deprecation of the SSH INodes Free sensor, that will be migrated to a successor SSH INodes Free v2 sensor when you update to this PRTG version. SSH INodes Free v1 sensors cannot be added anew when you have updated to this PRTG version. For more information about sensor deprecation and discontinuation, please see our Knowledge Base article:What do deprecation and discontinuation in the context of sensors mean?

With this version we deprecate the Python Script Advanced sensor that we already announced with PRTG version 25.1.104.1946. The Python Script Advanced cannot be added anew when you update to this PRTG version, however, existing sensor types continue to run. Please use the successor sensor Script v2 instead. For more information please see our Knowledge Base article::What do deprecation and discontinuation in the context of sensors mean?

Read here for differences and more information about the two sensors: Why should I use the Script v2 sensor?

We also provide information on how to migrate your scripts with this Knowledge Base article: How can I make my Python scripts work with the Script v2 sensor?

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.2.106.1091

• sha256_exe 6A97F4F49EF8307FEBD0B72FFB3CD4E919F6D68CEBC478EBD0ABED59A93E7FEE
 
• sha256_zip C00C2AA3A941D1BCC92F6A02198A5AAB0FD16946D61297BC503B24E3E612920F

• You can now receive and edit location information with the include parameter set to locationgroup via GET and PATCH request on the devices and group endpoints. To see the location of an object, use the /{id} or list endpoint for a certain object type and make sure to include locationgroup via the include parameter.
• We added the sections /experimental/users/{id} and /experimental/users for GET requests in the api/v2/oas.
• You are now able to create a group via PRTG API v2 and an according POST request on the endpoint /api/v2/experimental/groups/{id}/group and /api/v2/experimental/probes/{id}/group .
• You are now able to edit group settings via PRTG API v2 and an according PATCH request on the endpoint /api/v2/experimental/groups/{id}.
• You can now delete a group or a sensor with a DELETE request in the experimental section /experimental/groups/{id} or /experimental/sensors/{id}. If the request is successful, you will receive a 204 response code.
• We updated the /devices/{id} and /groups/{id} to receive and display information about the status of auto-discoveries. When you execute a GET request on the mentioned endpoints, you will see the additional section about auto-discovery with the fields active, progress and last_autodiscovery, which display whether an auto-discovery is currently running, the progress and when the last auto-discovery ran respectively. Please make sure to set the include parameter first for the section autodiscovery.
• We fixed an issue that occurred when you sent a PATCH request to the /devices/{id} endpoint for the settings group discoverytypegroup and the devicetemplate value was not set. The returned error response code was 400 with the message BAD REQUEST in those cases.
• We fixed an issue for the dbport field in the dbcredentials used for Credentials for Database Management Systems in the device settings. When the default value of that according field was set to 1, for example, the request would fail in the PRTG API v2.

You will now see an indicator bar in your device tree view indicating there is an auto-discovery session running in the device tree. If you have more than one sessions running the indicator bar will display the total number.

We updated the German and Spanish language files.

We fixed an issue where not all of the settings for the probes, groups, and devices were displayed in the previous PRTG version 25.1.104.1841. Specifically, the System Information setting option under the Advanced Network Analysis section was missing for all three objects. In addition for probes, the section Scheduled Restart Settings was not available in the Settings tab.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.1.104.1877

• sha256_exe B060AC1F35630FFD49FC1F5FE1C2D4D57DBE7532A7B6570128B9F603D3834C62
• sha256_zip C0E700E6D54E20CD70C79649D7B6A3E4E3AC69BA514EB5D37FEC562452D58B79

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 25.1.103.1676

• sha256_exe A29A040145DD45E841E59A7C90C4F2A0852A2F29F87FDF676D0DE4410297BCAD
• sha256_zip AED5A3DE819321B77BE4CAA64B55B133751AB99CCF43948B32D51602FEF05C12

You can now define a scale factor as integer or floating-point number for the MQTT Subscribe Custom sensor in the sensor settings during sensor creation. The setting is available in the MQTT Specific settings and can be defined in the Scale Factor setting of a channel when the Channel Unit is set to custom. The default scale value is set to 1 and can be changed depending on whether you want to scale up or down. You can change this setting later after sensor creation in the Edit Channel settings under Scaling Multiplication.

Various other minor fixes and improvements, updated user manual.

The PRTG application server will now be installed by default when you install PRTG for the first time with a valid license key. This change applies only for new installations that do not have a trial key license, existing PRTG version updates are not affected. After you have set up a fresh installation of PRTG, you will see the Open new UI button on the login page. Additionally, the PRTG application server service is available and running on your system.

For more information, please see our Knowledge Base article: I want to use the new UI and API v2. What do I need to know?

We fixed an issue that occurred in the CoreActivation logfile when you used a trial license key for a PRTG offline activation. The activation was successful, however, the CoreActivation log would show an error unknown license selector passed. The issue was due to our internal license processing and did not have any functional impact.

We fixed an issue for the MQTT Round Trip sensor that was not added to a device when you used this sensor in a device template and the Port configured was not default 1883. For example, when you changed the default Port of a device in the Credentials for MQTT to secure connection Port 8883 and ran Run Auto-Discovery with Template with MQTT Round Trip selected, no sensors would be created afterwards.

You can now generate a Historic Data report when you click on the arrow button behind the Start button that is displayed in the Historic Data tab for Historic Data Report Settings. In previous PRTG versions, the report could not be created and instead an error message was displayed: PRTG Network Monitor has encountered a problem. Your last request could not be processed properly.

With this PRTG version we announce the deprecation of the Python Script Advanced sensor as of PRTG version 25.x.106. You will receive a corresponding PRTG to do ticket when you update to this PRTG version and when you have added the Python Script Advanced sensor to your PRTG installation. The Python Script Advanced sensor will be deprecated and cannot be added anew as of PRTG 25.x.106. Please use the successor sensor Script v2 instead. For more information please see our Knowledge Base article: What do deprecation and discontinuation in the context of sensors mean?

Read here for differences and more information about the two sensors: Why should I use the Script v2 sensor?

We also provide information on how to migrate your scripts with this Knowledge Base article: How can I make my Python scripts work with the Script v2 sensor?

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 24.4.103.1665

• sha256_exe 3B54A052BFBDA0FB786D811B68C0810AB4AE1DBE1ECDF7E9EAB305725E7AD1F3
• sha256_zip 174AC1601B26ABB1B0701CABAF1550D22A0BF1A1F24B9C58CD48A197391BCB74

Preview 24.4.103.1638

• sha256_exe E395351A58E0F2CDD0D23B1AEB6D6B63B413ACA606049599F0E83D64AB394CC6
• sha256_zip 42DCCFDBCAC7C1AAED2E5F324EF74C3A31C132366890BFC3A821FD4479921B43

We fixed an issue for the Cisco WLC Access Point Overview sensor that reported the error message The returned result from OID...is the wrong type ('Error'). The expected type is 'Integer (32bit)' in certain cases what resulted in access points not being able to be monitored. The issue occurred in cases when the Number of Slots during sensor creation reported more slots then were actually successful for an access point. For example, the SNMP response during sensor scan reported 2 slots, slot 0 did work whereas slot 1 failed. The sensor will now no longer report an error in these cases but show the data of the successful slots instead. Additionally, you can change the number of slots in the Cisco WLC Access Point Overview Specific settings upon request with the lock button.

• We fixed an issue for the section scheduledependency where maintstart and maintend for Schedules, Dependencies, and Maintenance Window setting where not displayed in UTC (Universal Time). When you executed a GET request on the endpoint api/v2/devices/id you could notice that the maintstart and maintend was displayed in the given timezone of the user set in the PRTG web interface instead of the UTC timestamps used by PRTG core and appserver.
• We fixed an issue for the endpoint devices/id that happened in rare cases when you executed a GET request with the include parameter. The values for id, name and href under _inheritanceSource were empty in these cases. For the value kind type you would receive an error message: unknown_referenced_object_type_for_itemEnumerated.

We fixed an issue for creating objects when the parent (e.g. device, group) was deleted in the meantime. In previous PRTG versions, you would receive an unspecific error message in this case. The error message now displays that the object could not be created: The parent object does not exist. It might have been deleted.

You can now set a different Refresh Interval (Sec.) for a page refresh in PRTG in your Account Settings for PRTG Web Interface. In previous PRTG versions, you were able to save your settings, however, the refresh timer in the page footer was not updated.

We improved the message toast that is displayed when you save settings on pages throughout PRTG in the new UI. The message that is displayed after you have saved your settings successfully will now show Settings have been saved. For Map comments and Report comment setting changes, the message displayed will be Comments have been saved.

We improved the message for new added sensors to a device when there is no data available yet. Previously, when you navigated to the sensor overview page of a new created sensor when no data was available yet, you would see the message No matches could be found. The message now displayed in such cases is No data yet.

The new UI and APIv2 now support the login via Single Sign-on with this PRTG release. When you want to use the PRTG application server, you do not need to specify any new callback URLs on your PRTG instance under Available Callback URLs in the Single Sign-on Settings. However, you need to configure the callback URL within the single sign-on provider for any domain that the appserver is reachable under (Okta or Entra ID). For more information on how to set up SSO, please see our Knowledge Base article: How to integrate Microsoft Entra ID into PRTG? and How to integrate Okta SSO into PRTG?

You are now able to see and access the tabs Log and History in the new UI provided that you have the according user rights for the relevant object. Please note that there is no contex menu available for object links, for example in the Log tab when you right click on a sensor or device.

We updated our API for maptiles and geocoding since the API from the location service provider has changed. In previous PRTG versions you would notice that there was no resolution anymore in some cases for your given geo location in the Location (for Geo Maps) and no map was displayed. This could have affected also new set geo locations while the old API was not working anymore.

Important: Please note that in certain rare cases you will need to take further action to make your geo location map work again. For example, when you have added a location by address in the Location (for Geo Maps) while the old API was not working, you will need to enter a (space, character) again in the location field and the map is displayed correctly when you update to this PRTG version. However, if you have entered the address as coordinates in the map before, no further action is required.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Preview 24.4.102.1344

• sha256_exe 7A1FC4907EBE8DF90020FE3B087361D1A240752EF460CA460E7D15EEC7C65E50
• sha256_zip 23D4F40EF5FD2C2CF02F4459BD509850BBA0137AADF7E8E1DC54A1516DCD75B4