On this page
Access lists & panel settings
Separate SMPP source authentication, Nginx address lists and URL abuse controls.
Different control layers#
| Control | Scope |
|---|---|
| Client IP addresses | SMPP client identity/bind restrictions |
| Gateway IP authentication | Configured SMPP connection-mode checks |
| IP Access Lists | Country/CIDR files used by configured Nginx locations |
| Bot filter / human challenge | URL-service request handling |
| Host firewall | Operating-system network access, managed separately |
Nginx allowlists and blacklists#
The panel displays allowed/blocked countries and additional IPv4 ranges. Save lists & reload Nginx writes the configured files and requests a reload; it is not a read-only action. These files affect only Nginx configuration that actually includes them.
Before saving, confirm the intended virtual host/location, file permissions, operator access and recovery path. The example default files are /etc/nginx/bd_ip_ranges.conf and /etc/nginx/bd_ip_blacklist.conf. They are not SMPP client password settings.
URL protection settings#
Bot-filter rules and human challenges influence URL requests and click reporting. Preserve the meaning of allow/deny rules when changing patterns. A signed challenge secret belongs in runtime configuration, never in public page content.
Account separation#
Public demo access is a distinct identity controlled by DEMO_MODE. Disable that identity when leaving demo mode and retain a separate private administrator. Client web access is controlled on the client account.
Verify safely#
Test the intended access from a known permitted location and verify the Nginx configuration before reload. Review actual HTTP outcomes and click events; do not assume that saving a list changed every service on the server.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.