Re: Native OpenWebRX Client for Android
26 Settembre 2026 ore 19:49
Is there a way to connect it to our personnal OpenWebRX+ ? Like adding a standalone device ?
I'd suggest certbot by Lets Encrypt: https://certbot.eff.org/
It'll do everything for you besides check your email and plug the certs into your program.
1) If it does not work for you, reload OpenWebRX page while holding the SHIFT key.
2) If it does not work for you, check "Settings | Feature report" page to see what you are missing.
3) If it does not work for you, wait for a day or two, maybe it starts working or you figure it out.
4) If it does not work for you, create a separate forum thread and explain your problem there. Attach the logs, obtained with "sudo journalctl -u openwebrx". Do not paste the entire log into the message, attach it as a file instead.
Hello. Jakob, this one is mainly for you, as the maintainer of Receiverbook.
I run dxcontest.org, a free DX cluster site for radio amateurs. Next to every
spot there is a "WebSDR" button that opens the spotted frequency on a remote
receiver that actually covers it. We do not proxy or re-stream anything: the
button opens the receiver's own page in a new tab, already tuned to the
frequency and mode, so the receiver gets a normal visitor and the credit.
The list behind that button holds about 880 receivers today. Almost all of them
are KiwiSDRs, which John Seamons (ZL4VO/KF6VO) kindly allowed us to download
once per hour. The OpenWebRX and WebSDR ones we have added one at a time,
taking the bands from each receiver's own status.json or bandinfo.js, which
does not get us very far.
I would like to use the Receiverbook listing for that, and I would rather ask
than crawl the site. The OpenWebRX and WebSDR receivers are the ones we are
missing; we would leave the KiwiSDR entries alone, since we already have that
list. Is there a way you would be comfortable with: a JSON export, an endpoint,
or permission to fetch the listing pages?
Whatever we use, we would download it once per hour at most, from a single IP,
cached on our side; identify ourselves with a clear User-Agent including a
contact address; follow any rate limit or format you prefer and stop at once if
you ask us to; and credit Receiverbook as the source, with a link, both on the
page and in the list itself.
If the answer is no, that is fine and we will leave it alone.
73, Pascual - EA5WU