<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: System Administration—Core & Probes

Use Proxy Server

We recommend using 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 there is a direct internet connection available to the server running the PRTG core server.

• Yes, in our network a proxy is mandatory: Define proxy settings below.

Note: Proxy settings are valid for Auto-Update, Activate the Product, obtaining Geo Maps tiles, and for sending out HTTP, push, and SMS text message Notifications. The sensor types Cloud HTTP and Cloud Ping use these proxy settings as well.

Proxy Server

This setting is only visible if proxy usage is enabled above. Enter the address of the proxy server that you use for outbound connections. Please enter a valid address.

Port

This setting is only visible if proxy usage is enabled above. Enter the port number of the proxy server that you use for outbound connections. Please enter an integer value.

Use Proxy Credentials

This setting is only visible if proxy usage is enabled above. Determine whether the proxy server needs credentials or not. Choose between:

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

User

This setting is only visible if proxy credentials are enabled above. Enter a username for proxy authentication. Please enter a string.

Password

This setting is only visible if proxy credentials are enabled above. Enter a password for proxy authentication. Please enter a string.

Probe Connections IPs

Define how PRTG handles incoming connections from probes. Choose between the following options:

• Local Probe only, 127.0.0.1 (PRTG will not be accessible for Remote Probes): This is the default setting. The PRTG core server only accepts local probe connections. You cannot use remote probes with this setting enabled.
• All IPs available on this computer: The PRTG server will always accept incoming connections from remote probes, no matter on which IP address of the core server they come in.
• Specify IPs:The PRTG server will accept Incoming connections from remote probes only on the selected IP address(es) of the 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.

Note: If you change this setting, PRTG needs to restart the core server. Because of this, all users of PRTG's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a dialog box will appear which asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen.

Access Keys

Enter a list of access keys, one 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 this key for a probe, please see the PRTG Administration Tool section.

Allow IPs

Enter a list of remote probe IPs that will be accepted when connecting to this PRTG installation; one IP address per line. The local probe (127.0.0.1) is always allowed automatically. Allowed IPs are checked first (before denied IPs). You can use PRTG's syntax for IP address ranges here (for information about the syntax please see the Define IP Ranges section).

• [Empty]: An empty field does not allow any remote probes (but only the local probe). Please enter IP addresses to allow remote probe connections.
• any: Enter the word any to automatically allow all remote probe connections. Note: This is recommended for use in Intranets only!

Note: If the IP address of your remote probe changes regularly (e.g. due to an internet provider assigning IP addresses dynamically), please enter the potential IP range for this remote probe or use the any option.

Deny IPs

Enter a list of remote probe IPs that will not be accepted when connecting to this PRTG installation; one IP address per line. This is useful to explicitly deny connections from certain remote probes you do not want to include in your setup any more (e.g. for a certain time). Access to IP addresses you allowed above will be denied if you enter them here. This is useful to allow access to an IP range in the field above, but deny access to a single IP address. You can use PRTG's syntax for IP address ranges here (see the Define IP Ranges section).

Deny GIDs

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

Mini Probes

Define if you want to allow Mini Probe connections to your PRTG server. If you want to use Mini Probes, you need to set up your PRTG web server to accept connections of Mini Probes here and choose the secure HTTPS server option in the web server settings. Choose between:

• No Mini Probes: Mini Probes cannot connect to your 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 your PRTG web server and use the defined TCP port for the web server for this purpose. The default port for SSL connections is 443.
• Allow Mini Probes to connect to an extra port: Mini Probes can connect via a specific port to your PRTG web server. This is useful if you do not want to have your whole PRTG web server reachable from other networks all the time only because of Mini Probes.
  Note: SSL is always required to be active on the Mini Probe port.

Please refer to the PRTG API for the full Mini Probe documentation. See also the section More below for further information about PRTG Mini Probes.

Note: If you change this setting, PRTG needs to restart the core server. Because of this, all users of PRTG's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a dialog box will appear which asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen.

Mini Probe Port

This field is only visible if you select the extra Mini Probe port option above. Enter the number of the port that you want to use for Mini Probe connections. Ensure that SSL is available on this port.

Note: If you change this setting, PRTG needs to restart the core server. Because of this, all users of PRTG's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a dialog box will appear which asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen.

Domain Name

To use the Active Directory Integration please enter the name of your local domain. Please enter a string or leave the field empty.

Access Type

Define which user account will be used to configure Active Directory (AD) access. This account will be used to query the AD for existing groups. Choose between:

• 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 you should not use this option.

• Use explicit credentials: Define a user account that will be used by PRTG to authenticate against the Active Directory. This should be a user account with full access to all of your Active Directory groups.

Access User

This field is only visible if the use of explicit credentials is chosen above. Enter the Windows user account name which is used to authenticate for Active Directory configuration.

Access Password

This field is only visible if the use of explicit credentials is chosen above. Enter the password for the Windows user account which is used to authenticate for Active Directory configuration.

Data purging enables you to automatically delete unnecessary data to free up disk space and improve system performance. You can define different time spans for several kinds of data. Select here for how many days historic data remains accessible. For further information on storage locations, please see the Data Storage section.

Logfile Records

Define how long records in the system logfile Log Database.db will be kept. Enter a value in days. All entries older than this value will be deleted from the log file 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.

Web Server Log Records

PRTG creates one web server log file every day. Define how many web server log files are kept. Enter a value in days. All web server log files files older than this value will be deleted automatically.

Historic Sensor Data

Define for how many days historic sensor data are 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 (500 sensors or less) a value of 365 should be fine. Historic sensor data is the basis for reports on monitoring data. If you decrease this value, there will be less historic monitoring data available!

Toplist Records

Define how long toplist records for Flow and Packet Sniffer sensors are kept. Enter a value in days. We recommend using 30 days here. However, old toplist data will be purged automatically as soon as a limit of 2 GB is reached. Thereby the oldest data is deleted first from the database.

Closed Tickets

Define how long tickets which are in status closed are kept. Enter a value in 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 older than this value are deleted automatically.

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 older than this value will be deleted automatically.

Full HTTP Sensor Screenshots

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