Sorry I do not know. My assumptions is that there is an issue with running the standalone app specifically on Mac OSX 10.10
The standalone seems to work fine on current OS versions, but I do not know that it was ever tested on OSX before 10.11
NanoWallet does not use Java.
Because it operates with JavaScript provided by browser, installing Java is not necessary.
The title is wrong here, and in the actual test, the test is done with MacOS 10.12.
It is said that similar symptoms appear in Universal clients.
I will rephrase the title.
thanks
Sorry, yes, of course - I saw the websocket errors and then totally forgot he was talking about Nanowallet.
1 Like
Oh, 10.12 works but 10.10 does not work. I made a complete mistake.
By design, the application version is not certified with 10.10, so please use the Universal version.
Although the problem is not solved.
Trying to run a traceroute is get the following result:
Not sure whether it helps with my lack of connectivity?
traceroute to alice6.nem.ninja (108.61.168.86), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 0.909 ms 0.600 ms 0.535 ms
2 lo0.central10.psb-bng02.plus.net (195.166.130.253) 6.754 ms 7.337 ms 7.000 ms
3 411.be6.psb-ir01.plus.net (84.93.253.107) 8.007 ms 7.820 ms 7.755 ms
4 core1-be1.southbank.ukcore.bt.net (195.99.125.130) 7.426 ms 7.485 ms 7.503 ms
5 peer6-hu0-6-0-4.telehouse.ukcore.bt.net (62.172.103.21) 9.017 ms 8.677 ms 8.868 ms
6 t2c4-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.244) 8.558 ms 8.332 ms 8.639 ms
7 82.112.101.73 (82.112.101.73) 8.584 ms 8.835 ms 8.846 ms
8 ae-13.r24.londen12.uk.bb.gin.ntt.net (129.250.4.25) 8.351 ms 8.977 ms 8.195 ms
9 ae-5.r24.nycmny01.us.bb.gin.ntt.net (129.250.2.18) 74.466 ms 74.277 ms 80.981 ms
10 ae-1.r25.nycmny01.us.bb.gin.ntt.net (129.250.3.207) 74.488 ms 79.210 ms 79.397 ms
11 ae-9.r22.asbnva02.us.bb.gin.ntt.net (129.250.2.149) 85.334 ms 80.583 ms *
12 ae-5.r23.lsanca07.us.bb.gin.ntt.net (129.250.3.189) 149.029 ms 149.143 ms 153.756 ms
13 ae-1.r22.lsanca07.us.bb.gin.ntt.net (129.250.2.206) 145.914 ms 150.987 ms 145.767 ms
14 ae-5.r20.sydnau02.au.bb.gin.ntt.net (129.250.3.165) 301.724 ms 301.772 ms 301.733 ms
15 202.68.70.146 (202.68.70.146) 303.371 ms 302.956 ms 303.035 ms
16 27.111.240.17 (27.111.240.17) 297.420 ms 297.255 ms 305.363 ms
17 xe-1-0-0.gw102.sy3.ap.equinix.com (27.111.240.139) 302.610 ms 302.394 ms 302.451 ms
18 * 180.189.25.6 (180.189.25.6) 303.101 ms 297.636 ms
19 * * *
20 108.61.168.86.vultr.com (108.61.168.86) 294.699 ms 294.492 ms 294.374 ms
Route information seems to have no problem.
And the next URL probably will return correct JSON.
http://alice6.nem.ninja:7890/node/info
In this case, there is a high possibility that OS and browser environment are intertwined complicatedly.
Please use Chrome that is most compatible with NanoWallet.
Could you tell me more about your OS version? (10.10.x)
Also please give me the browser version.
Please try building the environment in the latest situation as possible.
I’m running 10.10.5 - and already tried both safari and chrome. My version of Chrome is 62.0.3202.94
Thanks
Is the environment of 10.12 also running at home in the same network?
no that’s at my work on a different network entirely