PRTG Network Monitor

Release notes
for the "stable" release channel

Software versions in this channel are updated about once a month. In this most conservative channel you receive the best tested versions. We recommend that you use PRTG's stable versions for live environments.

Please use the "Auto-Update" feature to update your PRTG installation: In the PRTG web interface, simply navigate to Setup | Auto Update. You can also obtain the latest version from the PRTG download page! 

Download PRTG · Manual: "Software Auto-Update" · Previous Versions and other Release Channels

calendar

March 1st 2023 – Version 23.1.82.2175


Fixed

Server


PRTG core server

 We fixed an issue with cloning and moving devices that lead to deadlocks of the PRTG server in certain cases as of PRTG 22.4.81, resulting in high CPU load and server crashes and restarts.

Fixed

Sensors


HPE 3PAR sensors

 The sensor types HPE 3PAR Virtual Volume, HPE 3PAR Drive Enclosure, and HPE 3PAR Common Provisioning Group work again. The sensors showed a down status with the error message 415 Unsupported Media Type after updating to the last PRTG version 23.1.82.2074 due to an issue with HTTP POST requests via REST API. This also affected the experimental REST Custom v2 (BETA) sensor.

HTTP push sensors

 HTTP push sensors work with HTTPS again. The sensors remained in unknown status after updating to the last PRTG version 23.1.82.2074 with HTTPS enabled in the sensor TLS settings and did not receive any answers for your sensor requests in this case. Affected sensor types were HTTP Push Data, HTTP Push Data Advanced, HTTP Push Count, and HTTP IoT Push Data Advanced. 

Fixed

Notifications


Notification delivery

 PRTG successfully sends your email notifications again when you use SMTP servers with specific TLS configurations as SMTP relay server, for example Microsoft Office 365. In PRTG version 23.1.82.2074, email notifications did not work with certain servers and showed, for example, the error message Error sending "Email": Connection to SMTP relay server "outlook.office365.com" failed in the logs due to an issue with TLS connections. 

Fixed

Licenses


License name

 You can activate licenses again when the license name contains an ampersand (&) character. The activation of the license failed with the message License name and key do not match activation file. in the last PRTG version 23.1.82.2074 due to an issue with encoding.

Note

Known Issues


Notifications

 The subject of email notifications is not correctly displayed in the current PRTG version if it contains special characters like diacritics or umlauts. If you primarily use special characters or Asian and Cyrillic characters in your email notifications, we recommend that you do not update your PRTG installation to version 23.1.82. We will deliver a fix for this issue with an upcoming PRTG version.

Reports

 With PRTG version 23.x.82, reports currently cannot be opened correctly for the option Create and store PDF and data files and Create and store PDF and data files and send them by email when you are logged in to PRTG via Single Sign-On. The opened page shows the message Unauthorized instead of the report data. As a workaround, please use an internal non Single Sign-On user account to view PDF file reports.

Windows MSMQ Queue Length

 In certain configurations, the Windows MSMQ Queue Length sensor reports an error with the message Queuename not found on specified machine. The error may come up during authentication on the target device. We are investigating the cause of this issue.

calendar

February 8th 2023 - Version 23.1.82.2074


Blog article

Michael Becker By Michael Becker • Mar 1, 2023

All about the new PRTG release version 23.1.82

All about the new PRTG release version 23.1.82
i Please note Version 23.1.82.2175 includes fixes for the HPE 3PAR and HTTP push sensors, as well as fixes for the delivery of notifications. Take a look here to get all the details. The latest...
Read the complete blog post here



Improved

Sensors


OPC UA sensors

 The OPC UA Certificate, OPC UA Custom and OPC UA Server Status sensor types now support insecure connections to your OPC UA server with username and password authentication. Note that if you use this configuration, your data including passwords will be transmitted unencrypted.

Thank you for your feedback that the ability to monitor devices with such configurations is needed in several use cases.

Improved

Security


Sensors

 Additionally to the Exchange PowerShell, Citrix and EXE sensors in Paessler PRTG version 22.3.79, we also improved the method of password transmission for the following sensor types:

  • Active Directory Replication Errors sensor
  • FTP Server File Count sensor
  • HTTP XML/REST Value sensor
  • IP on DNS Blacklist sensor
  • Ping Jitter sensor
  • Traceroute Hop Count sensor
  • Windows Print Queue sensor
  • Windows MSMQ Queue Length sensor
  • WSUS Statistics sensor


Previously, passwords were sent in clear text. Now they are encrypted, so they are no longer visible in the Windows Event Log or Task Manager.

Vulnerability

 We fixed a vulnerability that affected certain exe sensors. We thank the reporter who brought this vulnerability to our attention.

Updates

 PRTG now uses HTTPS by default when downloading new software versions for the PRTG auto-update.

Fixed

Sensors


SMTP&POP3 Round Trip

 We fixed an issue with the SMTP&POP3 Round Trip sensor that did not report an error if no email was found in the relevant mailbox. The issue was caused by the sensor matching any email on the mail server.

SSL Certificate

 The SSL Certificate sensor works with a Virtual Host (SNI Name) again even if the SNI name does not contain a dot (.). In previous versions, the sensor showed a down status with the error message Connection reset by peer (socket error # 10054) if the SNI name had no dot. For example, the sensor still worked as expected with example.com but not with example as SNI name. Additionally, the SSL Certificate sensor now supports domains that contain an umlaut (like ü or ä) in the name.

Fixed

Server


Access rights

 Read-only users can change their password by themselves again if the PRTG System Administrator enables the option Allow user to change the account password in their user account settings.

PRTG Core Server

 We fixed an issue where in some cases certain licensee names caused the service for the PRTG core server to stop. The issue occurred during the license activation process.

Remote probes

 The automatic update of a large number of remote probes to the latest PRTG version properly works again. In previous versions, remote probes required a manual update after 20 automatically updated remote probes.

Fixed

WebGUI


Tutorials

 You can now watch again the PRTG Tutorial: Creating Maps on the PRTG Welcome page. The link did not work anymore in the previous versions.

Note

Installer


Security

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

Preview 23.1.82.2026
  • sha256_exe B5A8A06EF616F023E6EFCE31031036ACDB08EC128BAEF5143DD16F36E18DFEE2
  • sha256_zip F04C82387B012049633C48CDAAA369A7368D58C3B6CA3B36B654CF79F5F41683


Stable 23.1.82.2074
  • sha256_exe 0ACD4ABDE0AA527E417E22148ABE1818639064B06D9D8E48F4281B945AA69710
  • sha256_zip F2F262AB9F98919C290B8159BDE1CAF8D1D2377562CC8A692B3E4345E11D0CAF

Note

PRTG API v2, New UI


Stability

 The new UI is now stable enough to be activated on production systems. Previously, we recommended that you activate the new UI only in test environments. When you activate it, you can use it side-by-side with the classic UI.

Please note that the new UI and PRTG API v2 are still in an ongoing development process and that several features are missing.

For further information about features, requirements and known issues for PRTG API v2 and the new UI please see our Knowledge Base article: I want to use the new UI and API v2. What do I need to know?

Lab

Sensors


HTTP v2
  • We fixed an issue in the multi-edit menu that caused an error in the required fields validation for the post body. As a result, the Post Body field is no longer marked as a required field when you select POST as Request Method.
  • We fixed an issue with the timeout setting in the HTTP v2 sensor. Previously, the sensor did not report an error even if the requested HTTP page did not respond within a certain limit of time.

Ping v2

 The Response Time channel is now set as the primary channel for the Ping v2 sensor if you created the sensor with Inverted Error Status disabled and multiple pings. The sensor still shows the Status channel as the primary channel if you enabled the Inverted Error Status feature when creating the sensor.

Script v2

 You can try out the experimental Script v2 sensor that also works on the Multi-Platform Probe. The sensor executes a Python script that returns data in JSON format and shows the exit code. This way you can create your own custom script sensors that may not be available in PRTG by default.

For available example scripts and how to use them, please see the Knowledge Base article: https://kb.paessler.com/en/topic/91349

Lab

New UI


Controls
  • You can now change the basic settings of a device in the Basic Device Settings section. The basic settings of a device include Status, IPv4 Address/DNS Name, IP Version, Device Name and Priority.
  • You can now resume acknowledged alarms for sensors using the Clear Acknowledged Alarm button via the context menu and bulk edit change.

Mobile View

 The mobile view now shows channels with unknown lookup states.

Channels

 We fixed an issue in the sensor graphs section to avoid the risk of possible cross-site scripting (XSS) attacks.

Security

 We fixed an issue for sensor channel values that were sometimes displayed in too large numbers.

Web Interface
  • You can now share the graphs page with a URL link.
  • You can now see the specific scanning times of a sensor if you have defined them as described in https://https://kb.paessler.com/en/topic/3723. In this case, the scanning interval is named Irregular and shows the scanning times in a tooltip.
  • We implemented live graphs for channels that show a down or warning status on the sensor and device overview cards.
  • We fixed an issue on the sensor graphs page that caused a reset after an automatic refresh if you interacted with the graphs, such as zooming in.
  • You can open graphs in a dedicated, larger view.
  • We have updated the content of the PRTG Welcome page to reflect the new features available.

Lab

PRTG API v2


Devices
  • You can now delete a device with a DELETE request in the experimental section /experimental/devices/{id}. If the request was successful, you will get a 204 response code in return.

    Note: You can only delete devices, not probes or groups, for example.
  • You can now edit the settings of a device by sending a PATCH request to /experimental/devices/ {id}. Please note that this feature is still in experimental status and does not contain all functionalities yet.

Sensors

 We fixed an issue in the experimental section for the settings endpoints /experimental/sensors/ID/settings and /experimental/devices/ID/settings. The settings were returned empty after you created a device or sensor.

Channels

 We renamed the scale field in the payload of channels to scaling and improved the description.

Web Interface

 We fixed an issue for sensor channel values that were sometimes displayed in too large numbers.

Improved

Various


All parts of PRTG

 Various other minor fixes and improvements.

Languages

 We updated the German and Spanish language files.

calendar

November 29th 2022 - Version 22.4.81.1532


Blog article

Michael Becker By Michael Becker • Dec 14, 2022

New release, new sensors! PRTG version 22.4.81 is available.

New release, new sensors! PRTG version 22.4.81 is available.
Paessler PRTG 22.4.81.1532 is now available in the stable release channel and comes with the experimental Ping v2 sensor, the experimental HTTP v2 sensor, a security update, and an update...
Read the complete blog post here



Fixed

Sensors


FTP sensors

 We fixed an issue for FTP sensors that in some cases displayed the error message Start SSL negotiation command failed. (SSL/TLS not available). The issue occurred in cases when a connection with a TLS-only port was established.

HPE 3PAR Drive Enclosure

 We fixed an issue for the HPE 3PAR Drive Enclosure sensor that in some cases showed an error during the sensor creation process. The error message displayed was The queried field 'FormFactor' is empty.

HTTP Push Data

 We fixed an issue for the HTTP Push Data sensor that showed an access violation error with the message Failed to handle request. Sensors that were affected are HTTP Push Data sensor, HTTP Push Data Advanced Sensor and HTTP IoT Push Data Advanced sensor. The issue occurred in cases when you used the port 5051 for HTTPS connection with TLS.

MQTT Subscribe Custom

 We fixed an issue for the MQTT Subscribe Custom sensor that returned the error message The received JSON data could not be parsed. This happened in cases when the JSON string could not be parsed completely due to additional characters.

Zoom Service Status

 The channels of your Zoom Service Status sensors will now be displayed correctly again. Regions have been introduced by Zoom recently and components have the same naming as regions, that is why channels in the Zoom Service Status sensor were displayed multiple times in the previous PRTG version.
To monitor the Zoom groups and components you have to add the Zoom Service Status sensor again. You will also receive a to do ticket for this sensor type with further information.

Fixed

Server


CPU usage

 We fixed an issue that occurred with Paessler PRTG version 22.4.80.1553 for denied remote probes that caused high CPU usage in the core server of PRTG. If you had IP addresses of remote probes in the Deny IP Addresses filter under Core & Probes this would lead to an increase in the CPU load as the issue was in the communication for disconnected connections to the core server of PRTG.

PRTG Administration Tool

 You can now send logfiles to Paessler again from the PRTG Administration Tool in the tab Logs and Info via button Send Logs to Paessler.

Security

 We fixed an issue in the tag handling system regarding tag parameters to avoid the risk of a possible Cross Site Scripting (XSS) attack.

Note

Installer


Security

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

Preview 22.4.81.1504
  • sha256_exe 28F05875EA31067881B2E04B3557F1BBC3D174D2064CCBA3E93BD4F1EC2E7839
  • sha256_zip A82725C7C7BBA8E116F31030857BD3DE099FF5B7C40248E04A1DB425A617318E


Stable 22.4.81.1532
  • sha256_exe 0DD1952B8EE8A56F77FBA968366794BFA58ABEFC38151192D378EAF35607091F
  • sha256_zip 64F4918CE265ED58EC98996516D59AA97BB7BBC614AAD644E2F90C9DAB22F106

Note

Sensors


Discontinued Sensors with PRTG 22.4.81

 With PRTG version 22.4.81 we discontinue the following sensor types: Dropbox sensor, Google Drive sensor, Google Analytics sensor, Microsoft OneDrive sensor. These sensor types were announced as deprecated with PRTG version 22.3.78.1873. If you run any of these sensor types they will show a down status when you update your PRTG installations to version 22.4.81. 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?

Note: We also announced the deprecation for the Amazon CloudWatch sensors with PRTG 22.3.78.1873 and that they will be discontinued with PRTG 22.4.81. However, since these sensor types still have a high utilization rate we will postpone their discontinuation until further notice.

Lab

Sensors


HTTP v2

 You can try out the experimental HTTP v2 (BETA) sensor that we introduce with this PRTG version. This sensor allows you to send a HTTP request (HEAD, GET or POST) and use placeholders, similar to the REST Custom v2 sensor.

Ping v2

 You can try out the experimental Ping v2 (BETA) sensor that we introduce with this PRTG version. This sensor keeps the basic ping settings to send one single ping or send multiple ping requests and comes with a new setting Inverted Error Status. If you select Enable for this new setting, the sensor shows a Down status if the target device is reachable.

Note: This setting is currently only available during sensor creation, however, you can change the relevant lookup in the reachable channel afterwards to disable the Inverted Error Status.

Multi-Platform Probe: Both HTTP v2 sensor and Ping v2 sensor work with the multi-platform probe that we first mentioned in the PRTG 21.4.73.1656 release notes when the multi-platform probe started its initial alpha phase. For more information please see our Knowledge Base article: https://kb.paessler.com/en/topic/90140

Lab

New UI


Sensors
  • The sensor information on the sensor overview page now displays placeholders while the object information is loading.
  • We fixed an issue for the Filter by keywords search option on the sensor list.

Channels
  • The primary channel of a sensor now has a pin icon indicator in the card for sensor channels.
  • We fixed an issue for primary channels that caused an unknown error. The issue occurred only when the primary channel of the sensor had not yet received any data.

Web Interface
  • We implemented a new subpage for sensors that shows all limit channels in interactive line graphs. You can select a timespan for the graphs from predefined options: live, short, medium, long.
  • We added time ranges to the timeseries interval picker that is available in the Graphs tab of a sensor.
  • We fixed an issue where deleting objects, likes sensors, devices and groups, led to an unknown error.
  • You will now receive a proper message for objects like sensors, devices and groups when they are moved to a paused status.

Lab

New API


API
  • We fixed an issue for sensor channels with lookup values that were not correctly formatted. The values are now displayed as percentages. The issue occurred in the /api/v2/experimental/timeseries/{id}/{type} endpoint.
  • We fixed an issue for new created devices in the experimental settings endpoints /experimental/devices/ID/settings and /experimental/sensors/ID/settings that led to a 404 not found error when you performed a get request.
  • You can now get information about settings and structure of a device with the GET endpoint /api/v2/experimental/devices/{id}/settings that we first introduced with PRTG 22.4.80.1553 for the experimental section.

PRTG application server

 We improved stability and performance of the PRTG application server.

Improved

Various


All parts of PRTG

 Various other minor fixes and improvements, updated user manual.

Languages

 We updated the German and Spanish language files.

calendar

November 7th 2022 – Version 22.4.80.1553


Blog article

Michael Becker By Michael Becker • Nov 21, 2022

New PRTG release! Two new sensors and an update for all language files.

New PRTG release! Two new sensors and an update for all language files.
PRTG 22.4.80.1553 is now available in the stable release channel! This version comes with the experimental NetApp SnapMirror v2 sensor, the experimental Port v2 sensor, and an update for all...
Read the complete blog post here



Improved

Security


Installer

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

Stable 22.4.80.1553
  • sha256_exe D02BE6A5A28ACE2C0EDF905BAFBC54542F5EF067206CE2FBF92E1472E4D6E338
  • sha256_zip A2DE8530143F750AEE1429CFF71D408CC9155E01E9E4E6667D9C77F081A6DEC1


Preview 22.3.80.1498
  • sha256_exe 12092FA3FC6DEDE54B246CFC9C445328862B21E04A3A63B1D79888AC71A37911
  • sha256_zip D985BCFD406B498C0D35FB0F2172738A34CCD6C63F5679AF015B85668D201F50


They will be documented in the release notes also for future versions. These hashvalues confirm the integrity of the PRTG installer and that it originates from a trusted source.

Improved

Sensors


Microsoft 365 Service Status Advanced

 We improved the filtering process of issues from the Graph API for the Microsoft 365 Service Status Advanced sensor.

Fixed

Sensors


Redfish Power Supply

 Your Redfish Power Supply sensors now handle null values correctly and work again as expected. In some cases, the sensor failed with the following error message displayed in the Result of Sensor Log: The queried field Status.Health has an unknown value: The following reverse lookup value is invalid: . Valid reverse lookup values are: Critical, OK, Offline, Warning.

Veeam Backup Job Status

 We fixed an issue for the Veeam Backup Job Status sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized due to a missing slash sign in the /api/sessionMngr/? API call.

Changed

Sensors


Cloud HTTP sensor, Cloud Ping sensor

 With PRTG version 22.3.80 we discontinue the Cloud HTTP sensors and Cloud Ping sensors, for which you received a to do ticket for with PRTG 22.3.78.1873. If you run Cloud HTTP sensors and Cloud Ping sensors on your PRTG installation they will be paused automatically to preserve the sensor history. These sensor types will be replaced with their successor versions Cloud HTTP v2 sensor and Cloud Ping v2 sensor when updating to PRTG version 22.4.80. Please also see our Knowledge Base article about the migration of the Cloud sensors: https://kb.paessler.com/en/topic/91091

Lab

Sensors


NetApp System Health v2

 We fixed an issue for the NetApp System Health v2 sensor (BETA) that in some cases displayed the error message The following reverse lookup value is invalid: multi_path_ha. The issue was caused by a missing status in the relevant lookup file.

NetApp v2 sensors
  • For the NetApp LIF v2 (BETA) sensor we fixed an issue in the Throughput Read, Throughput Total and Throughput Write channel settings that are now configured as counter channels, as well as the NetApp NIC v2 (BETA) sensor channels Link Down Count, Receive Errors and Transmit Errors where you can now also set limits.
  • With this version comes the experimental NetApp SnapMirror v2 sensor (BETA) that we introduce additionally to the already released experimental NetApp v2 sensors (BETA) in PRTG 22.3.79.2108. The sensor supports the new ONTAP REST API as of ONTAP 9.6

Port v2

 You can try out the experimental Port v2 sensor (BETA) that combines the features of the Port sensor and Port Range sensor. The sensor comes with the channels Maximum Connect Time, Open Ports, Closed Ports and Errors and will send you alerts depending on your settings about open or closed ports.

Note: If you use a larger port range in the Port List of the sensor Settings, the sensor may remain in the unknown status for an uncertain period of time since it performs a scan for each port. To avoid this condition, please increase the Scanning Interval of the sensor.

Lab

New UI


Sensors
  • You can now switch between the channels of a sensor via dropdown menu in the channel detail dialog.
  • We added an overview tab with channel cards to the sensor view.

Lab

New API


API
  • The experimental section now includes a GET endpoint for the settings of a device /api/v2/experimental/devices/{id}/settings. This endpoint is still under development and does not include all features yet.
  • We fixed an issue where cloned groups with added devices and sensors did not show the correct path for the sensor channels.
  • We fixed an issue in the /experimental/timeseries/{id}/live endpoint that in some cases wrongly displayed gaps in graphs for precalculated data.
  • We fixed an issue for the channel ID filter where you could not search for comma separated IDs with the endpoint /experimental/timeseries/{id}/{type}.

API Keys

 You can now use API keys, that you can generate in the PRTG web interface under My Account in the Setup menu in the API keys tab, for the new API. With the API key you can authenticate yourself in the new API without implementing login credentials in a script or integration. The API keys can also be used once for endpoints in the Swagger UI for each Swagger session and they will be sent automatically afterwards with each request.

Documentation

 We improved the documentation.

PRTG application server

 The application server now handles errors correctly when a webserver cannot be created.

Note

Sensors


Discontinued Sensors with PRTG 22.x.81

 With this version we inform you again about the deprecation of the following sensor types, for which you will receive a to do ticket for: Google Drive sensor, Microsoft OneDrive sensor, Dropbox sensor and Google Analytics sensor. Running sensors of these types will still work, but you will not be able to deploy them anymore.

We already announced the deprecation of the mentioned sensor types with PRTG 22.3.78.1873, as well as of Amazon CloudWatch sensor, Cloud HTTP sensor and Cloud Ping sensor. As of PRTG version 22.x.81 that we plan to release in Q4 2022, all these sensor types will be discontinued and stop working.

For further information about sensor deprecation and discontinuation in general please see our Knowledge Base article: https://kb.paessler.com/en/topic/90680

Note

Known Issues


Microsoft 365 Mailbox

 The Microsoft 365 Mailbox sensor currently cannot match emails when you use special (non-ASCII) characters in the filter options Filter by 'subject' with Contains all or Contains any, for example words with accents like "é". This issue is located in the library where URL encoding does not work properly. As a workaround, you can manually URL encode those parts you want to have URL encoded. We will deliver a fix for this issue in the upcoming PRTG versions.

PRTG Administration Tool

 You currently cannot send logfiles from the tab Send Logs to Paessler via PRTG Administration Tool. Sending logfiles results in an error with the message Error connecting with SSL. As a workaround, please use the Contact Support option in the PRTG web interface that can be found in the Setup menu. We will deliver a fix for this issue in the upcoming PRTG versions.

Solved with PRTG 22.4.81.1532

Security

 PRTG is currently affected by a CSS vulnerability with low severity (CVE-2022-35739). For more information please see the Knowledge Base article: https://kb.paessler.com/en/topic/91149

Zoom Service Status

 Some zoom components that belong to regions in the Zoom Service Status sensor will be displayed as channels multiple times. Regions have been introduced by Zoom recently and components have the same naming as regions. The Zoom Service Status sensor is not updated yet to use the Zoom structure for components. We are currently working on a fix for this issue.

Solved with PRTG 22.4.81.1532

Note

Update Notes


Cache recalculation

 The update to this PRTG version will immediately cause a cache recalculation upon starting the PRTG server. While PRTG is usable during the cache recalculation, it will considerably consume more hardware resources like CPU and memory. Depending on your monitoring configuration, you may encounter negative effects on the performance of PRTG during this process. We recommend that you reserve extra time for the PRTG update.

Tree version update

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

Improved

Various


All parts of PRTG

 Various other minor fixes and improvements, updated user manual.

Languages

 We updated and improved all language files.

calendar

September 14th 2022 – Version 22.3.79.2108


Blog article

Michael Becker By Michael Becker • Sep 30, 2022

New release! PRTG version 22.3.79 is available in the stable channel.

New release! PRTG version 22.3.79 is available in the stable channel.
PRTG 22.3.79 is now available in the stable release channel! This version comes with the new Microsoft 365 Mailbox sensor, the new FortiGate System Statistics sensor, an update for OpenSSL...
Read the complete blog post here



New

Sensors


FortiGate System Statistics sensor

 The new FortiGate System Statistics sensor monitors the system health of a Fortinet FortiGate firewall via the Representational State Transfer (REST) application programming interface (API). We released this sensor type as experimental sensor with PRTG version 21.4.73.1656.

Microsoft 365 Mailbox sensor

 The Microsoft 365 Mailbox sensor monitors a Microsoft 365 mailbox. We introduced this sensor type as experimental sensor with PRTG version 22.3.78.1873 and implemented several improvements since then.

  • The filter option in the Microsoft 365 Mailbox Settings is now divided into Contains All and Contains Any to enable a filter for different words in mails. Please note that already created sensors that had the filter option Contains will have the option Contains All after updating to this version.
  • You can now choose different folders in your mailbox to monitor when you add the Microsoft 365 Mailbox sensor.
  • We removed an empty settings field for Microsoft OAuth 2.0 Specific that appeared when you added a Microsoft 365 Mailbox sensor. You can see the following information for the Microsoft OAuth 2.0 specific field when the sensor has been added in the sensor settings: The OAuth 2.0 authorization renew feature is currently under development. If you change OAuth 2.0 settings in Microsoft Azure that require a reauthorization, you must add the sensor anew.
  • On creation of the Microsoft 365 Mailbox sensor you will see a dialogue for the Shared Mailbox User where you can add a mailbox account from a different user.

New

Server


API

 With PRTG version 22.3.79 you can create and manage API Keys for any PRTG User. The API Key can then be used as a parameter in any call instead of the username and password (or passhash) to interact with PRTG's HTTP API. The syntax for using the API Key looks as follows: &apitoken=myapitoken.You can find the new Tab API Keys on the Setup page under Account Settings and under System Administration in the User Accounts settings.

Improved

Sensors


Modbus sensors

 You can now add up to ten Modbus values for the Modbus TCP Custom sensor and Modbus RTU Custom sensor in the Modbus Channel Specific settings to monitor your metrics.

NetFlow sensors

 The sensor types NetFlow v5, NetFlow v9, and their custom variants are now able to listen for UDP packets on IPv6 addresses.

Sensor Security

 We improved the method of password transmission for the Exchange PowerShell, Citrix and EXE sensor types to make them more secure. The transmission happened in cleartext format before and is now encrypted so that the passwords are no longer visible in Windows Event Log or Task Manager. Improved sensor types are as follows:

  • Exchange Backup (PowerShell) sensor
  • Exchange Database (PowerShell) sensor
  • Exchange Database DAG (PowerShell) sensor
  • Exchange Mail Queue (PowerShell) sensor
  • Exchange Mailbox (PowerShell) sensor
  • Exchange Public Folder (PowerShell) sensor
  • Citrix XenServer Host sensor
  • Citrix XenServer Virtual Machine sensor
  • Hyper-V Cluster Shared Volume Disk Free sensor
  • RADIUS v2 sensor
  • SIP Options Ping sensor
  • HTTP Advanced sensor
  • HTTP Transaction sensor

Script sensors

 We added a new section Credentials for Script Sensors for placeholders in the sensor Settings where you can enter your credentials as parameters and which are displayed as masked. The following sensors support the new placeholders %scriptplaceholder1 up to %scriptplaceholder5: EXE/Script sensor, EXE/Script Advanced, SSH Script sensor, SSH Script Advanced sensor, Python Script Advanced sensor. You can use the new placeholders in the parameter field for Command-line Parameters.

Improved

Security


Server

 We updated our OpenSSL libraries to version 1.0.2ze that patches the CVE-2022-1292 vulnerability. The c_rehash script does not properly sanitise shell metacharacters to prevent command injection, where attackers could execute arbitrary commands with the privileges of the script.

Changed

Sensors


EXE/Script sensors

 With PRTG Version 22.3.79 you won't be able to use DLL files as sensors anymore. We removed this feature for EXE/Script sensor and EXE/Script Advanced sensor in the Sensor Settings for the EXE/Script function since it will be deprecated.

Fixed

Sensors


AWS Cost sensor

 The AWS Cost sensor now correctly calculates the forecast values again in the given forecast channels.

Core Health (Autonomous)
  • We improved the stability of the Core Health (Autonomous) sensor. Under certain circumstances, the sensor wrote error messages to the core.log file with each sensor scan.
  • The Core Health (Autonomous) sensor as well as the Application Server Health (Autonomous) sensor show the correct status again when you deactivate the new UI and new API instead of remaining in status Unknown.

FTP sensor

 We fixed an issue for the FTP sensor where in some cases the sensor displayed the error message OK (530 - Login incorrect.) but nevertheless stopped working. You can now use the FTP sensor again even if it cannot log on to the FTP server because of a wrong password. The error message shows that the credentials are incorrect but the sensor remains in the up status.

HTTP sensors
  • We fixed an issue with SNI inheritance affecting HTTP sensors. In previous versions, HTTP sensors showed a down status if the parent device had an IP address as host and the affected sensor was set to Inherit SNI from parent device. The error message in this case was Error connecting with SSL or similar.
  • We improved the compatibility of HTTP sensors with certain web servers. HTTP sensors now only set the content-type application/x-www-form-urlencoded on POST requests because using it with GET requests resulted in a down status in some cases.

HTTP Transaction

 We fixed an issue for the HTTP Transaction sensor where HTTP requests did not work anymore because the sensor created a new Result of Sensor logfile with every scan and exceeded the Windows character limit at some point. The sensor now uses the initial logfile again.

Microsoft Azure Virtual Machine

 Your Microsoft Azure Virtual Machine sensor now displays all existing virtual machines from your Azure environment in the list. The list only showed 50 virtual machines even if there were more available.

NetApp LUN

 We fixed an issue with the NetApp LUN sensor where in certain cases the sensor showed the message error and stopped working due to LUN data that could not be found.

SSL Certificate

 The SSL Certificate sensor now also works when monitoring endpoints that require client authentication. In previous versions, the sensor showed a down status with the error message Error getting certificate information: Not Connected in such cases.

Sensor creation

 PRTG now aborts the scan for available monitoring items and shows a suitable error message in the Add Sensor dialog if the target URL is invalid or the target device does not respond. In previous versions, the meta-scan when adding a sensor never finished and the dialog window got stuck in such cases.

Fixed

Server


Login

 Failed login attempts are now logged again in the WebServer.log. In the previous PRTG versions, the failed login attempts were not listed anymore to comprehend why Overload Protection is active. For more information about Overload Protection please see our Knowledge Base article: https://kb.paessler.com/en/topic/25523

Memory usage

 We fixed several smaller memory leaks on the PRTG server.

Security

 We fixed an issue for SSL passwords in the Core Activation Log that were displayed in a readable format and that are now masked again. The issue only appeared for the Log in Debug Level.

Start-up

 We improved the underlying process of restarting and updating the PRTG server. In previous versions, a check for CSRF tokens could possibly interfere with the server start.

Fixed

WebGUI


Contact Support

 We replaced the old link for our Contact Support options on the pages Help and Support Center and Change License Key in PRTG with the new one redirecting to our Helpdesk portal.

Lab

Sensors


Cisco Meraki sensors

 The experimental sensor types Cisco Meraki License BETA and Cisco Meraki Network Health BETA now include the organization name in the instance name so that you can easily recognize to which organization the Meraki sensor refers to.

FortiGate VPN Overview sensor

 We fixed an issue for the FortiGate VPN Overview sensor where VPN tunnels were shown as down even if the tunnels were up, due to a not linked dial-up entry for the parent link.

NetApp v2 sensors

 You can try out the experimental sensor types NetApp Aggregate v2 (BETA), NetApp LIF v2 (BETA), NetApp NIC v2 (BETA), NetApp Physical Disk v2 (BETA), NetApp I/O v2 (BETA), and NetApp LUN v2 (BETA) that support the new ONTAP REST API as of ONTAP 9.6. We introduce new NetApp sensors based on REST API as with ONTAP 9.6 NetApp delivers a new RESTful API for ONTAP based storage systems.

Note: You must have ONTAP REST API version 9.11 or higher to see two additional channels, Battery State and Storage Configuration, that we introduced with NetApp System Health v2 sensor. You also need ONTAP REST API version 9.11 or higher to create an NetApp I/O v2 sensor.

Lab

New UI


Controls
  • The back button now works as expected again on all pages in the new PRTG web interface.
  • When the Show all sensors view on a Device Overview is selected, the view is now kept when opening a sensor and using the back button to navigate back to the Device Overview.
  • You can now scroll horizontally and vertically on object information cards as expected again.

Errors

 We updated several error messages. They now contain more information about the corresponding objects and details about the failed object actions.

Sensors

 You can now update the acknowledge message and the duration until which a sensor stays in the Down (Acknowledged) status.

Web interface
  • Breadcrumbs are now dynamic and will be truncated if they exceed a certain length.
  • Items in the Device List are now sorted as expected again.
  • The URL of a device tree now reflects the filter status of the device tree to allow users to share specific device tree views.

Web interface
  • We have improved the visibility of the buttons in the filter bar on small screens.
  • We have improved the Reset filter button icon to clarify its function.
  • The new PRTG web interface now displays the correct error page if the PRTG application server is not available.
  • The Overview, Device List, and Sensor List tabs are now in horizontal orientation.
  • You can now see all details about an object on its Object Information page.
  • We updated and improved the layout of object headers.
  • You can now right-click any sensor and select Show Channel Details to see the current measurement, limits, minimum and maximum measurements, and lifetime average or the lookup definition and status of the primary channel of the selected sensor. You can also click any channel on the sensor's Overview tab to open the channel details.

Lab

New API


Documentation

 We improved the documentation.

PRTG application server
  • The results returned by the /settings/public endpoint now contain graph setting data.
  • We fixed a bug that caused an internal error if the ExecutionTimeoutInSecond was set to -1.
  • We moved the /sensors/{id}/settings endpoint from the sensors section to the experimental section. The new URL path is now /experimental /sensors/{id}/settings.
  • We improved the security of the PRTG application server.

Improved

Various


Languages

 We updated the German and Spanish language files.

All parts of PRTG

 Various other minor fixes and improvements, updated user manual.

calendar

August 09 2022 - Version 22.3.78.1873


Blog article

Michael Becker By Michael Becker • Aug 17, 2022

PRTG version 22.3.78 is now available in the stable release channel

PRTG version 22.3.78 is now available in the stable release channel
The latest version of PRTG comes with the new AWS RDS v2 sensor, which leaves beta status and is now fully supported, and the experimental Microsoft 365 Mailbox sensor, which is compatible with...
Read the complete blog post here



New

Sensors


AWS RDS v2 sensor

 The new AWS RDS v2 sensor monitors the performance of an RDS database instance via the AWS API and will be the successor of the Amazon CloudWatch RDS sensor. We released this sensor type as experimental sensor with PRTG 21.3.71.1416.

Improved

Sensors


IMAP & POP3 Roundtrip sensors

 We updated the defaults for Transport-Level Security in the sensor Connectivity settings. The new default port for IMAP sensor and SMTP&IMAP Round Trip sensor will be port 993. For POP3 sensor and SMTP&POP3 Round Trip sensor it will be port 995. These sensor types now use Enforce Transport Level Security as default in the Connectivity settings.

Fixed

Sensors


AWS EC2 v2 sensor

 You can add the AWS EC2 v2 sensor again as expected even if some services in a region cannot be accessed. In rare cases the sensor failed with the error message You are not authorized to perform this operation.

Cloud v2 sensors
  • We fixed an issue for the Cloud HTTP v2 sensor and Cloud Ping v2 sensor that caused the sensors to run into an error with the message The queried field "response_time" is empty.
  • The Cloud HTTP v2 sensor now inherits the Proxy Settings for HTTP Sensors that are given in the parent device.

FTP sensor

 We fixed an issue for the FTP sensor that failed in certain configurations after updating to the last PRTG version 22.2.77.2204. The issue occurred when the sensor tried to connect during the authentication step and therefore the sensor came up with the error message Start SSL negotiation command failed. (SSL/TLS not available).

HTTP Advanced sensor

 You now receive a proper error message for your HTTP and HTTP Advanced sensor when the Proxy server requires credentials in the Proxy Settings for HTTP Sensors.

HTTP Apache sensor

 We fixed an issue where HTTP Apache sensors consumed to much memory, resulting in a memory leak on the PRTG probe system.

Redfish System Health sensor

 You now receive a proper error message for your Redfish System Health sensor when a drive of an according controller does not report back. Before, the sensor only reported that the request had failed.

SSH sensors

 To increase our support for older SSH systems, we extended our list of encrypted algorithms for the SSH sensors. Affected sensors, like the SFTP Secure File Transfer Protocol sensor, ran into an error when, for example, the SSH server for Windows did not support secure algorithms. Your SSH sensors will now work again as expected. You can find a list of supported SSH algorithms here in our Knowledge Base article: https://kb.paessler.com/en/topic/90689.

SNMP Fujitsu System Health v2 sensor

 In certain cases, the SNMP Fujitsu System Health v2 sensor could not be created via auto-discovery device template. Adding the sensor with auto-discovery now works again as expected.

WMI Vital System Data Sensor

 You can add the WMI Vital System Data Sensor again as expected. The sensor now correctly reports Bytes Received and Bytes Sent in the appropriate channels, these values were previously inverted. Only new created sensors were affected by this issue.

Fixed

Server


API
  • You can set the geolocation for your probes again with API call /api/setlonlat.htm.
  • In very rare cases, acknowledged alarms for sensors that exist on a remote probe which is added to a cluster system and which reports to both nodes were not synced to the master node. The issue occurred with api call /api/acknowledgealarm.htm. Your acknowledged alarms will now be synced to the master node if you use the api call for down sensors on a remote probe within a cluster system.

Stability

 We fixed an issue that led to access violations in the Core.log when objects in PRTG were deleted while auto-discovery was running.

Passwords

 We fixed an issue in the CoreWebServer.log that contained readable passwords and passhashes. This occurred only in cases when the login with password or passhash failed.

Changed

Sensors


Common SaaS sensor

 We removed the Common SaaS sensor from the auto-discovery as it will be discontinued in upcoming PRTG releases. The sensor is no longer created during initial and manually triggered auto-discovery.

Python Script Advanced

 PRTG Version 22.2.77.2204 broke compatibility with pip.exe install (to install Python packages). With this PRTG release we have removed support for this command to prevent unexpected errors. As of now the only supported way of installing a Python package to use Python Script Advanced sensor is python.exe -m pip install . Please also see our Knowledge Base article for more information about Python installation: https://kb.paessler.com/en/topic/90686.

Changed

Tree Version


Tree Version Update

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

Lab

Sensors


FortiGate VPN Overview sensor

 We improved the experimental FortiGate VPN Overview sensor concerning data that is received from the FortiGate API.

Microsoft 365 Mailbox sensor

 You can try out the experimental Microsoft 365 Mailbox sensor that we created to be ahead of the deprecation for basic authentication. The Microsoft 365 Mailbox sensor authentication option is based on OAuth2. Microsoft is retiring basic authentication starting in October and IMAP and POP3 including Roundtrip sensors will stop working accordingly. We are looking forward to receive your early feedback for the experimental Microsoft 365 Mailbox sensor that you can send to [email protected].

NetApp

 For the NetApp System Health v2 sensor and NetApp Volume v2 sensor we made the User Name in the settings for Credentials for NetApp visible, it was masked before. Due to this change you need to pause, resume and rescan these NetApp Beta sensors manually to make them work again.

Lab

New UI


Controls

 The refresh timer on the bottom of the new PRTG web interface is now part of the tab index again and can be focused via keyboard navigation as expected.

Device tree

 We have added a new resizable split-screen mode for the device tree.

Device list

 Sorting items by probe name or location now correctly takes empty fields into account again.

Sensors
  • We fixed an issue where objects were not paused and alarms were not acknowledged if the entered message exceeded the maximum message length.
  • We added a validation for the pause message field and acknowledge message field that does not allow messages that exceed the limit of 1,500 characters.
  • You can now pause large numbers of sensors as expected again.

Web interface
  • We have improved the visibility of the buttons in the filter bar on small screens.
  • We have improved the Reset filter button icon to clarify its function.
  • The new PRTG web interface now displays the correct error page if the PRTG application server is not available.
  • The Overview, Device List, and Sensor List tabs are now in horizontal orientation.
  • You can now see all details about an object on its Object Information page.
  • We updated and improved the layout of object headers.
  • You can now right-click any sensor and select Show Channel Details to see the current measurement, limits, minimum and maximum measurements, and lifetime average or the lookup definition and status of the primary channel of the selected sensor. You can also click any channel on the sensor's Overview tab to open the channel details.

Lab

New API


Documentation

 We improved the documentation.

PRTG application server
  • The PRTG application server now returns the correct error response if the duration in the request exceeds the maximum duration.
  • Pending requests no longer prevent the PRTG application server from stopping.

Swagger UI

 We updated Swagger UI to the latest stable version to close a potential XSS vulnerability.

Improved

Various


All parts of PRTG

 Various other minor fixes and improvements, updated German and Spanish language files, updated user manual.

Note

Sensors


Discontinued Sensors with PRTG 22.x.81

 We announce the deprecation of the following sensor types that you will receive a to do ticket for: Amazon CloudWatch sensors, Dropbox sensor, Google Drive sensor, Google Analytics sensor, Microsoft OneDrive sensor, Cloud HTTP sensor, Cloud Ping sensor. We will discontinue these sensor types with PRTG version 22.x.81 that we plan to release in Q4 2022. Running sensors of these types will still work for some more versions, but you will not be able to deploy them anymore. For further information about sensor deprecation and discontinuation in general please see our Knowledge Base article: https://kb.paessler.com/en/topic/90680.

Gitlab Build Status sensor

 With this version we discontinue the already deprecated Gitlab Build Status sensor. The sensor was deprecated with PRTG 21.1.65.1767 and will now no longer provide any data. You will as well receive a notification with further instructions if you run this sensor.

Note

Known Issues


Microsoft 365 Service Status sensor

 Your Microsoft 365 Service Status sensors and Microsoft 365 Service Status Advanced sensors will run into an error with the message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. (code: PE270) when updating to this PRTG version. You need to pause and resume these sensor types to make them work again.

Note

Paessler PRTG Hosted Monitor


Map backgrounds, Device templates

 Your additionally added map backgrounds and device templates are available again on Paessler PRTG hosted monitor installations.

calendar

June 22nd 2022 – Version 22.2.77.2204


Blog article

Michael Becker By Michael Becker • Jul 4, 2022

PRTG release 22.2.77 comes with a new Python distribution

PRTG release 22.2.77 comes with a new Python distribution
PRTG version 22.2.77 is now available in the stable release channel and comes beside a new Python distribution, a security improvement for maps and an update for all language files with many...
Read the complete blog post here



New

ITOps Board 3.5


Elasticsearch Upgrade

 ITOps Board has been updated to use Elasticsearch 7.17.0.

New SLA Report

 This release introduces a new PDF report for SLA availability statistics across multiple business services. The report allows you to view SLA statistics on a weekly or a monthly basis, and contains the following information: Report summary, combined SLA statistics, individual SLA statistics.

Enhancements to Boards

 The Boards page has been enhanced to improve loading time and provide additional page view and filtering options. You can now choose to show a maximum number of boards on the page; you can reduce the page load time by decreasing the number of boards to show. The Filters panel contains the following page view and filtering options: Display Top, Visualize by, Sort by, Display Board States, Health Rollup Types, Exclude Child Boards, Display Boards with.

Improved

Security


Maps

 We added a validation for the image upload in maps that minimizes a potential risk in uploading files with arbitrary content.

Improved

Installer


Command line parameters

 We added the command line parameters /datadir and /snmpCommunityStrg to change the PRTG data path and the SNMP community string at first installation via command line.

Changed

Sensors


Python Script Advanced

 With PRTG version 22.2.77 we deliver a new Python distribution. Python distribution 3.9.12 includes security patches, for example CVE-2021-3177, and several other improvements, as well as we renamed the Python helper library from prtg to paesslerag_prtg_sensor_api.

After installing PRTG version 22.x.77, PRTG creates a ticket that informs you about the Python update. Please make sure your custom Python scripts are compatible with Python version 3.9.12. You only need to consider the change if you are using the Python Script Advanced Sensor.

For more information, see our Knowledge Base article https://kb.paessler.com/en/topic/90484.

Fixed

Sensors


Auto-Discovery

 We fixed an issue that occurred for several newer sensor types during auto-discovery. The sensors could not be added if an additional scan for a scheduled auto-discovery was carried out, however, it worked for the first scan. One affected sensor was, for example, the Veeam Backup Job Status Advanced sensor. The auto-discovery options now work again as expected.

Channels

 Newer sensor types that previously displayed bandwidth measurements in Bytes only now take the configured channel unit configuration for Bytes (Bandwidth) into account. We fixed this behavior for sensor types like Amazon CloudWatch, WMI Logical Disk v2, and WMI Physical Disk v2. Also newer sensor types now include channel unit configuration like AWS EBS v2 and AWS RDS v2, as well as custom sensor types like the EXE/Script Advanced sensor.

HTTP sensors

 We fixed an issue where the option for SNI inheritance did not work correctly for affected sensor types HTTP sensor, HTTP Advanced sensor and HTTP Data Advanced sensor.

Note: If you use the option Inherit SNI from parent device for the mentioned sensor types, you need to enter the IP address as host name in the parent device settings. Otherwise your sensors may run into the error with the message Error connecting with SSL.

Microsoft Azure SQL Database

 The Microsoft Azure SQL Database sensor is now able to monitor databases with umlauts in the name string.

Modbus sensors

 We improved the connection stability of Modbus RTU Custom and Modbus TCP Custom sensors. In certain cases, the Modbus sensors switched between warning and up status and returned an unknown error.

Redfish sensors

 We improved the handling of optional fields in the Redfish System Health sensor and Redfish Virtual Disk (BETA) sensor to avoid an unnecessary warning status. In such cases, the sensors went into a warning status with the message Error: The queried field "Status.State" is empty.

SNMP sensors

 We fixed an issue that occurred in very rare cases when adding SNMP Traffic or other SNMP sensors ran into a timeout. The sensors could not be added successfully. This affected, for example, certain Cisco, Arista, and Fortinet devices.

SSL Security Check

 SSL Security Check sensors now correctly show the message Weak Protocols Available if TLS 1.1 is accepted.

VMware Host Performance (SOAP)

 The VMware Host Performance (SOAP) sensor now correctly displays watt as unit of the Power channel. Previously, the sensor showed a hashtag (#) instead.

Fixed

Server


Configuration

 We fixed an issue for notifications where in rare cases missing lookup files caused the notification delivery for PRTG to stop working.

Notifications

 We fixed an issue for notifications that stopped working in some cases due to unavailable lookups that create a todo ticket.

Reports

 You can now generate PDF reports when you are logged in via single sign-on. This was not supported before.

Lab

Sensors


Cisco Meraki Network Health

 We hardened the process of adding the Cisco Meraki Network Health (BETA) sensor.

PowerShell Security Enhancement

 We improved the experimental PowerShell Security Enhancement feature for EXE/Script sensors that in some cases caused executed scripts to return 0 as a value. As a consequence, custom EXE/Script PowerShell sensors did not work anymore when you enabled the feature.

REST Custom v2
  • The REST Custom v2 (BETA) sensor now supports arrays in the request URL. Previously, the sensor shortened the arrays so that it did not return the desired values.
  • Placeholders in the POST Body setting of the REST Custom v2 sensor now properly work. Previously, the resolution did not work after a first successful sensor scan.

Lab

New UI


Web interface
  • We added a new and revised device overview.
  • We improved the visuals of the device overview.
  • We overhauled the lookup bars, added new styles, and updated their behavior.
  • We added gauges to the device overview that display the channel limits.
  • We improved several features in the device list view.

Device tree

 We added buttons that allow you to collapse and expand the device tree.

Navigation
  • Switching from the sensor overview to the mobile web interface no longer causes unknown errors.
  • The dropdown list that opens when you click a breadcrumb now shows all child objects of the object again.

Controls

 We fixed a bug that caused an unknown error when an object was deleted while it was opened by another user.

Filters
  • Filters set when viewing further sensor results on sensor status cards are now reset again if you use the go back function of your browser.
  • Filters set for a probe now persist when switching between the overview, device list, and sensor list.

Lab

New API


PRTG application server
  • The system startup screen now shows the correct IP address or DNS name when the TCP port for the PRTG web server was changed. In previous version, an incorrect port was displayed when the PRTG application server was running.
  • We improved stability and performance of the PRTG application server.

Improved

Various


Languages

 We updated and improved all language files.

All parts of PRTG

 Various other minor fixes and improvements, updated user manual

Note

Sensors


StartTLS connectivity

 For sensors using the StartTLS option Use transport-level security if available using StartTLS (default) in the Connectivity settings, you have to select Use transport-level security if available or better Enforce transport-level security if they use a TLS only port (which is 993 for IMAP or 995 for POP3). If a setting with StartTLS option is used, on a TLS only port in this case, the sensors now correctly try to connect to the server unencrypted first and may run into a timeout. Affected sensors are, for example, IMAP sensor, POP3 sensor, SMTP&IMAP Roundtrip sensor, SMTP&POP3 Roundtrip sensor.

Note

Known Issues


Access rights

 Read-only users that have the option set for Allow user to change the account password under User Accounts on the Setup page, can currently not change their password in this version. The password needs to be changed by the administrator in these cases.

HTTP Apache sensors

 The sensor types HTTP Apache ModStatus PerfStats and HTTP Apache ModStatus Totals may cause increased memory usage on the probe system in this version. Please increase the scanning interval of HTTP Apache sensors on your probe or reduce the number of running HTTP Apache sensors until the next PRTG version is available if too much memory is consumed.

Previous Versions
and other Release Channels