I can't unblock device on Omada 3.2.4 controller, "client does not exist"
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I have blocked a device by mistake, and when I go to "Insight" -> "Blocked" and click on "Unblock" an error message appears: "Client does not exist." I have an Omada v3.2.4 controller.
Can you help me?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Juasama
Below EAPs are not compatible with Omada controller V4.x.x and above.
EAP220 v1.0
EAP225 v1.0
EAP225 v1.0/2.0
All others are compatible.
If this issue only happens on that client, I believe it's a compatibility issue or some other unknown issue.
However, all of the EAP products above and the Omada V3 controller are end-of-life, I am afraid there will be limited support for this issue.
You may search for other solutions.
- Copy Link
- Report Inappropriate Content
Hi @Vincent-TP
I finally managed to unlock clients that were showing the error 'client does not exist' in Omada 3.2.4 via the web interface:
1. Access the Omada database with the Robo 3T management tool.
2. Run this to see which Collection has the 'isBlock' field set to 'true' (PDA locked).
db.getCollectionNames().forEach(function(coll) {
print("Collection: " + coll);
printjson(db.getCollection(coll).findOne({ "isBlock": true }));
});
3. List blocked clients:
db.statlifeclient.find({ "isBlock": true })
4. Unblock client:
db.statlifeclient.updateOne(
{ "mac": "XX-XX-XX-XX-XX-XX" },
{ $set: { "isBlock": false } }
)
5. Confirm that it was unblocked (isBlock set to false)
db.statlifeclient.find({ "mac": "XX-XX-XX-XX-XX-XX" })
I'm sharing this in case it can be of help to anyone.
- Copy Link
- Report Inappropriate Content
Hi @Juasama
Omada 3.2.4 is too old. What's the model number of the EAP products you're using?
Please forget the network on the client side and see if that helps.
- Copy Link
- Report Inappropriate Content
Hi @Vincent-TP
We have a controller version 3.2.4 with APs model:
EAP220 v1.0
EAP225 v1.0
EAP225 v1.0/2.0
EAP225 v3.0
EAP245 v3.0
and another controller version 5.4.6 with APs model:
EAP225 v4.0
EAP225 v5.0
EAP245 v4.0
EAP245 v5.0
I have tried forgetting the network but it doesn't work.
The problem exists in the controller with version 3.2.4, in the other we can block and unlock devices without problem, but I don't know if the APs we have in the 3.2.4 are compatible with controller version 4.5.6...
- Copy Link
- Report Inappropriate Content
Hi @Juasama
Below EAPs are not compatible with Omada controller V4.x.x and above.
EAP220 v1.0
EAP225 v1.0
EAP225 v1.0/2.0
All others are compatible.
If this issue only happens on that client, I believe it's a compatibility issue or some other unknown issue.
However, all of the EAP products above and the Omada V3 controller are end-of-life, I am afraid there will be limited support for this issue.
You may search for other solutions.
- Copy Link
- Report Inappropriate Content
Hi @Vincent-TP
I finally managed to unlock clients that were showing the error 'client does not exist' in Omada 3.2.4 via the web interface:
1. Access the Omada database with the Robo 3T management tool.
2. Run this to see which Collection has the 'isBlock' field set to 'true' (PDA locked).
db.getCollectionNames().forEach(function(coll) {
print("Collection: " + coll);
printjson(db.getCollection(coll).findOne({ "isBlock": true }));
});
3. List blocked clients:
db.statlifeclient.find({ "isBlock": true })
4. Unblock client:
db.statlifeclient.updateOne(
{ "mac": "XX-XX-XX-XX-XX-XX" },
{ $set: { "isBlock": false } }
)
5. Confirm that it was unblocked (isBlock set to false)
db.statlifeclient.find({ "mac": "XX-XX-XX-XX-XX-XX" })
I'm sharing this in case it can be of help to anyone.
- Copy Link
- Report Inappropriate Content
Thank you for the sharing, it's very helpful. 
I will share this with others if anyone had the same requirement.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 974
Replies: 5
Voters 0
No one has voted for it yet.