jks

Kiwi-1 does now offer the proxy service by request given that Kiwi-2 includes it by default. Just send me an email at support@kiwisdr.com and we can get it set up for you.

But people have also used their own proxy solutions as mentioned on various forum posts.

Hi Jeff,

Impossible for me to debug a weird problem like that without actually having access to the Kiwi.

Is the Kiwi server still running? That is, can you still connect to the admin page? If so, does it have an admin password set and can it be accessed from the Internet? Please email the link/URL and admin password to support@kiwisdr.com if so.

Alternatively, open the ssh port in your router and point it to your Kiwi so I can connect that way. email details as above.

Found a trivial way to do it. So will be part of the v1.801 release.

On the list of things to do, but very low priority.

I will be removing posts that talk about code security issues, weaknesses and strategy.

As of today (December 6) there are roughly 50 public Kiwis running v1.6xx and 120 running v1.7xx. I encourage everyone to update to v1.8xx as soon as possible. So far I've had to fix about 45 Kiwis manually.

v1.800 does not have the admin page reload problem. v1.800 fixes that problem. I want to state this so people don't get the wrong idea and start complaining to me (this happens all the time when inaccurate information is posted on the forum).

What you probably saw was the state of the sources in /root after a failed v1.8xx transition. When v1.7xx decides it needs to transition to v1.8xx a few things happen. Remember that it is running out of /usr/local/bin/kiwid and uses only the configuration files in /root/kiwi.config. So the state of the sources don't matter.

The sources in /root/Beagle_SDR_GPS are removed to make disk space in case the filesystem is full. Which is why we are in this mess to begin with. Then the new KiwiSDR repo is git cloned. Then a build of v1.8xx is attempted. If the build fails for any reason the source files will look like it is on v1.8xx. But if you cd; cd KiwiSDR; ms the log will show it still running on the v1.7xx out of /usr/local/bin/kiwid because the build never finished and installed the v1.8xx version. And if the Kiwi restarts same thing.

The image you download to create an SD card for re-flashing a BBG/BBB-based Kiwi-1 or Kiwi-2 has been updated from Debian 11.9 to 11.11 and Kiwi software release v1.690 to v1.800.

Full instructions here: http://kiwisdr.com/info/#id-net-reflash

Yes, this problem can occur anytime in the future a Kiwi first crosses the barrier between pre- and post-v1.8xx. That's the point at which the git repo rebase occurs. So going from v1.699 to v1.8xx qualifies (even if v1.800 itself is skipped).

In your case it sounds like you have a Kiwi at a remote site with automatic updates turned off so you can more carefully control the update schedule (an entirely reasonable thing to do). It would be better if you just let me manually do the update to v1.800 now and save you any potential problems when you're next out there. Just set a temporary admin password and email it to support@kiwisdr.com and I'll be happy to do that.