Configurator Stuck Loading on Kira

On windows 10 I am unable to access the kira page in the configuration tool. It is stuck "loading" even after refreshing, reopening, restarting the computer and trying again. I gave the tool over an hour to load and it still did not come up.

Getting a connection_timed_out error when trying to pull the Kira-Standard.json file. Does not seem to be a firewall issue.

I'm getting the same issue on MacOS 10.13.6.

I'm seeing this issue in Windows 10 1709 as well. This is while running Kiibohd as Administrator too. IN Linux (running as root) it works fine.

I am also having this issue, but in my case I think it IS a corporate firewall issue. Is it possible to host the layout files on standard http port 80 or even better, over https on 443?

EDIT: in trying to sort this out myself, I found the following in the src/renderer/state/settings.js file:

// const defaultUri = dev ? 'http://localhost:8080' : 'https://configurator.input.club';
const defaultUri = dev ? 'http://localhost:8080' : 'http://vash.input.club:3001';

For fun, I checked https://configurator.input.club/layouts/Kira-Standard.json, and it responds but has an older version of the default layout defined. Can this endpoint be updated with the 2019 edit of the file?

I'm having the exact same issue with my Kira keyboard on Windows 10. @bjohnso5, did you ever have any luck solving this? Thanks!

@travVT no, sorry, I didn't want to spend too much work time looking into it, as that's where I use my Kira.

Similar issue on macOS Mojave, with the K-Type keyboard. I am also on a corporate laptop, so it could be related to that.

I'm getting a net::ERR_CONNECTION_TIMED_OUT for "versions" and "KType-Standard.json"

On further investigation, I have confirmed that I'm unable to access that URL that is requested by the software:

http://vash.input.club:3001/versions

On my work laptop, I can access vash.input.club but not over port 3000.

On my home computer, I can get a response from that URL over 3000 just fine.

For me it was my corporate network blocking certain ports. I ended up connecting my computer to my phone's wifi hotspot and re-trying; it worked just fine. You should either try to configure your keyboard at home or using some other network, if you have access.

The fix for this should be to re-deploy the API for that endpoint to a more standard port 80 or port 443. That way, it would have a much lower chance of getting blocked by corporate policies.

@jbondeson do you know how this endpoint might be able to be moved to a standard port? It seems you were the last person to set this:

configurator/src/renderer/state/settings.js

Line 13 in 1ba70df

    
           const defaultUri = dev ? 'http://localhost:8080' : 'http://vash.input.club:3001';

It's working for me now with 1.0.2 and commit 18ac1cd

Thanks @jbondeson !!! This might have been a "small issue" for you, but it was a total blocker for those of us affected.

1.0.2 is working for me too! Thanks @jbondeson. :)