bbunge
Part of the Furniture
Good thought but pretty much wrong. These certs are generated internally on setup. Not retrieved from the web. Older routers such as the AC68U just take time to boot up.I don't want to disrupt the trouble-shooting, but I'd like to share my experience when first upgradin my aimesh units to 4.0.0.4.386: when resetting a node in order to add it, the wait-time before the node shows up in the available node list is abnormally long compared to earlier versions. I assume now that this is because of:
1) Added default log-in which supports BOTH http and https on lan. I believe that the node tries to fetch a valid https certificate after boot. The http-deamon has to timeout these requests, which can take many minutes, before it completes startup.
2) for https to work, correct time and dates may be required on both devices. On a reset node, this might be a faulting error.
3) Depending on build default settings (or inherited from last install), https might be set as required for wireless admin access. This might not be possible until a valid certificate is available online.
I recommend to login to the node and verify that either http-only is accepted as login via wifi, or that date and time is set manually after a reset. Also wait a lot (more than 8 minutes after boot).