KIWISDR.LOCAL only working on admin interface

dl2sbadl2sba
in Problems and Issues
Hi Group

I've updated today from a 1.8x version to current 1.9.5.

I can connect the ADMIN UI via http://kiwisdr.local:8073/admin as well http://192.168.2.100:8073/admin
But I cannot connect to the RX UI via http://kiwisdr.local:8073 - the browser window is blank.
When I connect to http://192.168.2.100:8073 the RX UI comes up.

What I'm doing wrong?

//Dietmar

Comments

  • jksjks
    edited May 2018
    Is this with Opera? I had another report of a blank screen with Opera. I don't know why anything would be different with using the ip address versus a .local. Could you try opening the browser console and look for error messages during the blank screen? It depends on your browser but somewhere there is a menu called "developer" and a menu item called "javascript console". The names will vary. Then look for any obvious error-looking messages. They will probably be marked in red and won't necessarily be at the end of the message list.

    Thanks.
  • dl2sbadl2sba
    edited May 2018
    You're right, there is an error:
    ?
    kiwi_util.js:459 getVarFromString: NO SCOPE cfg.ant_switch.denymixing scope_name=ant_switch
    kiwi_util.js:51 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
    kiwi_util.js:62 iOS=false OSX=false Linux=false Windows=true android=false
    kiwi_util.js:63 safari=true firefox=false chrome=true
    kiwi.js:49 conn_type=kiwi
    kiwi_util.js:898 WebSocket connection to 'ws://kiwisdr.local:8073/1526825870872/SND' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
    w3_util.js:272 w3_el_softfail("id-debugdiv") SOFTFAIL
    kiwi_util.js:924 WS-CLOSE: SND
    xdLocalStorage.js:181 XDLS seen servers=0
    ?
    The same error appears also sometimes on the ADMIN UI - then also blank screen

    ?
  • jksjks
    edited May 2018
    Well, this looks okay. It's just telling us what we already know -- that a lookup on "kiwisdr.local" doesn't resolve. By that user agent info it looks like this is Chrome 66 running on Windows. What version of Windows?

    But to get this far it did successfully connect to http://kiwisdr.local:8073/ (note "http" instead of "ws") to fetch the html and javascript parts of the Kiwi code. So it is partially working. It's as though lookups on kiwisdr.local are not 100% successful all the time which is extremely odd. I hate to say it but have you tried rebooting Windows? This has got to be an mDNS problem on Windows somehow. Anyone else having this problem?
  • JohnTJohnT
    Yes I have the problem ever since the Windows April update which arrived a few days ago on my PC.
    Up to then it was working perfectly. I tried using the ITunes fix which I used when I first got my Kiwi assuming the update had removed it but it has not resolved the problem.
  • jksjks
    Well there you go. Micro$oft strikes again. One of the many reasons I have never used it here.
  • dl2sbadl2sba
    edited May 2018
    @JKS
    Microsoft Windows [Version 10.0.17134.48]
    Yes rebooting was done several times in the meantime

    @JohnT
    What is the ITunes fix?

    BTW - sorry for using a niche operating system :-/
  • jksjks
    All I have here is Windows 10 Home 1709 16299.431 and it works fine. But I do have the iTunes mDNS stuff installed (see http://kiwisdr.com/quickstart/index.html#id-net-mdns)

    If you open a Windows command window does a "ping kiwisdr.local" run without dropped ping responses? I think it defaults to trying 4 pings. There is probably some switch to get it to run a bit longer.
  • dl2sbadl2sba
    Ping never works in command line with a full installation of the latest iTunes.
    Removing Bonjour didn't solve the problem.
  • jksjks
    Well, so Microsoft has broken mDNS. Until there is an update released with a fix I would suggest just creating a bookmark using the ip address. If your local DHCP is moving the ip addresses around you should probably be able to increase the DHCP lease time or lock the ip address to the Beagle Ethernet MAC address.
  • jksjks
    One additional thing to check. If you can, log into the Kiwi Beagle and type "scs avahi-daemon". See if it is running. If it's not running then restart it by typing "scre avahi-daemon", check the status again with "scs", and see if pings to kiwisdr.local begin to work. Also check that "cat /etc/hostname" on the Beagle prints "kiwisdr" as the host name.
    Powernumpty
  • JohnTJohnT
    Just by chance I have discovered that kiwisdr.local:8073 will work in Firefox provided there is already one tab open!

    It does not seem to matter what that open tab is looking at, my PC is set up to open on the BBC news page but anything else I tried also works.

    I tried this with Chrome and Microsoft Edgeto see what happens but it does not work.

    Very strange.
  • dl2sbadl2sba
    So here the data:

    --------------------
    root@kiwisdr:~# scs avahi-daemon
    ? avahi-daemon.service - Avahi mDNS/DNS-SD Stack
    Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled)
    Active: active (running) since Sat 2018-05-19 09:47:41 UTC; 4 days ago
    Main PID: 441 (avahi-daemon)
    Status: "avahi-daemon 0.6.31 starting up."
    CGroup: /system.slice/avahi-daemon.service
    ??441 avahi-daemon: registering [kiwisdr.local]
    ??458 avahi-daemon: chroot helper

    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

    --------------
    root@kiwisdr:~# cat /etc/hostname
    kiwisdr
  • jksjks
    Okay, that all looks normal. So the Kiwi should be responding to mDNS requests.
  • jksjks
    edited May 2018
    I don't think it will help, but in a Windows command window try the command ipconfig /flushdns (note: ipconfig, not ifconfig like on Unix).
  • dl2sbadl2sba
    No - didn't help
Sign In or Register to comment.