Add a MikroTik Server

Connect Zettabit to your MikroTik router for PPPoE user management.

Prerequisites

Before adding a server, ensure:

1. Router is accessible - You can reach the router from the internet or your network
2. API is enabled - The RouterOS API service is running
3. Credentials ready - You have a username and password with API access

Preparing Your MikroTik Router

Enable the API Service

On your MikroTik router, enable the API:

/ip service enable api

Or for SSL (recommended):

/ip service enable api-ssl

Create an API User (Recommended)

Create a dedicated user for Zettabit:

/user add name=zettabit password=YOUR_SECURE_PASSWORD group=full

For better security, create a limited group:

/user group add name=zettabit-api policy=read,write,api,!ftp,!local,!ssh,!telnet,!winbox,!web,!reboot,!sniff,!test,!password,!policy,!sensitive
/user add name=zettabit password=YOUR_SECURE_PASSWORD group=zettabit-api

Check API Port

Verify which port the API is using:

/ip service print where name~"api"

Default ports:

• API: 8728
• API-SSL: 8729

Adding the Server in Zettabit

1. Navigate to Network > Servers

Click Network in the sidebar, then Servers.

2. Click Add Server

Click the Add Server button.

3. Fill in Connection Details

4. Test Connection

Click Test Connection to verify settings before saving.

A successful test shows:

• Router identity
• RouterOS version
• Connection latency

5. Save the Server

Click Save to add the server.

Connection Settings Explained

Host

The address Zettabit uses to reach your router:

• Public IP: If router is on the internet (e.g., “203.0.113.50”)
• Private IP: If Zettabit is on the same network (e.g., “192.168.1.1”)
• Domain: If you have DNS configured (e.g., “router.myisp.com”)

Port

SSL Certificate

If using API-SSL with a self-signed certificate:

• Zettabit accepts self-signed certificates by default
• For production, use a proper SSL certificate

After Adding a Server

Once added, Zettabit will:

1. Connect and verify credentials
2. Fetch existing PPPoE profiles
3. Begin monitoring server status
4. Be available for client assignment

Troubleshooting

”Connection refused”

• API service is not enabled
• Firewall blocking the port
• Wrong port number

”Authentication failed”

• Incorrect username or password
• User doesn’t have API access
• User is disabled

”Connection timeout”

• Router is unreachable
• Network path is blocked
• Wrong IP address

”SSL handshake failed”

• Using SSL port (8729) without enabling SSL
• Certificate issues
• Try disabling SSL temporarily to test

Security Best Practices

1. Use API-SSL - Always encrypt API traffic
2. Strong passwords - Use unique, complex passwords
3. Limit access - Restrict API to known IP addresses
4. Minimal permissions - Only grant necessary access
5. Regular rotation - Change passwords periodically

Editing a Server

To modify server settings:

1. Click on the server in the list
2. Click Edit
3. Update settings
4. Test connection
5. Save changes

Deleting a Server

To remove a server:

1. Remove all client assignments first
2. Click the Delete button
3. Confirm deletion

Note: Deleting a server doesn’t affect the actual router, only Zettabit’s record.