Wi-Fi System Error - Mws::Controller::Manager: the controller DPN document is not accepted.

[cffmnk]

I'm trying to connect KN-1111 as Extender to my KN-3811 using Wi-Fi System. KN-1111 shown in "Extenders available for adding to the Wi-Fi System" but on "Acquire" nothing happens.

Error from KN-3811 system log
Mws::Controller::Manager: the controller DPN document is not accepted. 

I've tried to reset both devices, tried different os versions, reinstalled wifi system component,  tried both ethernet and wps connection methods. No success.

[Aleksei Kotenko]

ok, lemme give a bit more context: I have two routers, one bought in Germany and another one is from the CIS. From the CIS one doesn't allow to build mesh anymore, so I switched EU one as the main router and the CIS one as a repeater; the setup now works.

P.S. The first setup worked on Feb 25 once I set it up, but after backup restore (yep, I did some shit and had to restore my routers), the mesh was not restored and had to be configured from scratch. The chatgpt says the DPD document and Mws::Controller::Manager are the components of Keenetic Cloud, so I may assume because of keenetic splitting into two companies (google netcraze), the old CIS-based devices now have issues.

[Aleksei Kotenko]

Same for me

[Leg4te]

Same problem!

Reset & downgrade firmware doesn’t help!

also, adding extender doesn't work through the netcraze app!

[Leg4te]

I found a solution. You need to connect to the main router via ssh and connect the candidate with the command: mws acquire <candidate MAC> eula-accept no-update

The MAC address you need to specify is the one that the candidate gives over the wire, and not the one on the device's sticker

Edited September 1, 2025 by Leg4te

[Tolik]

Leg4te

You're the man! God bless you for your brilliant way to acquire an extender. It did work!

[lyonya]

On 9/1/2025 at 10:04 AM, Leg4te said:

I found a solution. You need to connect to the main router via ssh and connect the candidate with the command: mws acquire <candidate MAC> eula-accept no-update

The MAC address you need to specify is the one that the candidate gives over the wire, and not the one on the device's sticker

do i need to connect via ssh as root ? bc with admin ((config)>) gives an error
(config)>  mws acquire 1a:7e:2c:f1:xx:xx 
Command::Base error[7405602]: argument parse error.

[eralde]

2 hours ago, lyonya said:

do i need to connect via ssh as root ? bc with admin ((config)>) gives an error
(config)>  mws acquire 1a:7e:2c:f1:xx:xx 
Command::Base error[7405602]: argument parse error.

If for some reason the MAC address does not work you also can use candidate's cid as the candidate identifier. Device's cid can be found in the show identification command output.

If you press Tab after entering mws acquire, there should be some autocomplete options available.

 

[schek]

Hello, everyone!

I would like to share how I solved this issue when adding an extender to a Wi-Fi system. I have Keenetic Hopper (Main Router) running OS 4.3.6.3 and a new Keenetic Buddy 6. The Problem: The "Acquire" button did nothing in the Web UI, and the system log showed the error: "The controller DPN document is not accepted".

Here is the step-by-step solution that worked for me:

1. Log in to your main router's web interface (192.168.1.1). Go to Management -> Users and Access. Ensure that your 'admin' user has SSH and Telnet permissions enabled (Telnet uses port 23 by default).

2. Open your terminal (I used Linux, but PowerShell/CMD works too) and connect to the router: "telnet 192.168.1.1" Enter your admin credentials to log in.

3. Manual Acquisition. Type the command "mws acquire " (with a space) and press Tab. The CLI should automatically show the MAC address of your Buddy/extender. Complete and run the command: "mws acquire <YOUR_MAC_ADDRESS> eula-accept no-update"

4. Wait and Save. After a short moment, the Buddy appeared as "Acquired" in the Web UI. To make sure the settings persist, run this command in the telnet session: "system configuration save"

5. Update Firmware. Once the node was active, I went to the "Wi-Fi System" tab in the Web UI and triggered an OS update for the nodes. After about 5 minutes, everything was fully synced and running the latest version.

6. Access Extender. I can now access the Buddy's local web interface directly by clicking its IP address link in the main router's Wi-Fi System list.

I hope this helps anyone struggling with the same DPN document error!