WISPOX setup and operating guide.

Overview

WISPOX is an ISP operations platform for MikroTik hotspot networks. It helps a service provider manage routers, customer accounts, vouchers, packages, SMS notices, payments, reports, staff access, and ISP workspaces.

The app has two main parts. The public website explains the product and sends users to login or registration. The dashboard is the private workspace used by ISP staff and platform admins.

Workspace Setup

A new ISP starts from the Register page. The form creates a workspace on wispox.com and records the ISP name, workspace slug, admin name, phone, email, plan, and password.

Steps

1. Open /register.
2. Enter the business name and workspace slug.
3. Enter the admin contact details.
4. Select a package from the active billing plans.
5. Submit the form and sign in from /login.

Router Setup

The router wizard guides staff through MikroTik setup. A step cannot be skipped until the required fields are complete.

Required router details

• Router name
• Connection type
• Management IP for public IP routers
• API username
• API password
• API port, usually 8728

RouterOS services

For public IP routers, RouterOS API must be reachable from the WISPOX server. The MikroTik hotspot profile must use RADIUS, and the RADIUS client must point to the WISPOX server or tunnel address.

WireGuard Path

WireGuard is used when the router site has a shared IP address or no inbound port forwarding. The router dials out to the WISPOX server, then WISPOX reaches the router through the tunnel address.

Information needed

• Router tunnel address
• Server endpoint
• Allowed address
• Server public key
• Router public key

Basic flow

1. Create the WireGuard interface on MikroTik.
2. Add the peer using the server public key.
3. Add the tunnel IP address to the router.
4. Allow API traffic over the tunnel only.
5. Use the router wizard to save and test the tunnel path.

Customers

Customer records store usernames, passwords, package details, phone numbers, account status, expiry date, and service type. Staff can create customers by form, sell a package, suspend a user, activate a user, or extend expiry.

Customer statuses

• Active: The account can use the hotspot service.
• Expired: The paid period has ended.
• Suspended: Staff have blocked the account.

Active sessions come from RADIUS records and router session cache. If sessions do not show, check router accounting, RADIUS secret, tunnel reachability, and the session polling job.

Packages and Sales

Packages define the internet access product sold to customers. Typical plans include hourly, daily, weekly, and monthly access.

Vouchers

Vouchers are pre-generated access codes. Staff can print them, export them, assign them to agents, and track sales.

Voucher agents

Agents receive voucher stock and sell to customers outside the office. The agent page tracks stock, payouts, and transaction history.

Payments

WISPOX tracks customer payments and ISP subscription payments. Paystack handles online ISP package payments, and payment reports show the status of each payment event.

Payment checks

• Confirm the Paystack public key and secret key.
• Confirm the callback URL in Paystack.
• Check the payment reference on the report page.
• Use SMS alerts to notify ISPs after package payment.

Reports

Reports help owners review performance without opening many pages. The dashboard shows active sessions, customer counts, router count, today revenue, total revenue, pending payments, voucher status, new customers, and expiring customers.

Common reports

• Payments report
• Subscription report
• Customer export
• Voucher export
• Accounting report
• Audit log

Domains

Workspaces can run on the main WISPOX domain or a custom domain. Custom domain requests are submitted by the ISP, then reviewed by the platform admin.

Wildcard DNS

For workspace subdomains, create a wildcard DNS record that points *.wispox.com to the WISPOX server. The app can then serve registered workspace slugs without a manual DNS record for each ISP.

Custom domain approval

1. The ISP submits the domain request.
2. The platform admin reviews it.
3. DNS is pointed to the server.
4. The platform admin verifies and approves the domain.

Security

WISPOX includes staff permissions, login alerts, two-factor verification, account lockout after failed login attempts, session timeout, audit logs, and secure cookie settings.

Recommended settings

• Turn on two-factor verification for platform admins.
• Use staff permissions for non-owner users.
• Keep router API access limited by firewall or WireGuard.
• Review audit logs after staff or billing changes.
• Use HTTPS for all domains and portals.

Troubleshooting

Hotspot users cannot log in

• Check the MikroTik RADIUS client secret.
• Check that the hotspot profile has use-radius=yes.
• Check that RADIUS accounting is turned on.
• Check that RouterOS can reach the WISPOX server or WireGuard tunnel address.

Active sessions do not show

• Check RADIUS accounting port 1813.
• Check that interim accounting updates are enabled.
• Check the router session polling job.
• Check that WISPOX can reach the router API.

Paystack payment hangs

• Check API keys.
• Check webhook and callback URLs.
• Check the payment reference in the subscriptions report.
• Check SMS settings before expecting payment SMS notices.