jks

No. As I mentioned, there are hundreds (thousands?) of Kiwis out there with old frp clients that cannot just stop working.

The other problem is that the frps server claims the proxy port (8073), so there is no opportunity for a web server (we use lighttpd) to act as a load balancer on top of (in front of) the proxy service. Any port redirection has to come from the frp server code itself.

I have this working now. But now there have to be changes on the Kiwi-side to decide when to use proxy2.kiwisdr.com. Probably something like if the proxy name starts with a digit (the new Kiwi-2 auto proxy feature using the serial number as default proxy name). Since currently there are roughly as many of those as there are Kiwis with alphanumeric names (changed by their owner/admins).

@jimjackii That particular error, where you get vundefined.undefined only occurs when your proxy setup if failing to correctly handle an XHR transaction for a file called "VER" the browser is trying to get from the Kiwi server. That file will contain a JSON response that looks something like:

{"maj":1,"min":804,"ts":4611686018441628445,"sp":1}

So open the Javascript console and network tab in your browser and see why the fetch of the VER file fails. Does it get an HTTP status of something other than 200? Is the response something other than like the above? If so, figure out why.

Also, on the admin webpage tab, toward the bottom of the page, change the "Web server caching?" setting to "No" and restart. Your Kiwi page loads will be much slower, because no web caching will be done, but it may overcome whatever shortcoming your proxy solution has.

From the CHANGE_LOG file: