Disappeared from the list [CDN filtered out kiwisdr.com]

edited October 14 in Problems Now Fixed

Hello,

my Kiwi recently disappeared from the list. Not sure when exactly, but it has been working without any changes for about 2 years. I have it behind a CDN.

Connect still says: "Based on above selection, and external port from Network tab, the URL to connect to your Kiwi is:iz6byy.k1fm.us:80"

Public says: "rx.kiwisdr.com registration: successful"

Network's check port open says: YES / NO

Has anything changed recently?

Thanks

Comments

  • jksjks
    edited October 14

    Hmm. Looks like you're getting hosed by your CDN.

    kiwisdr.com does a curl https://iz6byy.k1fm.us/status every 45 minutes to decide if your publicly-listed Kiwi is running or not. When I do this from my home IP it works fine and I get the expected result returned.

    When I do this from either of the two kiwisdr.com VPN servers I get a HUGE amount of HTML and Javascript junk returned. It sort of looks like a filter or access challenge of some kind. But it's too much for me to wade through manually. If I could force it to get loaded into a browser from my home IP it would be easier to see what it's doing.

    See if there is a way to put kiwisdr.com on a whitelist with your CDN provider.

  • Now I know what's going on now.

    I recently started filtering out cloud based requests. The filter works fine but has the side effect of cutting out your legitime requests. Are there any fixed IPs I could whitelist, maybe?

  • kiwisdr.com currently = 50.116.2.70, but this will change if it ever migrates due to upgrade or something. Can't you just do it by domain name? The other one (forum.kiwisdr.com) is not really necessary for this problem.

  • edited October 16

    I was finally able to solve the issue and I would like to add some details that I believe will be useful to others who run into the same issue. Here they are:

    • The moment one toggles the switch under "Public" that says "Register on rx.kiwisdr.com?" two attempts will be made to reach the /status endpoint of your Kiwi. In my case, I saw those requests coming from this Linode IPV6 host: 2600:3c01::f03c:91ff:fed4:ac4. If any of those two requests is successful the kiwi is immediately registered
    • The IP suggested by jks (50.116.2.70) doesn't seem to be related to the registration procedure. I have not received any requests from it
    • There is another IP address performing daily /status requests originating from Sydney at about 17:00 UTC: 185.167.116.109. I am not sure if those requests are for list housekeeping

    Thanks for the help

  • That IPv6 address is also from [proxy.]kiwisdr.com (see below). The Kiwi server code does a DNS lookup on kiwisdr.com to cover the case of kiwisdr.com moving in the future (the IPv4 address is hardcoded to be used as a last resort). So on IPv6-only or 4/6 mixed networks I guess it's possible the IPv6 address would be used. I'm not all that familiar with the nuts and bolts of IPv6.

    I didn't have the 185.167.116.109 address in my notes. There are a bunch of people who poll kiwisdr.com/public of course to drive things like http://rx.linkfanel.net


Sign In or Register to comment.