Mic
@justparking Can you please test this fix and let me know if it works for you?
The address returned by `/REST/nodeURLs` is only a single value. If this returned an array of possible addresses then a test could be added on the UI for the most...
Just following up on this issue again. I have created a simple method for checking if the address is reachable before presenting it to the user. It would be good...
I believe this is now supported?
It might also be worth considering having a subnet broadcast mode?
Just checking over older issues. I'm not entirely sure why I've been assigned this as I don't have a mac and I'm not sure how complicated the steps really are....
Should be fixed now. Can you verify?
This may also be addressed in the new UI, soon to be released, where there is the ability to navigate to different available frontends from the navbar.
Late to the party here I know, sorry. The other option is to add a type attribute, e.g. ``. It's a convention already since we have ``.
Came across this today when remotely accessing a site. The issue is that the REST endpoints for the node are responding with incomplete data because the node hasn't finished initialising...