(v2.3) Settings - Configuration - Security - Access restrictions
Section for setting up various filters restricting access of selected clients to the web interface of the application.
Access restrictions - IP filter
Filter enabled
If enabled, access to the application will be restricted based on the listed IP ranges and a client's IP address.
(default: disabled)
Blocked networks list
List of IP addresses and ranges (in CIDR notation) separated by line breaks. Clients with an IP address within the specified ranges will not have access to the application.
Access restrictions - reverse record lookup
Filter enabled
If enabled, access to the application will be restricted based on the listed reverse lookup records, which are compared with the reverse lookup record of the client's IP address.
(default: disabled)
Blocked records list
List of blocked reverse lookup records (or parts of them) separated by line breaks. Clients with reverse lookup record containing any of the listed lines will not have access to the application.
Access restrictions - country
Filter enabled
If enabled, access to the application will be allowed or restricted based on the client's country.
(default: disabled)
Filter type
Blacklist mode - clients accessing the application from the listed countries will not have access to the application.
Whitelist mode - only clients accessing the application from the listed countries will have access to the application.
(default: blacklist)
List of allowed/blocked countries
A list of blocked or allowed countries. Depending on the whitelist/blacklist type, clients accessing the application from any of the specified countries will/will not have access.
Access restrictions - User-Agent header
Filter enabled
If enabled, access to the application will be restricted based on the HTTP User-Agent header. If the User-Agent header contains a string from the list, access is denied.
(default: disabled)
Blocked User-Agent list
List of blocked User-Agent strings (or parts of them) separated by line breaks. Lines are compared with the HTTP User-Agent header and if any line is contained within the header, access is denied.