- English
- Deutsch
- Español
- Français
- Italiano
- Português
We fixed an issue where PRTG ran into deadlocks in certain cases as of PRTG 24.1.94.1393, resulting in high CPU load and server crashes and restarts. This issue was more likely to happen if you ran aggregation type sensors, like Sensor Factory sensors, for example.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 24.1.94.1397
We updated the German and Spanish language files.
We fixed an issue where the access of a public map resulted in the error message Map refresh failed when you updated to the previous PRTG preview version 24.1.94.1355. The workaround was to log in with an administrative user account. Public map access will now work again without an active user session when the map is configured for public access.
We fixed an issue where running the PRTG application server caused a higher CPU load on the relevant system in the previous PRTG preview version 24.1.94.1355.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 24.1.94.1393
The behavior of the Environment setting was changed for the EXE/Script and EXE/Script Advanced sensors to prevent remote code execution for Batch (.bat) scripts. Thanks to IT Matters Most GmbH who made us aware of that vulnerability and which can be tracked under CVE-2024-28055. Please note that this change might cause your running custom scripts to fail as it is no longer possible to use the environment variables placeholders in the Parameters setting for Batch (.bat) scripts anymore.
We hardened PRTG against possible Cross-Site Scripting attacks via User Agent in the browser.
We improved the Single Sign-on handling for PRTG user integration in Microsoft Azure AD to support the Microsoft Graph API for paging when a user is assigned to more than 100 groups. Previously, the issue occurred in certain cases that a user with Microsoft Azure AD integration could not log in to PRTG via Single Sign-on when he was assigned to more than 100 groups.
Due to limitations in the Access Token concerning the group memberships we need to switch to Microsoft Graph API for paging what was not yet supported by PRTG. The user would then receive the message that the login has failed. In the Core.log you could also find this error message for the user login: is no member of SSO groups allowed by PRTG.
You can configure the Group Claim Retrieval for Access token or GraphQL in the Single Sign-on settings.
Various other minor fixes and improvements, updated user manual.
You will now be able to save the settings for all your selected sensors when you use the multi-edit function. This did not work properly before in the previous PRTG versions in certain cases. Saving the value Maximum (Mbit/s) for the channel Traffic Total when you have selected several SNMP Traffic sensors would only work for the first sensor in the list, not for all sensors that you selected via multi-edit.
We fixed an issue for notification triggers, that is Speed, Volume and Threshold trigger where added values in the PRTG web UI would not be saved correctly in certain cases. It could happen that after you have entered for example a valid value for bit/second in the Speed trigger under Notification Triggers, that the value was saved afterwards with 0 or even an invalid float value. We also fixed this issue for the PRTG App for desktop.
We fixed an issue where not all probe Settings were displayed in the previous PRTG versions when you installed a new remote probe on your system. When you have added a remote probe successfully and opened the probe Settings tab you could see that, for example, the Credentials for Cisco Meraki were missing.
We fixed an issue where the PRTG Administration Tool could not be opened on a remote probe with a 64-bit operating system in the previous PRTG preview version 24.1.93.1655. You would receive an error message Load of logging dll PaeAdvLog.dll failed with error code: The specified module could not be found in this case. The workaround was to open the PRTG Administration Tool directly from the folder as 32-bit version. The PRTG Administration Tool will now start correctly as 32-bit version when you open it on a remote probe with a system running on 64-bit. Please note that when you update from preview version 24.1.93.1655 to this version, the folder C:\Program Files (x86)\PRTG Network Monitor*\64bit still exists. We will deliver a fix for this issue with upcoming PRTG versions.
We fixed an issue for the Oracle SQL v2 sensor that reported an error The type initializer for OracleInternal.Common.ProviderConfig threw an exception when Oracle Data Access Components (ODAC) was installed on the system where also the sensor was added, e.g. on a remote probe. The sensor then went into an error state in this case because one of the Oracle assembly references did not match.
The Result of Sensor.txt file will now be updated again when you have activated the Store result option for Debug Options in the sensor Settings. Updating the Result of Sensor.txt file did not work anymore in the previous PRTG versions for certain sensor types. This issue affected sensor types like Traceroute Hop Count sensor, Windows Print Queue sensor and Active Directory Replication Errors sensor, for example.
We fixed an issue for the SNMP Memory sensor that reported the error message (value)' is not a valid integer value in certain cases. The issue occurred because certain devices falsely returned counter values instead of integer values for the storage size in the OID 'hrStorageSize' (1.3.6.1.2.1.25.2.3.1.5) what the sensor then could not process correctly.
You can now acknowledge alarms with your read-only user in the PRTG App for Desktop when you have set the according rights for that user in the PRTG web interface before. Previously, when you have created a read-only user in PRTG and afterwards added additional rights Allow user to acknowledge alarms to that user, the settings would not automatically be updated when the user was logged in to the PRTG App for Desktop. As a workaround, you had to restart the Core server or the user had to log in to PRTG App for Desktop again.
We fixed an issue where the execution of an auto-discovery with device template on the PRTG App for Desktop produced an access denied message in the CoreWebServer.log.
You will notice a higher CPU utilization on your system when you run the PRTG application server and when you update to this PRTG preview version 24.1.94.1355. As a workaround, please try to run your PRTG installation without the PRTG application server service. We will provide a fix for this issue in the upcoming PRTG versions.
Public map access reports the error message Map refresh failed when you update to this preview version 24.1.94.1355 and when you open a map that is configured for Allow public access in the map settings. You will have to log in with an administrative user account for an active user session to view a map with public access on this preview version. We are currently working on a fix for this issue.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 24.1.94.1355
With this PRTG version we introduce a new Multi-Platform Probe Connection Health (Autonomous) sensor that will inform you of the NATS server connection with your Multi-Platform probe and is created automatically when you have activated Allow multi-platform probe connections in the Core & Probes settings of your PRTG installation. The sensor comes with the channel NATS Connection state that has the lookup values Disabled, Connected and Disconnected. When you have disabled the setting for Allow multi-platform probe connections the sensor will display an according error message and return the value Disabled.
Please note that the sensor is in BETA status but you do not need to enable the BETA feature in order to get this sensor created. This sensor type only concerns the connection between Probe Adapter and NATS server.
We added the NATS Connection Security toggle in the Multi-Platform Probe Connection Settings to explicitly set the security schema used.
The configuration for connecting the PRTG core server to a NATS server has changed. The schema is now an explicit toggle instead of encoded into the NATS URL. The NATS URL setting was changed to NATS Server Host, which is made up of the hostname and port of the NATS Server. After this update, the NATS Server Host setting will be reset to the default localhost:23561 value and users will need to reconfigure their NATS server.
Important for PRTG Hosted Monitor: This setting is not visible for PRTG Hosted Monitor instances. Customers will be informed separately, as soon as the multi-platform probe can be used with PRTG Hosted Monitor.
Credentials like passwords in the PRTG configuration file are now masked when you use the option Include configuration file (contains passwords) for Send Logs to Paessler in the PRTG Administration Tool in order to send a support bundle. When you have a larger configuration file, e.g. 355 MB and run the PRTG Administration Tool as a 32 bit version, you will receive a message that PRTG was not able to hide encrypted passwords in the configuration file. The same behavior applies when you want to send a support bundle with a broken configuration file. You will then be asked if you still want to include the configuration file containing passwords or not.
Please note that currently is not possible to start the Administration Tool for a Remote Probe running on a 64-bit operating system. As a workaround go to the Program Files (x86) folder, open the PRTG Network Monitor folder, and run the 32-bit version of the Administration tool. We will deliver a fix for this issue in the upcoming PRTG versions.
You will now see a log entry in the History tab of a device when you have enabled or disabled the inheritance of an object. For example, if you enable the Inherit From feature toggle for Credentials for Windows Systems, it will be logged as Credentials for Windows Systems: Inherited in the History tab of the device.
Various other minor fixes and improvements, updated user manual.
We updated the Spanish language files for certain selected sensor types.
We changed Bytes (File) to Bytes (Disk) in the Channel Unit Configuration of the VMware Datastore (SOAP) sensor to better match the size of datastores. Please note that this change will come into effect only when you add this sensor type as new and does not affect any existing sensors.
We fixed an issue for the HTTP transaction sensor that could not access a target URL anymore in certain cases and reported the error message String not found in the previous PRTG version, or when you changed to Compatibility engine in the sensor settings the error message was Object reference not set to an instance of an object.
We fixed an issue that could cause a higher memory consumption especially on the Multi-Platform Probe when you ran MQTT sensors and OPC UA sensors on your system. We therefore also updated our MQTT library to version 1.3.13 what patches several issues.
Your Microsoft Azure SQL Database sensor will now report an according sensor message when the monitored single database or elastic pool is in a different state then Online or Ready. Previously, the sensor reported an error message The queried field "average,count,maximum,minimum,total" is empty. when, for example, the queried database was in status Paused.
The QoS (Quality of Service) One Way sensor now no longer displays any IP address in the Quality of Service Measurement section for Target Probe when you are about to create this sensor type. Previously, the sensor displayed 127.0.0.1 for the local probe what did not reflect the actual probe ID being used.
We fixed an issue where in certain cases the message reported by the sensor suddenly displayed only OK after some time. In these cases the message of the sensor was reverted from the original to OK when the message sent from Probe to Core contained an empty string for some reason. The issue occurred for sensor types like WMI Custom String sensor, SNMP Custom String sensor and REST Custom v2 sensor.
We fixed an issue that occurred for certain sensor types, like the SNMP Custom v2 sensor, where an additional text overlapping the help box was displayed in the section for Schedules, Dependencies and Maintenance Window. Additionally the default dates for Maintenance Begins and Maintenance Ends were not displayed correctly.
We fixed an issue for the SNMP HPE ProLiant Physical Disk Sensor that reported an error Disk: Required field, not defined when you added multiple disks where at least one disk was defective, e.g. did not report serial number and model values. As a result, the sensor could not be created and additionally the PRTG configuration file could also no longer be saved. You will now be able to save your PRTG configuration file again even if your SNMP HPE ProLiant Physical Disk sensor includes a defective disk.
We fixed an issue for the Windows Print Queue sensor that did not report the correct sensor message when monitored printers were offline or paused. The sensor wrongly reported the status message up in these cases.
We fixed an issue where in certain cases API calls to PRTG failed with the error Unauthorized although the API token was valid. For example, when you use the API endpoint /api/table.json to reach PRTG with a valid created API key, it could happen that the call resulted in an Unauthorized message.
We fixed an issue for sms notifications that were cut off in the text when you used certain special characters, like for example ampersand &.
You can now use Probe Transfer and Configuration Viewer in the PRTG App for Desktop when you have configured a proxy server under Probe Connection Settings in your PRTG installation. In the previous PRTG versions, the remote probe would not connect to the server if you enabled the Probe Transfer feature and if you had a proxy server configured on your PRTG installation. The beta feature Template Transfer for custom device templates from one PRTG server to another will now work as well with a configured proxy server.
We fixed an issue for Paessler PRTG Hosted Monitor where you could not change the Inherit From option for Access Rights when you right clicked on a probe in order to edit access rights from the menu. Instead of the Inherit From option you would see the message You need full access rights to view or edit access rights for this object. although you were logged in with a user that has administrative rights.
We fixed an issue for the Find Duplicates feature on /api/findduplicates.htm. Previously, if you selected the option Find Duplicates from the device Context menu the result you would have received was empty.
With this version we discontinue the below already deprecated sensors:
If you run any of these sensor types they will show an error message This sensor type was removed from PRTG. For more information, see https://kb.paessler.com/en/topic/68227. (code:PE258), when you update your PRTG installations to version 24.1.94. You can pause existing sensors afterwards but you will not be able to deploy them anymore.
For further information about sensor deprecation and discontinuation in general as well as successor sensors and sensor alternatives please see our Knowledge Base articles: What do deprecation and discontinuation in the context of sensors mean? and What sensors are deprecated and what are their successors or alternatives?
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 24.1.93.1655
You will now need to configure the probe adapter connection to the NATS server through the PRTG web interface. You can set up your probe adapter configuration in the Core & Probes tab of the System Administration in the Multi-Platform Probe Connection Settings section. In this section you can choose the Multi-Platform Probe Connections, add a NATS Server URL, NATS Server Name, NATS Password, choose the NATS Server Certificate Authority Handling and finally choose the Connection Log Level where you can define the log severity level to determine which logs appear in the probe adapter log file. For this field you can choose one of the options offered from a dropdown menu: Error, Warning, Info (default), Debug, Trace.
We fixed an issue for the PRTG application server that ran into panic mode when you ran a mini probe on your PRTG installation, for example a Python Mini Probe or a PRTG Mobile Probe for Android. The created panic log would display the error panic: runtime error: invalid memory address or nil pointer dereference in these cases.
You can now configure and manage your Credentials for Windows Systems in the device settings in the new UI and also via API v2. This enables you to use sensors on your device which require windows authentication, like WMI sensors. The available fields are Domain or Computer Name, User Name and Password. You can also see and manage the Inherit From toggle and enable or disable it. The windows credentials will also be visible in the new UI when you set them via APIv2 PATCH request on the endpoint /api/v2/devices/{id}. Additionally you are now able to edit the following device settings in the new UI and APIv2: Credentials for VMware/XenServer, Credentials for AWS, Credentials for Script Sensors, Advanced Network Analysis.
We improved the navigation in the mobile view for the new UI. When you click on the menu icon it opens a drawer from the left hand side. The drawer remains open during navigation and you can close it with the x button. Additionally, when you select home in the side bar, you will see links to the sections Welcome and Quickstart.
We updated the German and Spanish languages files.
We fixed an issue where the messages for the Syslog Receiver sensor and the SNMP Trap Receiver sensor were not displayed in the Messages and Sensor Overview tab after updating to the previous PRTG Preview version 24.1.92.1496.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 24.1.92.1545