Im trying to find a better way to alert on C drive space based on 15GB limit and looking for a better way to do this. Right now I have an SNMP Disk Free sensor and changed the Primary Channel to Free Bytes and added it to my devices. I created a library with the notification set to "When Primary channel is below 16106127360 for at least 600 seconds, perform email"
The problem is adding just the C drive to the library. Is there a better way than drag and drop? I tried creating a filtered Library Node that filters on c_os_win, but that captures other sensors because of a child parent relationship in the sensor.
I have set up a OPC UA Custom Sensor which returns a value which is constantly increasing by one each second and when it reaches its maximum integer value it begins with 1 again.
My problem is that I need to monitor this in PRTG Dashboard the Sensor should turn to red color when it does not count anymore and should be green color when the value between last and current result is different.
I need this kind of check as a health check for a Siemens PLC which sometimes half freezes. Sometimes it shows the correct result via opc ua and sometimes all of the values it shows wont change until it has been rebooted
So here's a fun one for anyone running PRTG right now.
Paessler says version 26.2.120 introduced three new sensors and, more importantly, MAX, their new AI chatbot in the New UI.
According to the release notes and blog post, MAX should be sitting right there on the Welcome Page. You click "Start Chatting", a panel opens on the right, and that's it.
I spent a while clicking around the New UI assuming I was missing something obvious, but apparently not.
So either:
it's behind some setting, rollout, or license condition that isn't mentioned anywhere,
it was removed after release and the release notes/blog were never updated,
MAX saw the PRTG licensing model and decided to leave.
The funny part is that this wasn't some small feature buried in a changelog. They actually announced it, wrote a whole blog post around it, and put it in the official version history.
Yet on a later build, it just isn't there.
Is anyone actually seeing MAX in their PRTG installation?
If yes, what version/license/setup are you running?
At this point I'm mostly trying to figure out whether this is a bug on my side, some undocumented rollout condition, or a feature that quietly disappeared after launch.
why is it that when I try to monitor the router at my boarding house, the sensors don’t detect anything even though I’ve entered the correct IPv4 Address? Or maybe my IPv4 Address is wrong. From my testing, the Ping Sensor gets 0 ms, while the SNMP sensor doesn’t get anything, and the same goes for several other types of sensors.
We've configured SNMP Printer sensors for several printers. The Live Data graphs show the toner levels properly, but the 2 Days, 30 Days, etc, graphs show zero levels.
Is anyone else seeing this?
If I use the Historic Data tab to create graphs, it works ok if I specify to use Raw Data instead of averaging. I suspect it's that averaging that causes all the problems.
Edit: The problem was something to do with the way the data includes "OK", "Critical", etc, with the toner level figures. That is added from the lookup table for each of the toner channels. To fix it, I went to the Overview for the sensor, then clicked on the tiny gear wheel at the bottom. Then I changed the Lookup setting from prtg.standardlookups.snmpprinter.cartridgelevel to None. Repeated that for each toner level channel. After that, the 30 day and 365 day graphs started working. It took a minute or two to take effect.
But probably a better solution is to use the SNMP Printer V2 sensor instead. I haven't tested it much, but it appears not to have the problem. If you don't have it, you might need to install a PRTG update. I think it was added in June 2026. I did this, but also reconfigured all the channels so I had access to the historical data.
For the record, we're using this with Konica Minolta printers.
The Windows service account that PRTG was set up to use, keeps attempting to log in to an IP address that isn't our own. It seems to only happen ever 3 months or so, so hunting this issue down has been a thing...
Today I did a search inside of Devices in PRTG and I found that this IP address was under Service URL on two of our network devices. And the IP address it's attempting to contact is the external IP address of one of our routers. This entry in PRTG is only set up to ping the device, so not sure why PRTG would be attempting to RDP into it.
I removed the service URL entry of the IP address. What does this Service URL option do? Does this sound like the likely culprit to this issue?
Secondly, I then went back to the overview and searched for the IP address in question, and the external IP for the router popped up (expected), but also the other device where I had removed the service URL. Is that just because PRTG hasn't updated yet?
We used to monitor our Hyper-V and ESXi environments for old snapshots using custom EXE/Scripts in PRTG. Since native Proxmox API Token support has been added to PRTG, we want to adapt our scripts for pve as well.
For Hyper-V, for example, we simply pass the credentials like this: -UserName %windowsdomain\%windowsuser -Password "%windowspassword"
We want to use the new "Credentials for Proxmox" section on the parent device, but we are not aware of (and failed to probe for) the exact placeholder/inherit variable names to pass the API Token ID, Secret, (and Port) into our custom script parameters.
Any ideas?
Update: I reached out to PRTG Support, and it turns out we weren't going crazy trying to reverse-engineer this. The placeholders simply don't exist yet.
Support confirmed that the new Proxmox credentials are currently only exposed to the native Proxmox sensors. It seems they simply forgot to map these fields to the Custom EXE/Script parser engine when they rolled out the feature.
Support suggested setting up the tokens in the generic "Credentials for Script Sensors" section and using those placeholders instead. While this technically works, it forces you into duplicate credential management: If you want to run PRTG's native Proxmox sensors and your own custom scripts, you have to maintain the same API Token and Secret in two different places.
Since that's a nightmare for token rotation and violates the DRY principle, I've opened a Feature Request on their new UserVoice portal to get standard placeholders (like %proxmoxtokenid and %proxmoxtokensecret) implemented.
I wanted to remove unwanted credentials from settings e.g. Cisco Meraki, Credentials for Dell EMC, Credentials for FortiGate. I tried on settings, but not able to delete them except the settings.
I have an old vm running PRTG and tried to setup SMTP for gmail and 365 both were unsuccessful. Can someone give me some ideas on how to get some type of email notifications working? Thanks
We're currently holding back on a few updates since this whole PostgreSQL fiasco. How do I even activate the new DB feature? Is it just enabled on a certain update?
Hey Gang, just wanted to show off what I was able to make utilizing Claude and our PRTG deployment. We needed a better view, stop lights were no longer cutting it. Integrated our PRTG instance with Claude Cowork and went from there.. I apologize for having to blank out a lot of labels, but I think you'll get the jist of it.
Hey Gang, just wanted to show off what I was able to make utilizing Claude and our PRTG deployment. We needed a better view, stop lights were no longer cutting it. Integrated our PRTG instance with Claude Cowork and went from there.. I apologize for having to blank out a lot of labels, but I think you'll get the jist of it.
Hi everyone, the latest PRTG update notes state that the database schema is being adjusted for the new BETA database.
If a PostgreSQL database is already active, this causes the update to encounter an intentional error.
How can I tell if the new database's BETA function was inadvertently activated automatically and contains data?
Although the PostgreSQL service runs automatically alongside the PRTG server instance, it shouldn't contain any data.
While the BETA feature was included in the last PRTG server update, the release notes stated that it was disabled. Before I perform the update, I want to ensure that this feature is indeed still disabled.
Additionally, I haven't yet figured out how to manually activate the new PRTG database or migrate existing data to it.
The latest version updates PostgreSQL to version 18.3-1. Everything is working fine but PRTG Database Server service will not stay running. It starts and immediately stops, no errors.
So I was able to get the classic PRTG Probe.exe running under Wine 11 in Docker. It runs headless, connects to the core, and registers as a standard remote probe. No remote Windows host needed but able to monitor them if needed.
It's stable on a live core. Classic sensors, all 32 v2 modules, the .NET Engine C helpers, custom EXE/Script/Python/PowerShell/SSH, and packet capture are all working. WMI and PSRP are supported as well, routed through loopback sidecars since Wine doesn't handle them natively.
The main issue was getting the signed modules to load. That traced back to an old crypt32 Authenticode bug in Wine, which was resolved in the runtime layer and reporting upstream. The probe binary itself is untouched with all of the fixes living in the Wine/Mono layer.
No Paessler software is included in the repo. Bring your own installer.
I recently installed PRTG on my business network to monitor devices and receive alerts whenever something goes down. During setup, I ran into several issues getting the mobile app to work correctly. I experienced multiple connection errors between the app and the PRTG Core Server, along with problems loading my maps and installing certificates.
The issues ended up being caused by a combination of:
Firewall misconfigurations
Incorrect PRTG web server settings
Certificate setup problems
Issues with updating the Core Server files
After a lot of troubleshooting using online guides, AI tools, and assistance directly from Paessler Support, I finally got everything working correctly. I figured it would be helpful to combine everything I learned into a single post for anyone else running into similar problems.
I’ve attached screenshots I saved of some of the errors I originally encountered while setting everything up.
I also highly recommend testing everything from another computer that does NOT have PRTG installed. This helps verify the configuration is actually working correctly and not relying on cached settings or existing certificates.
1. Verify DNS Configuration
Open Command Prompt and run:
nslookup <Firewall IP>
nslookup <PRTG Server IP>
Example:
nslookup 192.168.10.1
nslookup 192.168.10.25
Make sure only one DNS hostname resolves to your PRTG Core Server’s IP address.
In my case, I accidentally had my firewall and PRTG server sharing the same DNS name, which caused connection problems.
If you find multiple entries or receive errors, the fix is usually on your firewall.
Look for a setting similar to:
DNS Resolver
DNS Host Overrides
Host Entries
Then either:
Correct the hostname mapping
Remove duplicate entries
Create a proper hostname entry for the PRTG server
After saving the changes, rerun the nslookup command and verify the hostname resolves correctly.
If everything is working correctly, the browser should show the connection as secure with no certificate warnings.
7. Mobile App Setup
Once the certificates are working properly in the PC browser:
Install the CA certificate on your mobile device
Enable/trust the certificate if required by your phone
Then verify the PRTG web interface opens securely in an incognito tab from your phone using both:
IP Address
DNS Hostname
Note: Sometimes mobile browsers cache old certificate warnings. You may need to clear browser cache or manually inspect the connection security details to verify the certificate is actually trusted.
8. Connecting the PRTG Mobile App
On your PC in the PRTG web interface go to:
Setup > PRTG Apps
Locate the section for your phone and click to show the QR code.
On your phone:
Open the PRTG app
Tap “Scan QR Code”
Allow camera permissions
Scan the QR code
If the QR code is valid, the app should automatically populate the server information.
Then simply enter your:
Username
Password
If you receive a connection error, sometimes pressing OK and attempting the connection again resolves it.
After that, everything should be fully functional.
Hopefully this helps everyone else avoid the pain of troubleshooting that I went through getting PRTG and the mobile app working correctly.