OC300 web interface unavailable
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I buy an Omada OC300 and two EAP610-Outdoor.
On first login, a few weeks ago, I connect the two APs to the controller. Today I logged into the controller to set a static IP and change the default HTTP/HTTPS port. So, I went to "Settings > Controller", made the changes and saved.
After this, the OC300 web interface is unreachable (on all ports, even the new ones). If I keep to refresh the browser page "https://<OC300 IP>" I sometimes see a screen that says: "Starting up ..." "This will take three to four minutes. Please wait. Keep the device powered on during processes." (see attachment) but more than two hours have already passed.
What is going on? How can I solve this problem?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@trigg3r is it possible you assigned it a static IP that is already in use by another device?
My suggestion would be to statically configure a laptop on the same subnet as the IP you assigned to the OC300. Disconnect the OC300 from the rest of the solution, and connect only the laptop to it. Reboot the OC300.
While that is going on you can run a
C:>\ ping -t ip,addr,ess,oc300
and wait for it to start to respond. Then you can try to access the web page. If it doesn't respond, you may have to factory reset the OC300 and start with a fresh config. I assum there is a non-Omada router or modem/router in the mix as well? If so, I highly recommend NOT using static IP's for your controller, but instead using a DHCP IP Address Reservation on the router (or DHCP server) that maps a fixed IP to your controller instead.
- Copy Link
- Report Inappropriate Content
Also try a different browser. I found this exact same thing to happen when I used Safari or Edge v1 (non chrome version)
Firefox works 100% for me on the OC200
- Copy Link
- Report Inappropriate Content
Thank you @d0ugmac!
I'll try what you suggest, but I'm pretty sure that's not the problem (ping stops responding every time the OC300 reboots).
The DHCP server is a pfSense. I can configure a static lease but if I can be honest this is not a point in favor of OC300 because nowadays I can't think that there are problems to configure a static IP ...
- Copy Link
- Report Inappropriate Content
Thaks @Philbert but this was the first test I did
- Copy Link
- Report Inappropriate Content
@trigg3r if the device is in a constant reboot loop, you most likely have a corrupt configuration database and you will need to factory reset the controller and rebuild it.
- Copy Link
- Report Inappropriate Content
Ok ... after a factory reset and changing settings one by one, I can tell that the problem occurs when I change the port on which HTTP (8080) and HTTPS (4433) respond.
- Copy Link
- Report Inappropriate Content
@trigg3r I know there have been some tickets around changing the default GUI access ports for the Omada Controllers. When the next (5.9) firmware drops for the OC300 this may be fixed...you'll need to check the release notes. Glad you found the issue though! You could also scan the Requests & Suggestions forum to see if others have reported a problem when changing from default ports.
- Copy Link
- Report Inappropriate Content
Thanks @d0ugmac1! Not a big deal in this case. I changed the ports more out of habit than out of real necessity ;-)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 991
Replies: 8
Voters 0
No one has voted for it yet.