Every hotspot operator meets the same short list of faults, usually at the worst moment: a full site, paying customers, and a login page that will not appear. This guide works through the twelve most common MikroTik hotspot problems in the order you should check them, with the actual fix for each. Where a fault is caused by manual operations rather than the network, we say so, because those are the ones that keep coming back until the process changes.
1. The login page never appears
The customer connects to your WiFi and nothing pops up. Usually one of three causes.
- •DNS is not being intercepted. The hotspot server must own DNS for unauthenticated clients. Check that your hotspot profile has a valid DNS name, that `ip dns` has servers set with allow-remote-requests enabled, and that the hotspot interface is in the right address pool.
- •The device is trying HTTPS first. Modern phones test connectivity over HTTPS, which cannot be transparently redirected. The portal must be reachable on plain HTTP, and captive-portal detection URLs (Apple, Google, Microsoft) should be allowed through the walled garden so the phone triggers its own sign-in sheet.
- •A stale DHCP lease. The device kept an address from another network. Remove the lease on the router, or have the customer forget the network and reconnect.
The fix that lasts: portals that are generated rather than hand-configured do not drift. Iterative Billing deploys the hotspot profile, DNS, walled garden and portal files to the router automatically when you add it, so the interception chain is correct on every site by construction.
2. Connected to WiFi, but no internet after login
Authentication succeeded and traffic still does not pass. Check, in order: the hotspot user profile has an address pool with free addresses; NAT masquerade covers the hotspot subnet; the customer's device is not pinned to a static DNS the walled garden blocks; and the client's rate limit is not set to something unusable on a mistyped profile.
3. A voucher is rejected or says it is already used
Voucher stock is where paper-based hotspot businesses leak money. Common causes: the voucher was sold twice by two agents, it expired while sitting in a drawer, or it was generated on a router that has since been reset, so the router no longer knows it. Vouchers held only on the router die with the router.
The fix that lasts: keep voucher stock in the billing platform, not in a router's local user list. Iterative Billing generates time and data vouchers centrally, tracks which are sold, used and expired, and cleans up phantom stock automatically, so a reset router never destroys inventory and no code can be sold twice.
4. Users are disconnected at random
If sessions drop unpredictably, look at idle timeout and keepalive timeout in the hotspot user profile (an aggressive idle timeout disconnects people who simply stopped scrolling), then at wireless stability, then at the address pool: if the pool is smaller than the number of devices, DHCP recycles addresses and sessions break. Also check for two DHCP servers on the same broadcast domain, which is common when a new access point ships with DHCP enabled.
5. Speeds are far below the package
Start at the queue. If the customer's profile sets a rate limit, confirm the syntax and that no parent queue is throttling the whole hotspot. Then check the actual backhaul under load rather than at 6am, and the wireless side: channel congestion in a busy estate will cap a customer long before your billing does. Finally, confirm that a shared queue is not silently dividing your uplink across far more sessions than it was sized for.
6. The customer paid but is still offline
This is a billing fault presenting as a network fault, and it is the single most common hotspot support call. The payment arrived, but nothing told the router to open the session, because the reconciliation is manual or the callback failed. Our companion guide, how to fix M-Pesa and billing problems, covers the payment side in detail.
The fix that lasts: payment and provisioning have to be one automated loop. Iterative Billing matches the payment to the account and opens the session in seconds through built-in RADIUS, with no operator in the middle.
7. HTTPS sites hang before login
If unauthenticated users see hanging pages rather than the portal, your walled garden is too narrow. Allow the captive-portal detection endpoints and your own payment provider's domains, otherwise an M-Pesa or card callback can be blocked at the exact moment the customer is trying to pay for access.
8. The portal loads but payment never completes
Check that the payment provider's callback URLs are registered and reachable, and that the customer's phone is on a network that can reach the provider at all. A customer paying from your hotspot cannot complete a payment if the payment domain is not in the walled garden, a genuinely common self-inflicted outage.
9. Devices are counted wrongly, or one person shares with ten
Set shared-users on the hotspot user profile to what you actually sell. If you sell one device per voucher, one is the number; if you sell a household bundle, set it deliberately. MAC binding helps but hurts customers who change devices, so pair it with a clear support path to release a binding.
10. Router reboots and loses the hotspot configuration
Any configuration living only on the router is one power cut from being gone. Keep the source of truth off the device, and push configuration back automatically after a reboot rather than rebuilding it by hand.
11. Multiple sites, and you cannot tell which is broken
Without central monitoring, you learn about an outage from a customer. SNMP monitoring and per-site session visibility turn that around, you see a site stop selling before anyone calls. Iterative Billing monitors each connection and, when something breaks, its AI agents troubleshoot at the customer-router and MikroTik network level and reboot the router remotely, so most faults are resolved before a customer notices.
12. The same fault, every week
If you recognise a recurring fault in this list, the underlying cause is almost never the router. It is that a human is holding state the system should hold: which voucher was sold, which customer paid, which profile a site is supposed to have. Automate that state and the fault stops recurring.
Stop firefighting, start operating
Every fix above is a symptom fix. The structural fix is a platform that provisions the router, owns the voucher stock, matches the payment, opens the session and watches the site. Adding a MikroTik to Iterative Billing is fully automated and takes at most 8 minutes from adding the router to fully up and running, and hotspot subscribers are unlimited.
Apply at https://billing.iterativebilling.com/register to test it on your own network, then read the hotspot billing guide for Kenya for the business side. Be Wisp B.
Frequently asked questions
- Why is my MikroTik hotspot login page not showing?
- Usually DNS interception, HTTPS, or a stale lease. Confirm the hotspot profile has a valid DNS name and that ip dns has servers with allow-remote-requests enabled; make sure the portal is reachable over plain HTTP because HTTPS cannot be transparently redirected; allow the Apple, Google and Microsoft captive-portal detection URLs through the walled garden so phones trigger their own sign-in sheet; and clear any stale DHCP lease from a previous network.
- My hotspot customer paid but is still not connected. What do I check?
- This is normally a billing fault, not a network one: the payment arrived but nothing instructed the router to open the session, because reconciliation is manual or a payment callback failed. Check that your provider's callback URLs are registered and reachable, and that the payment domains are inside the hotspot walled garden. The durable fix is an automated payment-to-provisioning loop, where a confirmed payment activates the session through RADIUS in seconds with no operator involved.
- Why do hotspot vouchers say already used or get rejected?
- Typically the voucher was sold twice by different agents, expired unsold, or was generated on a router that has since been reset and no longer holds the user list. Vouchers stored only on a router are lost when the router is reset. Keeping voucher stock centrally in the billing platform, with sold, used and expired states tracked and phantom stock cleaned up automatically, removes all three failure modes.
- Why do hotspot users keep getting disconnected randomly?
- Check the idle timeout and keepalive timeout on the hotspot user profile first, since an aggressive idle timeout disconnects users who simply stopped browsing. Then check for an address pool smaller than the number of devices, which forces DHCP to recycle addresses and break sessions, and for a second DHCP server on the same broadcast domain, which often arrives with a new access point that ships with DHCP enabled.