Proxy nodes are currently getting restarted to apply a patch to resolve an issue. Cheers for that @Joseph_Meagher . This issue would have prevented clients reconnecting to the network for about 2 hours after disconnecting from the network, especially if all proxy slots were utilised in the last session.
This should hopefully be complete in about an hour (each node taking about 3 mins each for 20 nodes). Not all nodes will be offline at the same time, we’re trying to do it slowly to prevent wiping the network data. Will update here once its complete or if we need to do a full restart of the network including data(hopefully doesn’t need it).
EDIT: Restart complete. Proxy nodes should be updated now.
Hi @Joseph_Meagher, when you say it fails what do you exactly mean? is the function on main.js being invoked at all? or it fails when invoking any of the safeApp functions within it? Perhaps you can add some logging to see what is exactly happening.
I am running the SAFE web API playground on localhost and it keep downloading safe_proxy.pac over and over again in chrome when I click on things. Apart from that it works.
Another issue that’s just with the API playground is that if there’s an error, there’s a spinning loader that doesn’t go away until I reload the page.
Yeah i am certain I did but if i try to create again using token it says token is already used. I could be losing it though as I am sleep deprived from the arrival of a baby maidsafer.
@intrz@Matt you have to edit the proxy settings of your internet browser (e.g. chrome or IE) and remove the link to this proxy file in the advanced settings.
Eager to start having a look at Test 18 but get …
This testnet is currently limited to forum users who are at least Trust Level 1
Currently on level 1 - help.
Thanks