As many of you have already findout, there's a bug in the currently available notochordOS image. Under some situations, when you try to assign an existing WIFI network you might end up with a situation where neither the raspberry as Access point nor the external WIFI connection will work. Forcing you to access using an ethernet cable or manually editing configuration files in the SD card.
Of course we want to avoid that, the remote console should be the only configuration entry point needed. And it should be available out-of-the-box for each notochordOS system that you flash.
One common issue several users are finding happens when, for some reason, it fails to connect to an external WIFI network set by the user. It may even be due to a user error entering the SSID or password. It's tricky for the server behind the remote console to check that a particular SSID/password pair is valid, because it should drop the current WIFI connection making the remote console unresponsive..
The current approach we are implementing is creating an script that gets executed at boot, which will first check the validity of the external WIFI network, and fall back to the Access point mode if there's a problem connecting to that one.
I just wanted to let you people know why is this new version of the notochordOS not available yet. And in case you have any observations or suggestions on another method to test an external WIFI network while keeping the remote console usable
@zaanen @TackY @Jump