Alternatives to reverse proxy

As the very useful reverse proxy service is currently not taking new requests, is there any alternative way of doing this?

My Kiwi connects via a cellular modem, but the provider doesn't support port forwarding.

Any ideas how to provide public access would be appreciated!

thanks


A

Comments

  • edited December 2020

    You can use same frp.

    Install server on a hosting VM or home PC with public IP and client on your remote QTH, than configure access...

    You will create personal reverse proxy for KiwiSDR and maybe something else... For example for ssh access to KiwiSDR or other devices on this site.

    Ofcourse you can use many frp-clients with one frp-server for multi sites.

    73! Yuri

  • Thanks - But I'd rather not have to use a separate PC or pi at the SDR, as its on a remote site with limited power from battery and solar, so I need to keep power consumption down.

    I'd prefer a solution that the Kiwi and my Teltonika 4G router can use natively.

    A

  • You can install copy frp-client from github on BBG, but be careful, because performance issues may arise.

    73! Yuri

  • Thanks Yuri,


    I was not aware of frp.

    I'll make it a configurable option in a future version of wsprdaemon.


    Rob

    rz3dvp
  • edited February 16

    I am using Cloudflare Tunnel. It's free and very fast.

  • You can use the reverse tunnel feature of ssh built into the BBG to provide remote access. On the BBG run:

    ssh -R 8073:localhost:8087 user@somepublicserver.com

  • I recently replaced my crappy metered satellite internet service and now have great speeds and unlimited data. However, I no longer have the ability to open ports.

    Since proxy.kiwisdr.com is apparently not currently an option, I have been looking to find another solution. I have been reading on this forum solutions that others have successfully used, however my knowledge on such matters is quite limited.

    Would someone be willing to provide detailed step by step instructions, and maybe some hand-holding ("Reverse Proxy For Dummies") on getting me set up on NGINX or Cloudflare or similar?

    I would be MOST appreciative!

    Thanks in advance.

    Dennis

  • edited February 16

    For Cloudflare configuration. You will need to own a domain name and know some Linux command. Instructions:

    https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide

    The configuration file would be

    url: http://localhost:8000
    tunnel: <Tunnel-UUID>
    credentials-file: /root/.cloudflared/<Tunnel-UUID>.json
    

    Replace the 8000 to whatever your KiwiSDR's port

    For whatever reason HTTPS doesn't work. So go into your Cloudflare dashboard and into page rules and create a new rules. URL is whatever URL you want to use with your Kiwisdr e.g. receiver.abcde.com/*

    Pick rules "SSL" to Off and "Automatic HTTPS rewrite" to Off.

    After you confirm it is working, you need to let Cloudflare tunnel run as service so it will start everytime. An easier way would be put a command in your /etc/rc.local

    cloudflared tunnel run <UUID or NAME>
    

    Or follow this guide to run it as service

    https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/as-a-service/linux

  • @pistsc hello!

    I've tried cloudflare tunnels and got an error

    This page isn’t working ******* redirected you too many times.
    Try clearing your cookies.
    ERR_TOO_MANY_REDIRECTS
    

    Does you config still work ?

  • edited August 9

    With a little struggle, I have kiwisdr running on the end of a cloudflared tunnel.

    1. My router forwards any thing received on port 8073 from my ISP internet connection to the static ip where my kiwisdr lives, namely on my private network http://192.168.1.120 Refer to NetgearPortForward .png (Note 6)
    2. I used the GUI dashboard in the Cloudflare website section on Zero Trust Tunnels. A few screen shots might help you find the correct areas. You can pick off the URLs from the .png screen shots.
    3. My web domain, foxgulch.net is registered with domains.google.com for $12/year. Cloudlare is the domain name servers for foxgulch.net (I changed it from google dns) so that then you enter kiwi.foxgulch.net in your browser, cloudflare sees that and routes your request down the tunnel into my kiwiSDR
    4. After setting everything up, I found I could get into my kiwi but only if I was in Incognito mode (non https). So the orginRequest noTLSVerify stanza was added to the config.yml file manually with a text editor.
    5. I followed the instructions found here using the GUI (with the exception of the step 4 above). https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/
    6. Go to https://www.dropbox.com/s/tm1nbfyza5w771w/CloudflarePng.zip?dl=0 which has the four illustrative .png files I mentioned above. I couldn't get the four of them to upload and appear here.
    7. Hope this is helpful. Larry W0AY
  • A little glitch: Entering kiwi.foxgulch.net establishes a connection to my kiwisdr over the Cloudflare tunnel OK. However, entering kiwi.foxgulch.net:8073 stalls and goes not where. Since rx.kiwisdr.com is checking periodically to see if kiwi.foxgulch.net:8073 establishes a connection to a kiwisdr, my kiwisdr never ends up on the map.

    I have tried kiwi.foxgulch.net:0 but that hung (stalled) also. Anyone experience this glitch?

    Tnx Larry W0AY

  • jksjks
    edited September 8

    For the problem of not appearing on the map: I changed the registration script that runs on kiwisdr.com to try port 80 if there is no answer on the configured port (typically 8073) when polling /status. It fixed this problem.

    We also had another user with an https (note 's') proxy where the curl of /status was not getting a proper connection upgrade from http to https (typically an http 302 redirect I believe). This case is now detected and handled. So this Kiwi is also now listed and appears on the map.

Sign In or Register to comment.