Skip to Content
NetworkMikroTik Servers

MikroTik Servers

MikroTik servers are the backbone of your ISP network. Zettabit connects to your routers to manage PPPoE users and monitor connections.

What is a Server in Zettabit?

A Server represents a MikroTik router that handles your client connections. Zettabit communicates with these routers using the RouterOS API to:

  • Create and manage PPPoE users
  • Apply bandwidth profiles
  • Monitor connection status
  • Sync client credentials

Server List

The servers page displays all configured routers:

ColumnDescription
NameFriendly name for the server
HostIP address or hostname
PortAPI port (8728 or 8729 for SSL)
StatusOnline/Offline indicator
ClientsNumber of clients assigned
Last SyncWhen data was last synchronized

Server Status

StatusMeaning
🟢 OnlineConnection successful, API responding
🔴 OfflineCannot connect to the router
🟡 SyncingCurrently synchronizing data

How Zettabit Connects

Zettabit uses the MikroTik RouterOS API (not Winbox or SSH):

  1. API Port - Default is 8728 (plain) or 8729 (SSL)
  2. Authentication - Username and password
  3. Commands - Reads and writes PPPoE configurations

Security Recommendations

Use Dedicated API User

Create a separate user on your MikroTik for Zettabit:

/user add name=zettabit password=strong-password group=full

Enable API-SSL

For secure connections, enable API-SSL on your MikroTik:

/ip service enable api-ssl /ip service set api-ssl certificate=your-certificate

Restrict API Access

Limit API access to Zettabit’s IP addresses:

/ip service set api address=YOUR_ZETTABIT_SERVER_IP/32

Managing Servers

View Server Details

Click on a server name to see:

  • Connection settings
  • Assigned clients
  • Recent sync history
  • Error logs

Test Connection

Use the Test Connection button to verify connectivity without making changes.

Sync Now

Force an immediate synchronization with the router.

Troubleshooting

Server Shows Offline

  1. Check router accessibility - Can you reach the router from your network?
  2. Verify credentials - Are username/password correct?
  3. Check API service - Is the API enabled on the router?
  4. Firewall rules - Is the API port open?

Sync Failures

Common causes:

  • Network timeout
  • Router CPU overloaded
  • API rate limits
  • Invalid credentials

Check the server’s error log for specific messages.

Last updated on