PRTG Release Notes:
Preview Channel

We updated the German and Spanish language files.

We fixed an issue for the PRTG installer when you selected to run it in the Custom installation mode. The issue occurred in the previous Preview version 23.2.86.1462 for fresh PRTG installations and when you used the default data path C:\ProgramData\Paessler\PRTG Network Monitor here. In this case you could not proceed on to the next installation step and the PRTG installer reported an error message The Setup program cannot access the selected data path. Check your Windows access rights or select a different directory.

We fixed an issue that resulted in an automatically created new user group when you have added a new user account in the previous Preview version 23.2.86.1462. This user group was also wrongly assigned as Primary Group to the user.

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

Preview 23.3.86.1515

• sha256_exe EAF4365079532BF00E0FEF602F60E6E956A1D58128A6AB09FB5D1EB0E1437C26
• sha256_zip F32CCFE19DC31A8D77DF026223C5763FDBBBE021866C71BA8FBCA8C998D453F6

• We fixed a vulnerability where a PRTG user with write permissions could trick a few sensors into creating possibly executable files on the host system, which could then be executed under certain circumstances.
• We fixed a vulnerability where it was possible to bypass the CSRF protection.
• We fixed a vulnerability where it was possible for a PRTG user with write permissions to trick certain sensors to use sensor specific files from unintended locations on the host system which could lead to arbitrary actions within the capabilities of the sensors.
• We fixed a vulnerability where a target url could be tricked to redirect the user to foreign domains.

We fixed a vulnerability that could enable an authenticated and authorized malicious user to write an arbitrary file on the probe system. The issue affected the exe sensors FTP Server File Count sensor and HTTP XML/REST Value sensor. The vulnerabilities can be tracked under CVE-2023-22631 and CVE-2023-22632.

For further information please also see our Knowledge Base article: https://kb.paessler.com/en/topic/91756

Various other minor fixes and improvements.

The PRTG installer now validates the access to the selected Installation Path and Data Path on PRTG installation in the Custom mode and resets the path to its default when it is not accessible. Previously, the installation displayed a fatal error with the message PRTG Webserver could not be started properly when the installer failed to write into the path due to access restrictions.

We fixed an issue for the HTTP notification type when it contained reserved special characters, such as hash symbols (#), in the placeholders of the URL which you can add in the Execute HTTP Action section. The URL string was cut off after the hash symbol in these cases.

We fixed an issue on group, sensor, device and notifications level that led to several issues in the web interface when you entered an URL as name of the relevant object.

We fixed an issue for the HL7 sensor that went into error status with the message Error caused by lookup value 'No' in channel 'Message Control ID OK' (AE:102 Data type error) after running for a certain period of time. The issue was located in the current date and time of the timestamp.

We fixed an issue that happened within the parsing of the output for the commands executed by the HPE 3PAR drive enclosure sensor. The sensor then reported the error message Invalid response structure encountered, some data is missing for HPE Primera systems in certain cases.

Your HTTP Advanced sensors now can use custom headers again when you have defined them in the setting for Use Custom HTTP Headers of the sensor settings. Previously, the custom headers were ignored and overwritten with a default value. We therefore also fixed an issue with the default HTTP headers where the wrong response format, e.g. XML instead of JSON, was returned in certain cases.

Your NetApp SnapMirror v2 sensor is now able to display a correct status for the channel Transfer Status when the reverse lookup value is insync for Snapmirror continuous protections. Previously, the sensor reported an error with the message The following reverse lookup value is invalid: insync. in this case.

We fixed an issue for the NetFlow v5 sensor where the values for Inbound and Outbound Interface were set to 16 bit instead of 32 bit in certain cases.

• We fixed an issue for the OPC UA Certificate Sensor, OPC UA Custom Sensor and OPC UA Server Status Sensor that went into an error status after one or more scan intervals with the message BadSessionInvalid. The issue happened during session establishment where the session timeout response from the server was not taken into account by the sensor.
• You can now set the connection configuration for OPC UA to SecurityMode = None in the Endpoints tab with additional user name authentication via Username & Password for a user account. This combination did not work previously and the connection to the OPC UA sensors could not be established before.

Your Windows MSMQ Queue Length sensors will now run again when you update to this PRTG version. These sensor types did not work anymore with PRTG version 23.1.82.2175 and reported an error with the message Queuename not found on specified machine in certain cases. The issue occurred on remote systems with a MSMQ service running that could not be queried.

You currently cannot add a library with a user account that has read/write access when you update to this PRTG Preview version. When you are logged in as a read/write user that has full access in the according user group you will get an Unauthorized ajax error message for adding a new library. As a workaround, please use an admin user account instead. We will deliver a fix for this issue in 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 23.2.86.1462

• sha256_exe 909475EFCFA182D71D7166DB6D9C6DB76E92D0C2E751CF2701A6B353F9AD283C
• sha256_zip 5E30416A1EF2271382EAD1FD8D1210DF7C89779CF1B189C1867687A92C82E890

We fixed an issue for the Cisco Meraki License Sensor and Cisco Meraki Network Health Sensor that went into an error status when PRTG was updated to version 23.2.84.1566 with the message The sensor could not get a response from the server. 0 (). schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed).

To make it more clear, we have renamed the setting from Timeout (sec.) to Timeout per Request (sec.) in the HTTP Specific settings of the sensor.

We fixed an issue for the SNMP Uptime v2 sensor that reported the following error in certain cases: Could not resolve OID for 'iso.org.dod.internet.mgmt.mib-2.host.hrSystem.hrSystemUptime.0'. Either the required MIB file was not found or the name is invalid. The issue occurred only when you have added the sensor to a remote probe.

We fixed an issue for the Script v2 sensor where the path to the Script folder was broken. The issue was fixed for the path on Microsoft Windows operating systems.

• We fixed an issue that led to an unknown error when you logged in to PRTG after a logout and when you navigated to Monitoring view via side menu.
• We fixed an issue that resulted in an error message "An unknown error occurred". The error occurred when you expanded the Graphs card of a sensor and then closed it with the x button.
• You can now add channel graphs again via the Add button in the expanded view of the Graphs page of a sensor.
• We activated the Change Password button, which previously prevented you from submitting your request to set a new password.
• You will now see a banner when you activate the new UI that will inform you about the development status. The text message with linked Knowledge Base article is The new interface is still in development and not yet feature complete. Please take a look at our Knowledge Base to see what is coming next.

We fixed an issue for Probe and PRTG application server access keys that were encrypted with Preview version 23.2.85.1310 what led to a corrupted PRTG configuration file in certain cases. The issue occurred only when you had more than one access keys and only when you executed a second core server restart after the update to Preview version 23.2.85.1310.

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

Preview 23.2.85.1327

• sha256_exe 96A458D4C378E0488E840D6B4FB0884D015DC265CA991799953D17052BB3BA03
• sha256_zip EDF16848F86608C1E3A52C211B753DF2629463D5F509BF209889C44D5B8B4921

Various other minor fixes and improvements.

Read-only users that do not have the permission to change their password will now receive an email again with the information Subject: Password Reset Failed: Please contact your PRTG administrator. Password Reset Failed: Not allowed. Read-only users without permission to change their password did not receive this email in the previous PRTG version before with the Forgot password? option on the PRTG login page.

Access keys for Probe and PRTG application server are now encrypted in the PRTG configuration file. The mentioned access keys were displayed in a readable format in the previous PRTG versions.

We fixed an issue for the DNS v2 sensor where the character escaping for curly brackets } in the Filter Value did not work properly. The sensor displayed the error message regex_error(error_brace): The expression contained mismatched { and }.

We fixed an issue for the Microsoft Azure Storage Account sensor's channel, Used Capacity , which was previously recording 0 values. With this fix the sensor returns the average values.

The OPC UA Server Status sensor now supports Client Keys with a 4096 bit length for OPC Client Certificates. In previous PRTG versions, the sensor reported an error when a private key with a length other then 2048 bits was used.

We fixed an issue for the Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized

We fixed an issue where the login for non admin user accounts did not work anymore when PRTG was updated to version 23.2.84.1566. The issue occurred for both manual and QR code login. The workaround was to log in with an admin user account.

The transfer of your probes to another server may fail in certain cases and will result in a deadlock. We are currently analyzing the issue.

With PRTG version 23.2.84.1566 we announced that you can find the Probe Transfer feature for PRTG Desktop under Probe Connection Settings in the PRTG setup and that it is no longer available in the Experimental Features section.

If you have more than one access keys in your list for remote probe connections, after updating to PRTG Preview version 23.2.85.1310, the configuration will retain only the first key entry and any other key gets deleted or overwritten. We are currently analyzing the issue and we will deliver a fix for this issue in the upcoming PRTG versions.

Note: Existing configurations fail after a second core restart after the update.

Solved with Preview PRTG 23.2.85.1327

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

Preview 23.2.85.1310

• sha256_exe 0EAF537945BDC40B60AEC4A8BA7A4B22B8B17D1D520D75607F2CA7E470621BBA
• sha256_zip 5595B872F30FC71513513F9C715FFC1C95B28CC91CE0F505B6DEC505D1CCB5B8

We improved the HTTP v2 sensor to be more compliant with its predecessors HTTP and HTTP Advanced sensor concerning the redirect handling. The HTTP v2 sensor now comes with the new Setting Maximum number of Redirects that is by default set to 16. You can use a value of 0 if you do not want the sensor to follow any redirects.

You can try out the experimental SNMP Disk Free v2 sensor that was rewritten to work on the Multi-Platform Probe. The SNMP Disk Free sensor monitors the free disk space on a logical disk via the Simple Network Management Protocol (SNMP). This sensor type has the same basic settings as its predecessor and comes with the channels Free Space (bytes), Free Space (%) and Total Space (bytes).

We fixed an issue that prevented logging in after an automatic logout, for example after a timeout, logout in a different tab or when the PRTG application server was disconnected.

• Your device Settings are now divided in collapsible sections providing you a clear overview of the available settings.
• You can now filter for items in the device Settings via an integrated search field. The matching results will be displayed expanded per section so that you can immediately change them.
• You can now collapse and expand the settings sections with a toggle button. Basic Device Settings are expanded by default. When you have expanded all settings sections, the button will display close all and open all when the settings sections are collapsed.

We fixed an issue that resulted in not keeping the zoomed-out position of a graph of a device or sensor overview in down or warning status after the automatic refresh.

We updated the German and Spanish language files.

We fixed an issue for Microsoft 365 credentials that were displayed in a readable format in the Core Log. The issue only occurred for the Log in Debug Level. 

We fixed an issue that appeared in the IPMI System Health sensors that caused increased mutex timeouts.

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

Preview 23.2.84.1562

• sha256_exe 571020D5363B56692249F190B0728560A60C590EB89B0F7F63AEBFF791D5F210
• sha256_zip 25A1199F80739374B678FD6695C11A648726CC2D7F98210E8D7AD01B8FCDC773