jks

No, that's not what LED #1 double-flashing every second means. That is the standard Debian/Linux heartbeat pattern, i.e. what Debian shows before the Kiwi software starts running (or fails to start). This should be clearly described in the operating info: http://kiwisdr.com/info/#id-leds

I haven't even released v1.696 yet that implements the new LED pattern that indicates FPGA initialization failure: http://kiwisdr.com/info/#id-fpga (update: v1.696 has been released).

Glad it's running again for you though.

This question is simply not valid. It doesn't take into account the architectures and evolution of the current Kiwi and owrx systems and how it is not possible to "move" between them. The Kiwi started with some owrx waterfall, sound and user interface Javascript code back in 2014-2016. But things diverged quickly from there.

owrx runs on a pc. And the Kiwi's Beagle + FPGA is not a pc. That's by design and the root of the issue.

Okay, that wasn't too difficult. Fix will be in the next release (v1.696). It will be a new file called ~/kiwi.config/opt.console.local

I turns out that setting is essentially bogus. You can override it easily. I didn't think it through carefully enough when implementing it.

Even if you're connected as admin from the Internet simply go to the "security" tab and set the switch that says Restrict console connections to the local network? to No. Then refresh the page, then go to the console tab and click Connect. It should now work.

The problem is that setting can't be in the admin interface. Otherwise it can always be defeated. This feature needs a setting similar to the one that disables the console tab entirely by creating a file called ~/kiwi.config/opt.no_console

See here: http://kiwisdr.com/info/#id-opt-dot

Yes, I can do that. Added to my infinite list of things to do..