@Fae 

 

Thanks I looked at the FAQ.

 

The EAP is and has always been working despite being disconnected from the controller, it has internet and those with valid vouchers can still connect.

 

The EAP IP is 192.168.0.190 it get's it IP from Router2 (192.168.0.1) which Connects to Router1 (192.168.254.254) for the internet.

 

Step 3 Ping - just times out

 

Step 4 - they are not in the same subnet so went to Step 5

 

Step 5 - there were about 8 entries for Javaw.exe so I tidied it up and checked private and public

 

I then restarted the pc - I am using nssm to run Omada Controller as a Service on Windows 10

 

Checked the EAP was still disconnected and stopped the Service

 

Step 6 Ran the discovery utility from PC running the Omada Controller - didn't find EAP - even with given IP address

 

Step 6 Ran the discovery utility from PC on same subnet as EAP - finds the EAP but when I try to "manage" the controller will not adopt it - Adopt Fails

 

I tried to look at the packets but I couldn't find anything on port 29810 as described - is there an easier way to check this ? I looked in the Log file for discovery but that doesn't say much...

 

Thanks

 

@Fae 

 

Hi

 

Think I understand - I tried it two ways:

 

1) using the admin account and password for the controller software and

2) using the windows log in account and password for the remote pc

 

Neither worked 

 

...

 

OK found the Device Account in Settings from your reply and used the password from there...

 

It says it succeeded but when I check it they're still disconnected!

 

I'll try it a couple more times using the correct account and password

 

It succeeds on the discovery utility but when I check again on the Omada Controller via web or remote pc the EAP is still disconnected :(

 

...

 

 

Another odd thing I've noticed when I try to run the Omada Controller app web interface it doesn't like it... I normally have to restart the remote pc to get it to run it and let me log in... 

 

 

Update:

 

I tried the Discovery Utility on the remote pc and it is now finding the EAP

 

I try to adopt it but Adopt Times Out...

 

@Fae 

Hi again...

 

Lot's of fiddling, but after a quick RTFM session: 

 

1 Turned off the NSSM - service manager for Omada Controller

2 Killed the mongo DB process - to release the ports stopping the Omada Controller starting again

3 Ran the Omada Controller

4 Deleted second site I have set up - see below - does this generate a 2nd Device Password?

4 Forgot the EAP

5 Left the Omada Controller running on remote pc and disconnected remote session

6 Ran Omada Discovery Utility on local pc - same subnet the EAP are connected to - discovered my EAP - I actually have 2

7 Managed EAP 1 setting succeeded 

8 Managed EAP 2 Failed - maybe a bug here - My Omada Controller software had a different password for each device (maybe I was fiddling to see if I could isolate a Site on one device at some time) but they both seem to use the password of the first device... which then appears to succeed on the Discovery Utility but doesn't gel when returning to the Omada Controller app

9 Logged back in to remote pc - provisioned EAP 1 and Connected OK - EAP 2 failed - tried forgetting that one

10 Tried discovering EAP 2 again... wasn't having it - pulled the LAN cable to force a reboot of EAP 2

11 Omada Controller discovered EAP 2 itself (Managed by Other's I think it said) - Adopted it using the password of Device EAP 1

12 All appears to running ok now - and I have only one password for both EAP's (I think)

 

I'll switch the service back on later but I cannot imagine that will cause any problems

 

@Fae 

 

Not quite there yet :(

 

Bit weird - running the Omada Controller - omada-start.jar ... the Omada Controller rediscovers the EAP's, provisions and connects

 

When I use the NSSM service, for some reason it doesn't rediscover the EAPS... they remain disconnected

 

I disabled the NSSM OmadaControllerService and installed it again - creating service: OmadaControllerServiceII but that doesn't work either.

 

I can run Omada Controller as a start up in Windows 10 but if there is a power outage (we have many) it won't run automatically whereas the NSSM does.

 

I would have thought LocalSystem had more permissions than a normal Administrator account - so not sure what's going wrong ... ?

 

I've checked the firewall settings for javaw.exe - and they seem ok

 

Further Info:

 

RunTime Used By Stand Alone Omada Controller
C:\Program Files\Java\jre1.8.0_301\bin\javaw.exe - 64bit

 

RunTime Used By NSSM Service
C:\Program Files (x86)\Common Files\Oracle\Java\javapath_target_2046953\javaw.exe - 32bit

 

I can also stop the OmadaControllerServiceII, kill the mongo db process and then run stand alone Omada Controller and it will rediscover the EAPS itself...

 

 

 

 

@Fae 

 

Thanks - the next day one of the EAP's annoyingly disconnected again!

 

Fortunately I had a back up from a couple of days prior to the issues arising and after doing a manual reset on both EAP's I re-adopted them both and restored the site settings that appears to have sorted things out.

 

So I think that is probably the "recommended solution"

 

One thing I noticed is that edge browser automatically disables files with cfg extension that Omada Controller creates for back-ups

 

Couple of other questions if you would:

 

Is there any progress on the Cloud Based Controller?

 

Is it possible for the Hotspot Operator to login via the cloud?

 

Does the Hotspot Operator login work?

 

The manual says:

 

For software controller

 

Visit the URL https://Omada Controller Host’s IP Address:8043/hotspot (for example:
https://192.168.0.174:8043/hotspot), and use the operator account to enter the hotspot manager

 

I created a test operator and tried a couple of times on mine but it kept taking me back to the admin login?