Path Panel DDoS Protection Management Panel User Guide
Complete REXE Path Panel user guide: Dashboard, My IPs, TR protection status, rule management, attack history, abuse filtered, password change and API access.
REXE Path Panel reseller guide: Dashboard, user management, IP management, TR protection, abuse filtered, bulk /24 protection, rule management, audit log and API access.
This guide is prepared for users with the Reseller role within the scope of the REXE remote protection service. As a reseller, you manage the Users under your account, make IP assignments and perform rule management. Through the Path Panel you can create users, assign IPs, create rules, review attack history, track audit history and enable API access.
You can access the Path Panel directly at x.rexe.tr.
When you log in, the dashboard page opens. Here, data for both your own IPs and the IPs of the Users under your account is displayed.
The dashboard only shows data for IPs assigned to you and your Users' IPs. Data from other resellers or admins is not visible.
Menu: Users
On this page you can view and manage the Users linked to you.
When a user is deleted, all rules, filter permissions and IP assignments belonging to that user are also permanently deleted. This operation cannot be undone.
Menu: IP Management
Displays the IP addresses assigned to you and lets you assign them to your Users.
| Column | Description |
|---|---|
| IP Address | Assigned IP address |
| Default Block | Automatic blocking status (Yes / No) |
| Protection | TR /32 protection status and on/off switch |
| Assigned Users | Users the IP is assigned to |
| Creation Date | Date the IP was added to the system |
You only see IPs assigned to you. You do not have permission to add or delete IPs; IP addresses are assigned by the upper manager (Admin/Manager).
You can assign an IP to your Users. In the IP detail popup:
Bulk operations:
Unassignment requires a 2-step confirmation. The removed user's rules on that IP are also deleted.
In the IP list, each IP's default block status is shown as "Yes" or "No". Default Block is managed automatically by the system based on the rule state of the IP. When there are no rules on the IP (including filter rules, ICMP/ping and presets), all ports are open and there is no Default Block. The moment the first rule is added, Default Block automatically comes into effect and only traffic matching the rules passes; when all rules are deleted, Default Block is automatically removed.
| Rule State | Default Block | Result |
|---|---|---|
| No rules | None | All ports open |
| At least 1 rule | Added automatically | Only allowed ports open |
| All rules deleted | Removed automatically | All ports open again |
Default Block management (adding/removing) is done by the Admin; as a reseller you only view the status.
In the Protection column of the IP list, each IP has a status indicator and an on/off switch (toggle).
| Status | Description |
|---|---|
| TR Protected | Protection active |
| TR Unprotected | Protection off |
| Queued | Operation queued |
| Applying | Protection enable operation in progress |
| Removing | Protection disable operation in progress |
| Error | Operation failed |
You can go to the rule management page by clicking the IP address. Rule creation, deletion and detail viewing can be performed.
Menu: Attack History
You view the history of attacks made against your IPs and your Users' IPs.
| Column | Description |
|---|---|
| Target IP | The IP address targeted by the attack |
| Reason | Attack type and trigger reason |
| Detail | Attack vector details |
| Peak BPS | The highest bandwidth of the attack |
| Peak PPS | The highest packet rate of the attack |
| Start | The time the attack started |
| End | The time the attack ended |
Menu: Abuse Filtered
You view IPs that have been filtered on the Path.net side due to abuse.
If the Admin or Manager has granted you the relevant permissions, additional protection pages appear in the left menu:
You can access the rule management page by clicking an IP address.
Newly created rules are shown at the top of the list. The rule creation screen has two modes: standard filter (protocol + port only) and hard filter (you pick one of the game or application filters). For SSH, RDP, and most services the standard mode is enough; both modes operate at Layer7 and track connection state, the only difference with a hard filter being application-specific packet inspection, and TCP Symmetric is just one of those hard options.
| Status | Description |
|---|---|
| synced | Rule successfully sent to Path.net |
| pending | Rule created, waiting to be sent |
| propagated | Rule propagated to all network nodes (full protection active) |
| failed | Send failed — can be retried with the retry button |
Propagation of a rule to all network nodes can take 2-5 minutes. Even if the rule appears not yet propagated in the panel, it has most likely already gone live; this is only a visual delay.
The rule form does not have a direct ICMP option. To turn Ping (ICMP) traffic on or off, use the "Ping On/Off" toggle at the top of the rule management page. When the toggle is turned on, the ICMP rule is created automatically; when turned off, it is deleted.
You can apply ready-made rule sets with a single click:
Menu: Audit Log
You view the audit record of operations performed by you and your Users.
| Filter | Description |
|---|---|
| Username | Filter the operations of a specific user |
| Operation Type | Filter by operation category |
| Action | Filter by the action performed |
| Tag | Tag-based filtering |
| Date Range | View operations within a specific period |
| Free Text Search | Search by keyword |
Operations performed via WHMCS appear with separate tags: WHMCS Create, WHMCS Update, WHMCS IP Assign, WHMCS Remove. This makes it easy to distinguish which operation was performed via the panel and which via the WHMCS integration.
If API access has been enabled for you by the Admin, additional pages appear in the left menu.
429 Too Many Requests response is returnedWith endpoint details, a response codes table and the "Try" feature, you can test directly. The endpoints you can access as a reseller:
Base URL: https://x-api.rexe.tr/api/v1/external — the paths below are appended to this address.
Shared endpoints (IP and rule management)
| Endpoint | Method | Description |
|---|---|---|
/health | GET | API connection check |
/ips | GET | IP list |
/rules | GET | All rules in the user + their hierarchy |
/rules/count | GET | Total rule count (hierarchical) |
/rules/count/ip/:address | GET | Single IP rule count |
/rules/count/ip/:address/:prefix | GET | CIDR/subnet rule count (max /20) |
/rules/ip/:address | GET | Rules belonging to a single IP |
/rules/ip/:address/:prefix | GET | CIDR block rules (max /20, aligned to network address) |
/rules | POST | Create a new rule |
/rules/:id | DELETE | Delete a rule |
/filters | GET | Filter list |
/attack-history | GET | Attack history |
Reseller-only endpoints
| Endpoint | Method | Description |
|---|---|---|
/users | GET | List the users linked to you |
/users | POST | Create a new user (user role only) |
/users/:id | PUT | Update user details (role cannot be changed) |
/users/:id | DELETE | Delete a user and their downstream chain |
/users/:id/disable | POST | Disable a user |
/users/:id/enable | POST | Re-enable a disabled user |
/ip-assignments | POST | Assign an IP to a user in your scope |
/ip-assignments | DELETE | Remove an IP assignment |
Permission-based protection endpoints
| Endpoint | Method | Description |
|---|---|---|
/network/protection/toggle | POST | Turn TR /32 protection on/off for a single IP |
/network/protection/bulk | POST | Bulk /32 protection (max /24 per block) |
/network/subnet24 | GET | Protectable /24 subnets and their states |
/network/subnet24/toggle | POST | Turn /24 blanket protection on/off |
Common error codes: 400 validation error, 401 invalid API key, 403 resource out of scope, 404 not found, 409 conflict (e.g. same IP + port), 500 server error.
The API Documentation page inside the panel shows the current list of endpoints open to your role; you can test them directly with "Try".
The X-API-Key header is required in all API requests:
curl -H "X-API-Key: YOUR_API_KEY" https://x-api.rexe.tr/api/v1/external/ips
From the IP Management page, select the relevant IP and assign it with "Assign to User". You can also make a bulk assignment by selecting multiple IPs with checkboxes.
No, you do not have permission to add/delete IPs. IP addresses are assigned by the upper manager (Admin/Manager).
Only if the Admin or Manager has granted you /32 protection permission. If granted, you can manage it with the Protection switch in the IP list or (permission-based) from the Bulk IP Protection / /24 Protection pages.
All rules, filter permissions and IP assignments belonging to the user are permanently deleted and their session is terminated instantly.
No, there is no permission to add/delete IPs. IP addresses are assigned by the upper manager (Admin/Manager).
Yes, from the Audit Log page you can track all user activities within your own hierarchy. Operations performed via WHMCS appear with separate tags.
A disabled user cannot log in to the panel and cannot use the API; their open sessions are terminated instantly. You can reactivate them at any time with the same toggle.
Complete REXE Path Panel user guide: Dashboard, My IPs, TR protection status, rule management, attack history, abuse filtered, password change and API access.
Path.net DDoS protection game filters guide: Arma/DayZ, Source Engine, CS:GO, CS2, FiveM, Minecraft, Rust and more — how to apply each filter.
Path.net DDoS protection application filters guide: OpenVPN, Wireguard, DTLS, RTP, QUIC, SIP, TCP Symmetric and more — how to choose the right filter.