After upgrade of Omada Software Controller V5.7 to V5.8.4 Windows no data is shown (using port 443)
I had my Windows Software controller working on port 443 until now, so up to and including 5.7.4. version.
After upgrading from 5.7.4 to 5.8.4 I started seeing blank screens.
For example, the new global dashboard was empty.
I then uninstalled the entire controller software 5.8.4.
Then I reinstalled the software.
And chose to restore a backup during the installation.
As a result, everything seemed to work again.
I just had to install a new certificate and change the default port 8043 to 433.
After adjusting the port, I had blank screens again.
I then did everything all over again, only this time I did not change the port to 443, and now everything works normally.
I suspect there is still a bug in working over port 443, can someone confirm?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @dbergloev ,
Thanks for reporting this issue to our community!
The support engineer has located the issue is a Browser Caching issue, and it can be resolved by clearing the cache of the browser or changing different browsers.
And this issue will also be continuously optimised in subsequent versions of the controller.
- Copy Link
- Report Inappropriate Content
I am also currently running Controller V5.8 and have tried changing the port to 443 without similar problems.
Have you checked to see if there are any devices on your network or server that are already occupying port 443?
- Copy Link
- Report Inappropriate Content
There are no network services on that server using port 443.
Here are some screenshots how it looks like when running on port 443, so a lot of menu's have blanks as a result.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@cmcouwenb I am having the same issue, nothing to do with changing port, I installed the 5.8.4 update and when Omada started I am missing all the data, all I have is 3 tabs on the side.
I have no idea what happened, did you find a fix for the issue?
Patrick
- Copy Link
- Report Inappropriate Content
Dear @cmcouwenb
Have you tried to clean the web browser cache? Or try another web browser, like google chrome incognito mode?
- Copy Link
- Report Inappropriate Content
I have the exact same problem. I had my docker set to ":latest", and got the 5.8 update, which broke everything. I thought it may have been because I updated from 5.6, skipping 5.7 in between. I tried reinstalling it, but same. I then tried installing docker and Omada Controller on an amd64 test server (main server was arm64), but I got the same result. Now I am running 5.7 without any issues.
- Copy Link
- Report Inappropriate Content
Dear @dbergloev ,
Thanks for reporting this issue to our community!
The support engineer has located the issue is a Browser Caching issue, and it can be resolved by clearing the cache of the browser or changing different browsers.
And this issue will also be continuously optimised in subsequent versions of the controller.
- Copy Link
- Report Inappropriate Content
I am still experiencing this issue on Safari and Chrome browsers (cache cleared) with versions 5.8.4 and 5.9.9. Version 5.7.4 works fine. Any advise on how to solve this issue? Thank you
- Copy Link
- Report Inappropriate Content
Hi @RobGob ,
RobGob wrote
I am still experiencing this issue on Safari and Chrome browsers (cache cleared) with versions 5.8.4 and 5.9.9. Version 5.7.4 works fine. Any advise on how to solve this issue? Thank you
When you use controller 5.9.9, is the error message(404/the page you visited does not exist) just like this post showing on Global page?
Or is there any other error messages reported?
Can you share a screenshot?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1657
Replies: 9
Voters 0
No one has voted for it yet.