Skip to content
MKController

Adoption Errors - How to Troubleshoot

Summary

This guide lists the 5 most common issues that prevent MikroTik devices from being adopted into MKController and explains how to identify and fix them. Includes RouterOS command examples and best practices.

1. Check RouterOS version

Symptom

Even after all the previous steps, adoption does not occur and the process gets stuck for several minutes at the creating VPN stage.

Diagnosis

The device may be running an old version of RouterOS that is incompatible with the required functions.

Steps to resolve

Check our supported RouterOS versions in the supported OS versions guide.

  1. Check the installed version and the one available in the configured channel:

    Terminal window
    /system package update check-for-updates

  2. The system will return something like:

    installed-version: 6.49.10

    latest-version: 6.49.12

    status: New version is available

  3. If an update is available, apply:

    Terminal window
    /system package update install

  4. Reboot the device:

    Terminal window
    /system reboot

2. Device Mode Advanced Disabled

Symptom

When running fetch, the log returns a device mode error:

Terminal window
{executing script script1 from winbox failed, please check it manually


failure: not allowed by device-mode (/tool/fetch line 1)}

Error on running MKController adoption script:

Device Mode terminal error

Terminal window
failure: not allowed by device-mode

Diagnosis

The MikroTik Device Mode is blocking functions such as fetch, hotspot, and scheduler.

Steps to resolve

  1. Run the following command to check if fetch and other options are “no” when they should be “yes”, like the image below:

    Terminal window
    /system device-mode print
    Confirm that the options are available

  2. Now run this command to activate Device Mode on your device:

    Terminal window
    /system device-mode update mode=advanced

  3. It is extremely important that you perform a “hard reboot” on your Device, by unpluging your MikroTik from the power outlet, completely cutting its power for a moment. Only after this type of reboot will the new settings be applied.

  4. After reboot, run the command from the item 1 above, and confirm that the options are available. After that try the adoption process again.

3. Missing PPP package

Symptom

Error when running the script:

expected end of command (line 6 column 33)

Diagnosis

The PPP package is not installed. It is required for creating the VPN tunnel used in adoption.

PPP Package is not insltalled

Steps to resolve

  1. Go to the MikroTik archive download site and download the package that matches your RouterOS version.

  2. Download the Extra Packages (.zip) file corresponding to your device’s architecture (e.g., mipsbe, arm, smips, etc.).

  3. Extract the .zip file on your computer and locate ppp.npk.

  4. Upload the ppp.npk file to the router:

    • In Winbox → Files tab, or
    • Via FTP or SCP

  5. Once the upload is complete, reboot the router:

    Terminal window
    /system reboot

    After reboot, the PPP menu should appear in WebFig/Winbox.

4. Issues when running the script

Symptoms

  • Message: failure: could not resolve host name
  • Message: status: failed / reason: timeout

Diagnosis

The MikroTik has no internet access or cannot resolve DNS. Both are essential requirements for communication with MKController.

Steps to resolve

  1. Test internet connectivity:

    ping 8.8.8.8

    If there is no response, check:

    • default route configured

      Terminal window
      /ip route print

    • NAT or firewall rules → blocking outbound traffic

    • Physical connection with the provider

  2. Once the ping to 8.8.8.8 works, as shown below, test DNS:

    When ping 8.8.8.8 works, test DNS

    Run:

    Terminal window
    ping app.mkcontroller.com

    If it fails and the result is different from the example below, set DNS servers:

    If fails, set the DNS servers

    • Set DNS
      Terminal window
      /ip dns set servers=8.8.8.8,1.1.1.1
    • Reboot
      Terminal window
      /system reboot

5. Insufficient disk space

Symptom

Errors when running fetch or installing packages.

Diagnosis

MikroTik requires at least 2 MB of free disk space.

Steps to resolve

  1. Run the command below:

    /system resource print

  2. If free-hdd-space is less than 2 MB:

    /file print

    /file remove <id>

  3. Delete old files or unused packages, then retry adoption.

Still have questions?

Following these steps will eliminate the main issues in the adoption process.

If problems persist, contact our support team. We can check logs, review the script, and assist with specific adjustments.

Click here for any questions.