Firewall
Open Settings > Firewall.How The System Works
Configure web and game protection such as DDoS protection, bot filtering, rate limits, and challenges. This page stores the records and settings used by the related admin workflow, storefront page, checkout flow, support area, theme, or integration. After saving, refresh the affected page and test the result from the user side when possible.Before You Fill The Form
Check that your admin role has permission for this page. If the form depends on a payment provider, server connection, theme module, or external account, configure that dependency before saving. If a selector is empty, create the related product, category, user, role, provider, server, or currency record first so it appears in the dropdown.How To Fill The Form
Create Or Update A Record
- Open the page from the admin menu.
- Click the add, create, publish, send, give, ban, upload, or generate action shown on the page.
- Fill the required fields first. Required fields are usually marked with an asterisk in the panel.
- Fill optional fields that affect display, delivery, pricing, limits, rewards, integrations, or visibility.
- Save the form and wait for the success message.
- Open the list or public page to confirm that the record works as expected.
Page Actions
- Switch Web tab: Runs this page action for the selected record or current settings.
- Switch Game Server tab: Runs this page action for the selected record or current settings.
- Add rule: Opens the form for creating or publishing a new record.
- Test protection: Verifies the connection, configuration, or selected value before you rely on it.
- Save settings: Stores the current settings or list changes.
After Saving
Return to the list and confirm that the record is visible. If the page supports ordering, drag the record into the correct position and click Save changes. Then test the affected user flow, such as checkout, login, support, content display, reward delivery, or integration sync.Important Notes
- Strong firewall settings can block real users if configured too aggressively.
- Use test actions before relying on new rules.
