Linux controller version 5.8.4 very slow using Safari browser
Linux controller version 5.8.4 very slow using Safari browser
Since upgrading to v5.8.4, the UI has gotten very slow. It's slow all around but I notice it most on the client list when I'm trying to sort on columns, refresh, search, etc. I have around 50 clients but there was never a performance issue prior to upgrading to the new code. I have found that a Chromium based browser performs much better, like Safari used to. I've cleared all cache/data on Safari and this doesn't resolve the issue.
The same behavior is observed on a 2021 MacBook Pro M1 Pro and a 2019 iMac with Intel 3.7GHz Core i5, both running Ventura 13.2 and Safari 16.3. I also tested the latest Safari technology preview (release 162) with same slow results.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I don't see this being an Apple issue when it worked perfectly fine on Safari prior to 5.8.4.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 cloud version of controller works just fine in Safari. So this is something that affects only local versions of Omada controller. Mine is Docker, not sure if people have same issue with OC200 controller.
- Copy Link
- Report Inappropriate Content
Thanks for info. I'm sure Safari has had updates since 5.8.4 was released, so it *could* be Apple..but the Cloud piece just above does beg the question about what's different in the backend between 'released' code versus the multi-tenant code that runs in the cloud that causes Safari to grind.
- Copy Link
- Report Inappropriate Content
and I thought it was just me......
Downloaded other browsers to find them working just fine. Have Firefox just for the controller until (hopefully) a fix is released.
- Copy Link
- Report Inappropriate Content
@Weza just tried this out, it's also very sluggish.
Weza wrote
@d0ugmac1 cloud version of controller works just fine in Safari. So this is something that affects only local versions of Omada controller. Mine is Docker, not sure if people have same issue with OC200 controller.
Switching to Chrome (sigh).
- Copy Link
- Report Inappropriate Content
Same issue here with OC200 (5.11.0) controller.
Mac Book Air M1 / 16 GB
Venture 13.4.1 (c)
Under Safari every click makes the process spin to 100% and hangs there till something is finished.
Under Chrome this isn't even noticeable.
This is really odd behavior in Safari that I cannot remember happening before. I do tend to switch platforms (Microsoft/Apple) and I've been accessing the OC200 web interface over Windows/Chrome these last couple of months, so I might have missed the exact moment when someone screwed up something.
- Copy Link
- Report Inappropriate Content
It began with 5.8.4. Sad to hear that it's still a problem in 5.11.x, though not surprised considering TP-Link didn't seem to care that much about it based on the response I got from support.
- Copy Link
- Report Inappropriate Content
I've checked the Javascript console in Safari. It looks like it launches a Webservice for the continuous communication between the controller and the browser using an old STOMP JS.
I noticed when looking at the device for instance list that the UI doesn't accept input, then refreshes and accepts input for a second or so.
Then I found this error popping up:
Unhandled Promise Rejection: Error: Navigation cancelled from "/" to "/empty" with a new navigation.
Could it be that Safari is more strict/secure than Chrome and other browsers? Then hopefully the bug will pop up in other browsers forcing TP-Link to fix the issue.
- Copy Link
- Report Inappropriate Content
I confirm the notable slowness with Safari, now with 5.12.7
The Omada controller has always been 2 notches below other controllers when it comes to fluidity.
The solution of using another browser is certainly not a solution.
- Copy Link
- Report Inappropriate Content
@SingletrackMind Hi! I found a solutions for this. Create a self-sign certificate for the Omada controller. Use this link for help https://www.youtube.com/watch?v=VH4gXcvkmOY&t=1332s. Upload the certificate and the private key to the controller and to you MAC . Problem no longer here for me.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 2608
Replies: 20
Voters 2
