Unauth failed error in Omada Controller OC300
We are currently experiencing an issue with the Hardware Controller OC300 where we encounter an "Unauth Failed" error when attempting to unauthorize a client from the captive portal. After this error occurs, we are unable to remove the client from the system. However, the network remains properly connected through the Omada Controller, and we have verified that there is no connectivity issue by performing a ping test.
This problem has occurred multiple times, and our temporary solution has been to restart the VPN and Omada Controller, which resolves the issue for about an hour. However, after that, the same error occurs again. I have previously posted this issue on the TP-Link Business community but have not received a solution yet. I have attached pictures of the Hardware Controller for your reference
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thank you, @Hank21, for your cooperation. We wanted to inform you that we have successfully resolved the issue related to the "Unauth failed error" in the Omada Controller OC300.
It was determined that the error occurred when attempting to unauthorized a client for the portal.
Upon careful observation by our team, we identified a conflict with the static IP addresses in our network. By resolving this conflict, we were able to resolve the "Unauth failed error" in the Omada Controller.
- Copy Link
- Report Inappropriate Content
AnnusKhan wrote
We are currently experiencing an issue with the Hardware Controller OC300 where we encounter an "Unauth Failed" error when attempting to unauthorize a client from the captive portal. After this error occurs, we are unable to remove the client from the system. However, the network remains properly connected through the Omada Controller, and we have verified that there is no connectivity issue by performing a ping test.
This problem has occurred multiple times, and our temporary solution has been to restart the VPN and Omada Controller, which resolves the issue for about an hour. However, after that, the same error occurs again. I have previously posted this issue on the TP-Link Business community but have not received a solution yet. I have attached pictures of the Hardware Controller for your reference
Hi @AnnusKhan
May I have the screenshots of the whole page when you encounter this error? And please share some screenshots of your portal page to us.
For these clients, may I know whether they are wireless client, or they are wired client?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @AnnusKhan
Thanks for sharing. Could you please help to confirm whether there were any EAP disconnected from the controller when you encountered this issue? Please go to Devices page to check the EAP status. You can also share the screenshot of the EAP status page.
If rather, could you also try to test whether the communication between the controller and EAP was disconnected?
- Copy Link
- Report Inappropriate Content
Hi @AnnusKhan
To assist you better, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID TKID240515661, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
Thank you, @Hank21, for your cooperation. We wanted to inform you that we have successfully resolved the issue related to the "Unauth failed error" in the Omada Controller OC300.
It was determined that the error occurred when attempting to unauthorized a client for the portal.
Upon careful observation by our team, we identified a conflict with the static IP addresses in our network. By resolving this conflict, we were able to resolve the "Unauth failed error" in the Omada Controller.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 640
Replies: 5
Voters 0
No one has voted for it yet.