- English
- Deutsch
- Español
- Français
- Italiano
- Português
We fixed an issue for Single Sign-on where it was not possible to log in with a Single Sign-on user when you updated to the previous PRTG Stable version 26.1.116.1498 and when you had Single Sign-on configured for your PRTG. The login failed and the page no longer worked. The error message too many redirects was displayed in those cases. If necessary, you may need to clear your browser cache and cookies.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 26.1.116.1534
The Cisco WLC Access Point Overview sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 24.3.98.1210. This sensor monitors your access points that are connected to your Cisco Wireless LAN Controller (WLC).
The PRTG Data Hub sensors, that is PRTG Data Hub Process sensor, PRTG Data Hub Traffic sensor and PRTG Data Hub Rule sensor, left their BETA status and are now fully supported with this PRTG version. We introduced those sensor types as experimental sensors with PRTG version 24.3.100.1361 in order to monitor a PRTG Data Hub instance.
The Port v2 sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 22.4.80.1553. This sensor combines the features of the Port sensor and Port Range sensor and monitors a network service by connecting to one or more of its TCP/IP ports.
The SSH INodes Free v2 sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 24.3.100.1361. This sensor monitors the free index nodes on disks of Linux/Unix and macOS systems via Secure Shell (SSH).
We improved the usage of lookups created by PRTG that now implement the necessary syntax to reference the schema. This shows you information about the formatting when you work with lookup files in an editor program. For example, when you check the created lookup in the \PRTG Network Monitor\lookups\custom folder with an editor program after you have added an SNMP Library sensor before, you will now see additional information about the XML schema. This change applies only for newly created lookup files.
Various other minor fixes and improvements, updated user manual.
We fixed an issue that could cause internal nodes to be deleted via API call. Internal nodes required for your PRTG installation can no longer be deleted now via API call.
You can now delete an object only when you have the according access rights to that object, regardless if you have write or full access to the parent node. Previously, there was a check for the access rights only on the parent node. If you do not have write access to all the objects that you want to delete, you will receive an access denied error for this operation.
We improved the behavior of PRTG auto-update concerning the available PRTG versions.
We fixed an issue where in certain cases an enabled Geo Map could lead to ajax timeout errors or slow performance in the PRTG web interface. You could observe this issue when your PRTG core server was blocked in your firewall for outgoing connections and PRTG would try to reach the geolocation service continuously. In the Core.log you could also read an error log entry GetGeoLocation: failed to read geolocation.
We fixed an issue for email Notifications that occurred in certain cases in the previous PRTG version where email notifications were not received although they reported the status Status sending Email: OK in the PRTG system information.
We improved the stability of PRTG local and remote probes that ran into a higher memory consumption in certain cases in the previous PRTG versions. You could observe access violations or exceptions in some cases in the Probe log and that the probe service stopped working due to the high memory consumption. Restarting the probe service only helped temporarily in such cases.
We fixed an issue for remote probes where in certain cases the content in the Log tab was not rendered and therefore the Log tab was displayed as empty.
We fixed an issue for reports where the first line of a report saved in .csv file format displayed the first line in unresolved characters and was not readable. The issue occurred when you have set your PRTG language to Russian, Japanese or Chinese and ran a report including data tables to be saved as .csv file.
You will now be able to log in with your Single-Sign on user account again after you have changed your license key or after server migration. In previous PRTG versions, the user account for a Single-Sign on user was paused after you have transferred to a new license and login was not possible.
We fixed an issue for the HPE3 PAR Drive Enclosure sensor where the drive controller reported an invalid temperature or no temperature at all in certain cases. The sensor will now ignore drives with missing or invalid temperatures instead of going into an error state.
We fixed an issue where in some cases changing settings of certain custom sensor types resulted in a PE270 error with the message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. In cases where pause and resume did not help, a PRTG core server restart would make those sensors run again. Sensor types affected were, for example, Modbus TCP Custom sensor and MQTT Subscribe Custom sensor.
The option Filter by Message in the WMI Event Log sensor settings under Filter Event Log Entries is now working again as expected. When you disabled the Filter by Message option and saved the settings, the log entries would still only be returned for this filter option
We fixed an issue for the Multi-Platform Probe Connection Settings in the PRTG Setup menu that you could not save anymore in certain cases. For example, when you changed the connection settings from Allow multi-platform probe connections to Do not allow multi-platform probe connections (default), the changes would not be applied after a Core restart. You could also observe an error message in the Multi-Platform Probe Connection Health (Autonomous) sensor that displayed Error caused by lookup value 'Disconnected' in channel 'NATS Connection State' although the NATS server was installed and running.
With this PRTG version we inform you about the upcoming sensor migration of the SSH INodes Free sensor to its successor SSH INodes Free v2 sensor in PRTG 25.x.106. You will receive an according To Do ticket in PRTG with this PRTG version when you run SSH INodes Free v1 sensors. This tickets informs you also about upcoming custom device template migration from the existing sensors to the new sensors.
For more information about sensor migration, see the following Knowledge Base article: https://kb.paessler.com/en/topic/91901.
You will notice that PRTG logs several entries for exceptions in the Core.log in certain cases when you change the graph period in the Graph Settings under User Interface in the System Setup. The issue occurred in the previous PRTG version 24.4.102.1351. The log entries with the message Exception: Wrong period in cache appear after the automatic core server restart when you have changed and saved graph settings before. We will deliver a fix for this issue with the upcoming PRTG versions.
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.1841
We improved the performance of the PRTG application server that caused a higher memory usage especially for larger PRTG installations in the previous PRTG versions.
You will now see the message in your acknowledged sensors about who acknowledged it with an according time stamp as well as the error message itself. This information was missing in the previous PRTG versions when you did not enter a text for an acknowledge message.
We fixed an issue for the error page with the message The selected object cannot be used here or it does not exist that is displayed when you, for example, want to clone or delete a not existing report. In this case the mentioned error page is displayed, however, the redirect would link you to the PRTG welcome page. You will now be redirected back to the page you came from, in this case the Reports tab.
We improved the drop down menu for the tab Logs in the PRTG New UI. In previous PRTG versions, you had to scroll down in the menu when you clicked on Choose Filter in order to see the option Status Message Related. The drop down menu has now an extended view to display all options without scrolling.
We improved the objects Detail page when you navigate to the Monitoring overview. Instead of just the content list, you can now scroll through the whole page. The Actions button will stay in place when you scroll through the page.
We fixed an issue where not all channels of sensors that belong to the probe device of a remote probe were displayed in the new UI. This issue occurred in previous PRTG versions after you have approved a new incoming remote probe.
We fixed an issue that occurred, when you clicked on a sensor in the navigation tree under Monitoring. The sensor overview page would open on the right side. When you closed the split view for the sensor overview page and clicked on the same sensor in the tree again, the overview page would not open.
We have set the HTTPOnly and SameSite flag for the cookies created by PRTG to strengthen secure transmissions.
We improved the security handling for API tokens regarding interactive web sessions by restricting access for API tokens to certain endpoints.
Single Sign-on users are now able to create API keys that can be enabled in the Single Sign-on account settings. As a prerequisite, SSO must be configured in PRTG and an SSO group must exist. You can then enable the new feature Enable API Keys for SSO Users in the Single Sign-on user group settings, which is disabled by default. Additionally, this setting includes a field SSO API Key Lifetime (Days) where you can set the days for how long the API key is valid. When SSO API keys expire after the configured lifetime, the relevant API keys will be cleaned up automatically. As a Single Sign-on user, you can use the SSO API keys also for API authentication.
We have implemented a character limit of 240 characters for the Display Name in the User Account Settings. You cannot save changes if the Display Name exceeds the character limit and you will receive an error with the message The display name cannot exceed 240 characters.
Various other minor fixes and improvements, updated user manual.
We updated the German, Spanish and Dutch language files.
We updated the French, Portuguese, Russian, Chinese, Japanese and Dutch language files for certain sensor types.
We fixed an issue where in certain cases activating an incorrect license key for PRTG Subscription licenses led to access violations in the Core.log file.
We fixed an issue where the License Name was cut off in certain cases on the License Status page when you did use special characters, in this case quotation marks ", in the license name.
We fixed an issue for Cloud HTTP v2 sensors that reported the error message The queried field "message" is empty in certain cases. The issue also happened when you monitored different endpoints in various Azure regions.
We improved the error handling for file system sensors, for example, Dell EMC Unity File System v2 sensor, to better map error messages like The specified network name is no longer available.
We removed the deprecated setting Basic256 in the Security Policy section of the Credentials for OPC UA. This setting was deprecated due to the used hash algorithm Sha-1. Please note that your OPC UA sensors will report an error message if you have configured the Basic256 setting and update to this PRTG version.
We fixed an issue for the scaling factor sensor channel setting where you can enter a multiplication or division scaling factor for sensors with custom units. The issue occurred, when you have configured a scaling factor for your sensor and at the same time entered channel limits. After saving the changes, you could observe that the channel limits were either divided or multiplied with the value you have entered as scaling factor.
We fixed an issue for the SNMP Windows Service sensor that occurred in certain cases when you have used this sensor type in a device template. For example, when you have configured a device template with the SNMP Windows Service sensor and have set an include/exclude filter for a certain service and run an auto discovery later on a device to create the sensors. When you delete one of those sensors afterwards and run the device template again, the deleted sensors would not be created.
We fixed a compatibility issue for Veeam Backup Job Status and Veeam Backup Job Status Advanced sensors that did not support Veeam 13 for Veeam Backup Enterprise Manager and Backup Server. The sensors reported an error with the message that the JSONPath is incorrect in previous PRTG versions.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 26.1.116.1487
You can try out the experimental Proxmox VE Virtual Machine Status (BETA) sensor that monitors performance metrics and status of QEMU virtual machines on Proxmox VE clusters. To use this sensor type, please enter the Credentials for Proxmox in the device settings with API token authentication.
You can try out the experimental Proxmox VE Container Status (BETA) sensor that monitors performance metrics and status of LXC containers on Proxmox VE clusters. To use this sensor type, please enter the Credentials for Proxmox in the device settings with API token authentication.
We implemented a new setting for the SNMP Custom String v2 (BETA) sensor in the Specific Sensor Settings, named Interpret Result as. This setting basically converts the result from the SNMP endpoint into a string. You can select String (default), MAC address and IPv4 address for this setting. The sensor message will then show the format of the setting you have selected before, for example for MAC address it will display "01-02-03-04" as server response.
The Custom v2 sensor now supports string-encoded BITS values, for example MAC addresses, that are converted to a numeric format. Parsed BITS values will work with existing channel configurations.
You can try out the experimental SSL/TLS Certificate sensor (BETA) which is the successor to the SSL Certificate sensor and which was rewritten to also work on the Multi-Platform Probe. This sensor type monitors the certificate of a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection. Please note that this sensor does not yet support the Use SOCKS proxy setting.
We fixed an issue for dialogues that disappeared partially behind the resize handler in the split view of the new UI. For example, when you have created a new device, you will receive a pop up dialogue success message object successfully created which could disappear partially behind the resize bars.
You are now able to delete multiple objects in the Sensor list or Device list via bulk edit selection. You will see a confirmation dialogue that asks you if you want to cancel or confirm the deletion of the selected objects. You will receive an according error message if you do not have the necessary rights to delete certain objects.
We updated the German, Spanish and Japanese language files.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 25.4.115.1212
You can try out the experimental SIMATIC S7-300/400 Restart Overview sensor (BETA) that we introduce with this PRTG version. This sensor detects and classifies restart events (cold, warm, hot, planned or unplanned) from legacy Siemens PLCs (Programmable Logic Controller). It helps operations teams understand why and how often a PLC has restarted, which is often critical in diagnosing power losses, software crashes, or watchdog faults. The sensor uses Snap7 and S7 protocol to access the diagnostic buffer of the PLC.
You can try out the experimental SIMATIC S7-300/400 CPU Status sensor (BETA) that we deliver with this PRTG version. This sensor connects to Siemens PLCs (Programmable Logic Controller) using the S7 protocol and reads key diagnostic values like CPU mode (RUN/STOP), OB1 cycle time, cycle load, and recent watchdog events. The data is collected read-only using Snap7 and provides OT teams with remote access to metrics that would otherwise require on-site inspection via TIA Portal.
Various other minor fixes and improvements, updated user manual.
Your DNS v2 sensor now only accepts IP addresses that exactly match the value you configured in the filter. The previous version did not allow exact matching of the results, which could cause false positive results. For example, an IP address matching the filter with one digit more was also accepted.
We fixed an issue for the HPE 3PAR Drive Enclosure sensor that reported an error with the message Invalid response structure encountered, some data is missing. in certain cases. The sensor log also displayed an invalid showcage command. The issue occurred when you used this sensor type for HPE Primera Storage systems.
We fixed an issue for certain HTTP sensors that were missing in the Add sensor list or stopped working in some cases when you updated to a previous PRTG version. This issue has occurred since PRTG version 25.1.104.1946 and affects the following sensors: HTTP Push Data Advanced, HTTP IoT Push Data Advanced and HTTP Data Advanced sensor. In some cases, an error message was logged if you already had HTTP sensors running in PRTG: Could not load "sensor ID: Osk for httppushdataadvanced was not loaded!
We fixed an issue for licenses that could happen when you clicked on the Down sensors on the home page to open the sensors list and tried to delete them via multi edit selection. In this case, you would receive an error object not found for those sensors afterwards. Additionally, you could find errors logged in the Core.log as exceptions. The issue also occurred in PRTG when you have activated it on an offline system.
We fixed an issue in the Core.log and CoreActivationLog which created incorrect log entries when you changed the license key in your PRTG. This issue only occurred if you had previously changed the log level to DEBUG. After you have changed the license key, you could see a warning message in the Core.log processing of activation data failed. Furthermore, the license activation success message, for example Startup: Error during activation of license PPEM: Activation successful was logged as error.
We fixed an issue for public Maps that displayed an error Map refresh failed when you configured an External Link before in the Map Designer and clicked on the corresponding object in the public map. This issue also occurred with any Sunburst map object that you have added to your map. Opening the links to the individual objects would also lead to an error.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
Preview 25.4.115.1167
We have added the Channel Unit Configuration section to the device settings, where you can configure default units for the channel types Bandwidth, Memory, Disk and File via dropdown menu. You can also use the Inherit From toggle for those settings.
We fixed an issue where you could not scroll down in order to see the full message when the sensor reported a down or warning message with a longer text.