@clintz, almost certainly this is a cabling issue. Wrong auto negotiation of a port's bandwidth can happen with unshielded and/or cheap cables.

@LucianoR, actually JAVA_HOME and JAVA_BIN should not be changed at all. Those are relicts from EAP Controller v2.7 which once had its JRE bundled and used different pathnames to start java under the...

@Rendel.Cruz, the mesh uses the 5 GHz band on Omada EAPs.

KiekerJan wrote However, I still get the general error at the end of the setup wizard. Perhaps the java version is not the issue here? Could be that something got screwed up before – probably some...

KiekerJan wrote I use the JAVA_HOME parameter in the Omada CONFIG file and have set that to JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64. Changing JAVA_HOME does not change the JRE, but it causes the...

KiekerJan wrote I have a Debian server where I have installed the software. I took the mongodb server 3.6 from the mongodb.org site. I made one change in the omada.properies file, to change...