PRTG Manual: System Administration—Core & Probes

Use Proxy Server

We recommend that you use PRTG with a direct internet connection. However, if you need to use a proxy, you can configure the relevant settings here. Choose between:

• No, use direct connection to the internet (default): Do not use a proxy. Use this setting if a direct internet connection to the PRTG core server system is available.
• Yes, in our network a proxy is mandatory: Define proxy settings below.

Proxy settings are valid for auto-update, activating the product, obtaining Geo Maps tiles, and for sending out HTTP, push, and SMS text message notifications.

Proxy Server

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Enter the address of the proxy server that you use for outbound connections. Enter a valid address.

Port

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Enter the port number of the proxy server that you use for outbound connections. Enter an integer value.

Use Proxy Credentials

This setting is only visible if you enable Yes, in our network a proxy is mandatory above. Determine whether the proxy server needs credentials or not:

• No, there are no credentials necessary: Do not use credentials for proxy connections.
• Yes, the proxy server requires credentials: Define credentials (username and password) below.

User

This setting is only visible if you enable Yes, the proxy server requires credentials above. Enter a username for proxy authentication. Enter a string.

Password

This setting is only visible if you enable Yes, the proxy server requires credentials above. Enter a password for proxy authentication. Enter a string.

Probe Connections IPs

Define how PRTG handles incoming connections from probes:

• Local Probe only, 127.0.0.1 (PRTG is not accessible for remote probes): The PRTG core server only accepts local probe connections. You cannot use remote probes with this setting enabled. This is the default setting in PRTG on premises.
• All IPs available on this computer: The PRTG core server accepts incoming connections from remote probes, no matter on which IP address of the PRTG core server they come in.

This is the default setting in PRTG hosted by Paessler.

• Specify IPs: The PRTG core server accepts incoming connections from remote probes only on the selected IP address(es) of the PRTG core server. In the list, select the IP addresses by adding a check mark in front of the desired IPs.

You can also change this setting in the PRTG Administration Tool on Core Server System.

If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the restart. During the restart, all users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Access Keys

Enter a list of access keys for remote probe connections. Enter one access key per line. Every remote probe that wants to connect to this PRTG installation has to use one of these keys.

For more information on how to set an access key for a remote probe, see section PRTG Administration Tool.

Allow IPs

Enter a list of remote probe IPs or Domain Name System (DNS) names that are accepted when connecting to this PRTG core server. Enter one IP address or DNS name per line. The local probe (127.0.0.1) is always allowed automatically. PRTG checks the list of allowed addresses before the list of denied addresses.

• [Empty]: An empty field does not allow any remote probes (only the local probe). Enter IP addresses or DNS names to allow remote probe connections.
  We recommend that you use IP addresses instead of DNS names because DNS name resolution might be cached.
• any: Enter the word any to automatically allow all remote probe connections.

This is the default setting in PRTG hosted by Paessler.
We recommend that you only use this option in intranets in PRTG on premises.

If the IP address of a remote probe changes regularly (for example, because of an internet provider assigning IP addresses dynamically), enter the potential IP range for the remote probe or use the any option.

You can use the PRTG syntax for IP address ranges here. For more information, see section Define IP Ranges.

Deny IPs

Enter a list of remote probe IPs or DNS names that are not accepted when connecting to this PRTG core server. Enter one IP address or DNS name per line. You can use this to explicitly deny connections from remote probes that you do not want to include in your setup either at all or for a certain time.

Access to IP addresses or DNS names that you enter in Allow IPs is denied if you enter them here. You can use this to allow access to an IP range in Allow IPs, but to deny access to a single IP address from this IP range here. You can use the PRTG syntax for IP address ranges here (see section Define IP Ranges).

We recommend that you use IP addresses rather than DNS names, because DNS name resolution might be cached.

Deny GIDs

Enter a list of global IDs (GID) Enter one GID per line. PRTG denies access to matching GIDs. If you remove a remote probe from the device tree or if you deny a remote probe after installation, its GID is automatically entered here. The remote probe is no longer able to connect. Denying GIDs is more precise than denying IPs, where other remote probes at the same location could be excluded, too.

A GID is the ID that PRTG attributes to every probe that you include in your monitoring.

Connection Security

Specify the security level for connections to and from the PRTG core server:

• High security (TLS 1.2): The PRTG web server only accepts high security connections from probes.
• Default security (TLS 1.1, TLS 1.2) (recommended): The PRTG web server additionally accepts connections secured with TLS 1.1 from probes.
• Weakened security (SSLv3, TLS 1.0, TLS 1.1, TLS 1.2): If you have probes that do not support high or default security connections because you updated from an older PRTG version, you can use this security level to connect and to update older probes. After updating, we recommend that you use the default or high security setting.

If you set a registry key in previous PRTG versions to override the Secure Sockets Layer (SSL)/Transport Layer Security (TLS) version and cipher suites of PRTG web server or probe connections, the High security setting overrides the registry setting and only TLS 1.2 is allowed. If you select the Default security setting, the registry value overrides the default security setting and the connection security defined in the registry applies.

If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the restart. During the restart, all users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Mini Probes

Define if you want to allow mini probe connections to your PRTG core server. If you want to use mini probes, you need to configure the PRTG web server to accept connections from mini probes here and choose the secure HTTPS server option in the web server settings. Choose from:

• No Mini Probes: Mini probes cannot connect to the PRTG web server. You are not able to monitor with mini probes if you choose this option.
• Allow Mini Probes to connect to the web server: Mini probes can connect to the PRTG web server and use the defined TCP port for the web server for this purpose. The default port for secure connections is 443.
• Allow Mini Probes to connect to an extra port: Mini probes can connect to the PRTG web server via a specific port. Use this if you do not want the whole PRTG web server to be reachable from other networks all the time only because of mini probes.
  SSL/TLS must be enabled on the mini probe port.

For more information ,see section Mini Probe API. See also the Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?

If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the restart. During the restart, all users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Mini Probe Port

This setting is only visible if you enable Allow Mini Probes to connect to an extra port above. Enter the number of the port for mini probe connections. Ensure that SSL is available on this port.

If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the restart. During the restart, all users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

This option is not available in PRTG hosted by Paessler.

Domain Name

To use the Active Directory integration, enter the name of your local domain. Enter a string or leave the field empty.

PRTG does not support trusted domains or AD subdomains. For more important notes about AD integration, see section Active Directory Integration, section Notes and Limitations.

Domain Access

Define how PRTG performs Active Directory queries:

• Use domain name: Use the entry in the Domain Name field above.
• Specify domain controllers: Use specific domain controllers. Specify the domain controllers below.

Primary Domain Controller

This setting is only visible if you enable Specify domain controllers above. Enter the DNS name of the primary domain controller.

Backup Domain Controller (optional)

This setting is only visible if you enable Specify domain controllers above. Optionally enter the DNS name of the backup domain controller or leave the field empty.

LDAP Connection Security

Define if you want to use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection to the LDAP server:

• Use LDAP without connection security: Do not use an SSL/TLS-secured connection.
• Use LDAP over SSL: Use an SSL/TLS-secured connection.

Access Type

Define which user account PRTG uses to configure Active Directory (AD) access:

• Use the PRTG core service account (usually LOCAL SYSTEM): Use the same Windows user account configured for the PRTG core server service. In a default installation, this is the "local system" Windows user account. If this account does not have the right to query all groups of your Active Directory, do not use this option.
• Use explicit credentials: Define a user account that PRTG uses to authenticate against the Active Directory. This should be a user account with full access to all of your Active Directory groups.

PRTG uses this account to query the AD for available groups.

Access User

This setting is only visible if you enable Use explicit credentials above. Enter the Windows user account name that PRTG uses to authenticate for Active Directory configuration.

Access Password

This setting is only visible if you enable Use explicit credentials above. Enter the password for the Windows user account that PRTG uses to authenticate for Active Directory configuration.

Logfile Records

Define how long records in the system logfile Log Database.db are kept. Enter a value in days. All entries older than this value are deleted from the logfile automatically. This also affects the content of the Logs tab of monitoring objects like sensors. Keep this value as low as possible to enhance system performance.

The default value is 30 days.

Web Server Log Records

PRTG creates one web server logfile every day. Define how many web server logfiles are kept. Enter a value in days. All web server logfiles older than this value are deleted automatically.

The default value is 30 days.

Historic Sensor Data

Define for how many days historic sensor data is kept for all sensors. It is used to create reports of monitoring data. Enter a value in days.

Depending on the used intervals and the number of sensors in your setup, the file containing this data can become large. For smaller installations (up to 500 sensors) a value of 365 is usually fine.

Historic sensor data is the basis for reports on monitoring data. If you decrease this value, less historic monitoring data is available.

The default value is 365 days.

The maximum value is 9999 days.

Toplist Records

Define how long toplist records for xFlow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors are kept. Enter a value in days. We recommend that you use 30 days here.

Old toplist data is deleted automatically as soon as a limit of 2 GB is reached. The oldest data is deleted from the database first.

The default value is 30 days.

Closed Tickets

Define how long tickets that are in status closed are kept. Enter a value in days.

The default value is 365 days.

Reports

Reports generated in PDF format are stored on disk for later reference. Define the maximum age for these reports. Enter a value in days. All reports that are older than this value are deleted automatically.

The default value is 365 days.

Configuration Auto-Backups

PRTG creates one backup of your configuration every day. Define the maximum age for these backups. Enter a value in days. All configuration backup files that are older than this value are deleted automatically.

The default value is 365 days.

Screenshots of HTTP Full Web Page Sensor

Define how long the screenshots of the HTTP Full Web Page sensor (PhantomJS browser engine) are kept. Enter a value in days. PRTG deletes older screenshots with every sensor scan.

The default value is 10 days.