Solution The Slow Broswer Issue On the Omada Hardware Controller v5.12
Solution The Slow Broswer Issue On the Omada Hardware Controller v5.12
This Article Applies to
Omada Hardware Controller v5.12
Issue Description/Phenomenon
We have noticed that some forum users are experiencing the Slow Browsing issue in the Controller GUI. This issue is manifests as a prolonged response time compared to all previous versions after logging in or clicking on any element within the Omada GUI, and this issue started occurring after upgrading the Omada Hardware Controller to v5.12.
Available Solutions
The R&D team has planned to optimize the slow browser issue in subsequent versions of Omada Hardware Controller, it will take some time as significant changes will be required. Please keep an eye on the new controller version release (subscribe to this post) for an update.
At present, you may refer to the following most to least recommended browser versions to access the Omada dashboard.
Chrome 69+ > Firefox 65+ > Edge 106+ > Safari
Thank you for your attention!
Feedback
If this was helpful, click the thumbs-up (Kudos) button below.
If there is anything unclear in this solution post, please feel free to comment below.
Thank you in advance for your valued feedback!
Recommended Threads
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, currently I am still getting OK performance from Chrome and the iphone App. It isn't very fast. I haven't tried safari again, but will add to my list of things to try.
- Copy Link
- Report Inappropriate Content
@Hank21 A workaround for this issue it to change or rename your clients using the Omada app.... Its seamless and there is no lag.
- Copy Link
- Report Inappropriate Content
@Hank21 Dark Reader add-on on Brave browser is cause of the problem in my case. Disabling for particular url solved the problem.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 9
Views: 8133
Replies: 13
Voters 5
