rz3dvp

You can build it manualy on SSH console connection.
For first time try use ./up script:
- connect to KiwiSDR console via SSH (you can use Putty for Windows) with debian user
> sudo su (type debian password again)
> cdp
> ./up
and wait about 40 min for build current version

if problems didn’t goes you can build KiwiSDR software from Github and then copy config from old version... look this post for fix serious problems: http://forum.kiwisdr.com/discussion/comment/8480#Comment_8480

Hello friends,
As you probably know know, for normal start BBG board need fast +5V voltage rise from PSU, if you use powerful transformer PSU you can have problem with autostart KiwiSDR after power outage.
Info from https://groups.google.com/forum/#!topic/beagleboard/aXv6An1xfqI[151-175]: "The BBG uses the TPS65217 power management IC. Per the data sheet, it will not turn on if the applied power has a ramp of greater than 50 mSec."

I have this problem with one of my PSU's, when BBG don't start after power lost and I installed device with 10s delay for allow power from PSU and it was very helpful for me:
https://www.ebay.com/itm/LED-Home-Automation-Delay-Timer-Control-Switch-Relay-Module-Digital-display-PLC/252867596893?ssPageName=STRK:MEBIDX:IT&var=551880757238&_trksid=p2060353.m1438.l2649



Maybe this info was halpfull for something else.

73! Yuri

Hello friends,
As you probably know know, for normal start BBG board need fast +5V voltage rise from PSU, if you use powerful transformer PSU you can have problem with autostart KiwiSDR after power outage.
Info from https://groups.google.com/forum/#!topic/beagleboard/aXv6An1xfqI[151-175]: "The BBG uses the TPS65217 power management IC. Per the data sheet, it will not turn on if the applied power has a ramp of greater than 50 mSec."

I have this problem with one of my PSU's, when BBG don't start after power lost and I installed device with 10s delay for allow power from PSU and it was very helpful for me:
https://www.ebay.com/itm/LED-Home-Automation-Delay-Timer-Control-Switch-Relay-Module-Digital-display-PLC/252867596893?ssPageName=STRK:MEBIDX:IT&var=551880757238&_trksid=p2060353.m1438.l2649



Maybe this info was halpfull for something else.

73! Yuri

Hello friends,
As you probably know know, for normal start BBG board need fast +5V voltage rise from PSU, if you use powerful transformer PSU you can have problem with autostart KiwiSDR after power outage.
Info from https://groups.google.com/forum/#!topic/beagleboard/aXv6An1xfqI[151-175]: "The BBG uses the TPS65217 power management IC. Per the data sheet, it will not turn on if the applied power has a ramp of greater than 50 mSec."

I have this problem with one of my PSU's, when BBG don't start after power lost and I installed device with 10s delay for allow power from PSU and it was very helpful for me:
https://www.ebay.com/itm/LED-Home-Automation-Delay-Timer-Control-Switch-Relay-Module-Digital-display-PLC/252867596893?ssPageName=STRK:MEBIDX:IT&var=551880757238&_trksid=p2060353.m1438.l2649



Maybe this info was halpfull for something else.

73! Yuri

http://195.222.165.118:8073/ my AirBand KiwiSDR with passive mixer (QTH near SVO airoport Moscow).

Hello guys, I try published 2 KiwiSDR receiver with using one real IP and using same port (8073) with Raspberry Pi3 and Nginx.
My topology:


On first step I created 2 different domain name in DNS, on my example it's kiwi.mydomain.com and kiwi2.mydomain.com (A or CNAME) with my real IP address 142.93.129.90
Second step, - on KiwiSDR1 configure SDR.hu registration to "Yes" and on connection add Next Kiwi URL redirect to http://kiwi2.mydomain.com:8073, on KiwiSDR2 configure SDR.hu registration to "No"
Next step, - install and configure Nginx on Raspberry Pi3:

• sudo apt update && sudo apt -y upgrade
  
• sudo apt install -y nginx
  

change Nginx config file (my example):

• sudo nano /etc/nginx/sites-available/default
  

upstream kiwi1 {
server 192.168.1.3:8073;
server 192.168.1.4:8073 backup;
}

upstream kiwi2 {
server 192.168.1.4:8073;
server 192.168.1.3:8073 backup;
}

server {
listen 8073;
server_name kiwi.mydomain.com;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header realip $remote_addr;

location / {
proxy_pass http://kiwi1;
}
}

server {
listen 8073;
server_name kiwi2.mydomain.com;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header realip $remote_addr;

location / {
proxy_pass http://kiwi2;
}
}

I use second KiwiSDR for backup main in upstreams for best site stability.

Test configure: sudo nginx -t and if it's correct restart Nginx: sudo /etc/init.d/nginx restart, if you don't want close established connections you can use sudo /etc/init.d/nginx reload

Final step, - published Raspberry Pi3 on router like one of the KiwiSDR and start for testing connection.

The End

Troubles:
KiwiSDR see real IP of connected clients but don't use time limits for it:


Maybe any ideas how fix it?

PS you can start gzip compression on Nginx for low bandwidth connection.
PSS off course you can use more than 2 KiwiSDR with simple correction of this config.

http://195.222.165.118:8073/ my AirBand KiwiSDR with passive mixer (QTH near SVO airoport Moscow).