General Settings
Manage ISP identity, branding, preferences, billing, service, network, integrations, security, and portal configuration.
Company & ISP Profile
Choose a category, change what you need, then save that section.
Routers
Add a MikroTik router in 4 easy steps
No typing of commands: ONE-KONEK makes the script, you paste it once, and the router connects by itself.
If it does not connect
| What you see | What to do |
|---|---|
onekonek-wg showsI(invalid) in Interfaces |
Paste the newest script again (Routers > terminal button). It now picks a free WireGuard port by itself. |
| Peer has never handshaked | The server does not know the router yet: do step 3 → "On the server" (one line), then wait 30 seconds. |
/ping to the server tunnel IP gets no answer |
The router cannot reach the server endpoint: check the router internet and that UDP to the server port is not blocked. |
| The terminal says "this router already has a tunnel" | Use it: Add Router > "It already has a tunnel" and enter its address from IP > Addresses. |
| Login failed / not enough permissions | Paste the script again; it recreates the ONE-KONEK user and its rights. |
| ONE-KONEK is on a different machine than the WireGuard server | That machine needs a route to the tunnel subnet (or install ONE-KONEK on the WireGuard server). |
Router NAS Management
Add a router, then copy the setup script to the MikroTik terminal. The row turns from Waiting to Connected by itself. A router on the same network or an existing VPN:Same network / VPN.
RADIUS & WireGuard Infrastructure
RADIUS server, WireGuard tunnel and isolation for the selected router.
RADIUS server
Selected router
MikroTik / NAS peers
Routers connected through the WireGuard tunnel.
How isolation works on this router
Automatic isolation of overdue accounts (grace days, notice, reconnect after payment) is set inBilling & Payment Preferences.
RouterOS isolation script
Safe to paste again: each rule is found by its comment and added or updated; nothing is removed first.
Isolation template for this router
The template decides the isolated speed, the allowed sites and where web pages are sent. Routers without a choice use the default template.
How ONE-KONEK reaches the MikroTik routers, reads and syncs the PPPoE accounts, and monitors them. The settings are below.
Limits on automatic changes to the network (isolation, reconnection, change windows). The settings are below.
Router on the same network or an existing VPN
Five short steps with a certificate check. For remote routers with RouterOS 7, use the Routers tab: one script does it.
Server readiness
Checked once and reused for every device. Saved settings alone never count as ready.
What do you want to connect?
Continue a setup
Other PPPoE servers and devices
PPPoE is how a subscriber logs in, not a way to manage a device. Only RouterOS routers are configured directly; everything else is described honestly below.
Setup script
No working management connection yet? An authorized administrator runs this once on the router: WinBox > New Terminal > paste. It changes only items marked "ONE-KONEK ENROLL" and contains a one-time password that is replaced at the first successful test.
The first read changes nothing on the router.
Plans and router profiles
Suggestions come from the profile name and its real speed limit, never from the price. Review each one; the router profile itself is not changed.
Accounts on this router
Matched by router and username. Linking never resets passwords, bills customers, changes status or drops sessions.
Which subscriber?
Subscriber
1Router and plan
2Account
Advanced: fixed IP
Open IP addresses (General Settings)3Set up the modem / ONU
4Verify connection
"Connected" only when the router or RADIUS shows a live session for this account.
OLTs
Huawei, ZTE, VSOL, C-Data, BDCOM, Fiberhome, SmartOLT cloud or any brand by SNMP. ONU status, authorization and outages are in Network > OLT & ONU.
Signal and outage thresholds
Used by the OLT & ONU page and the Monitoring Board.
IP addresses
Subnets, router address pools, fixed IPs and what is really in use. Problems are shown for you to fix; ONE-KONEK never moves a customer to another address by itself.
| Address | State | Recorded for | Live session | Router / scope |
|---|
Subnets
| Subnet | Purpose | Router / scope | Use |
|---|
Address pools on the routers
Read from /ip pool (read-only). Use is counted from live sessions.
| Router | Pool | Ranges | Use | Read |
|---|
Reservations (devices, gateways, servers)
Customer fixed IPs are set on the subscriber's PPPoE account; they appear under Addresses.
| Address | Label | Kind | Router / scope |
|---|
Is this address free?
The same check runs when a fixed IP is given in Connect Device.
Payment gateways
Online payments subscribers make in the portal. Set up a gateway with its API keys; payments are posted to the bill automatically.
Where are the API keys kept?
Keys typed in a gateway's setup are stored encrypted on the server and are never shown again (only their last 4 characters).
Keys can also stay in the server environment file (backend/.env); a key typed here is used first.
| Provider | Sandbox (testing) | Live (real payments) |
|---|---|---|
| Xendit | XENDIT_TEST_SECRET_KEY, XENDIT_TEST_WEBHOOK_TOKEN |
XENDIT_LIVE_SECRET_KEY, XENDIT_LIVE_WEBHOOK_TOKEN |
| PayMongo | PAYMONGO_TEST_SECRET_KEY, PAYMONGO_TEST_WEBHOOK_SECRET |
PAYMONGO_LIVE_SECRET_KEY, PAYMONGO_LIVE_WEBHOOK_SECRET |
| Maya Business | MAYA_SANDBOX_PUBLIC_KEY, MAYA_SANDBOX_SECRET_KEY |
MAYA_LIVE_PUBLIC_KEY, MAYA_LIVE_SECRET_KEY |
Sandbox is for testing only: subscribers never see sandbox gateways, and test payments are never posted to a bill.
Manual payments, QR codes & bank accounts
Accounts subscribers can pay into directly (GCash, Maya, QR Ph, bank transfer) and the instructions they see. Staff confirm these payments in Payments & Collections.
Add one entry per account. The account name, number, QR image and instructions are shown in the subscriber portal and on payment reminders.
Connected services
Every integration ONE-KONEK supports, with its real status. Items marked "Not available yet" still need development and are never shown as connected.
Webhooks & API access
Receive payment notices from providers, send signed event notices to your other systems, and manage API keys.
Incoming: payment provider webhooks
Copy each address into the provider dashboard. Every request is verified (token or signature) before it is used, repeats are ignored, and payments are re-checked with the provider before posting.
Outgoing: send events to your systems
ONE-KONEK posts a signed JSON message to each address when a chosen event happens. Failed deliveries are retried automatically.
How receivers verify the signature
Each request has these headers:
X-OneKonek-Event— the event name, e.g. payment.postedX-OneKonek-Event-Id— unique per event; store it and ignore repeatsX-OneKonek-Timestamp— Unix time in secondsX-OneKonek-Signature—v1=+ HMAC-SHA256 oftimestamp + "." + raw bodyusing the endpoint secret
Reject requests older than 5 minutes or with a signature that does not match.
Delivery history & troubleshooting
Every attempt is kept with its result. Re-sending an event that can post a payment or change a service asks for confirmation first.
API keys
For other systems that call the ONE-KONEK API. A key has the same permissions as your account, is shown only once, and can be revoked at any time.
Invoice, receipt & message preview
How your saved company details and logos appear to subscribers. Update logos above and company details in Company & ISP Profile.
Notification identity
Sender name, reply-to email and the message footer are edited in Notifications & Communications.
Edit sender & templatesWho can change settings
These rules are enforced by the server. Every saved change is recorded in the history below without secret values.
Maps & Coverage
Map provider, default map location, default address on new forms, address lookup, coverage rules and who can see subscriber pins. Only a Super Administrator can change these.
Configuration History
Versioned changes, approvers, deployment state, rollback points, and audit references.
No configuration versions loaded
Approved backend configuration versions and rollback evidence will appear here.