v1.816 breaks all browsers except Firefox, LibreWolf et al [update: fixed in v1.817,818]

jksjks
edited August 9 in Software release information

Looks like the upgrade of Mongoose (Kiwi's web server) in v1.816 breaks all the browsers I didn't test with 🙄

I've stopped the update for now. More news ASAP.

Comments

  • VK3KHZVK3KHZ

    No problem,

    I have v1.815 on all SD Cards and can restore from there.

    Cheers

    Paul

  • bwilsonbwilson

    I updated while switching modes, and get a "cannot connect" error, 502. Even on Firefox.

    If this is a network thing I presume it will repair when it reboots and updates the next version.

  • jksjks
    edited August 7

    What do you mean "while switching modes"?

    Error 502 is "Bad gateway". Do you have an unusual network setup? Private proxy? Wireless link, etc?

  • bwilsonbwilson

    I switched from 8 channel receive to 4-channel "classic" mode. That seemed to restart enough to trigger the update.

    I use Cloudflare, but when hitting directly to the IP address with Vivaldi browser (a chromium version) I get a connection refused error. From Firefox I get a unable to connect error.

    My KiwiSDR is wired to a network switch.

  • jksjks
    edited August 7

    v1.817 rolls back to Mongoose 5.6 fixing the problem. I see what the problem is, but I could not find where exactly the problem was. So I'll look for it offline. We'll continue to have the "connections from 127.0.0.1" problem as a result.

    Just restart your Kiwi to get the update. Use Firefox (or a derivative) to connect and restart when browsers like Chrome, Safari and Edge don't work.

  • bwilsonbwilson

    All better now. TNX

  • VK3KHZVK3KHZ

    Thanks John !

    All cards on v1.817 now..

    Cheers

    Paul

  • jksjks

    Bug found. My fault (always is). But I'm not going to be updating Mongoose 5 => 7 for a while. Due to the @bwilson issue and possibly others. Too much else of higher importance going on right now..

    F5AFY
  • jksjks

    @bwilson I'm going to have to move forward with the Mongoose update at some point because it solves problems other people are having.

    Instead of the 502 error you mentioned could it possibly have been a "503: Service Unavailable, determining local IP address -- try again in 10 seconds" error? Because that is a known condition that resolves itself with a retry after a delay.

  • barneyukbarneyuk

    Never noticed the problem myself.

  • bwilsonbwilson

    I don't think it was ever seen as a 503, but since it was going through Cloudflare reverse proxy, it could have well been reported as something other than it was. The best I can offer is that the web server just didn't respond on my install of 1.816 when I bypassed the reverse proxy. I waited far longer than 10 seconds to assess. I was hitting the web interface a number of times during the update so my impatience might have borked something in the web server.

    But I don't mind experimenting, so push the Mongoose upgrade and I'll help as I can if I see something hinky again.

Sign In or Register to comment.