Delete the #/init-error from the end of the URL and refresh. Be sure you are using the latest version of Chrome without a VPN. Lastly, go to settings and manually change your node under the Access.
You are viewing a single comment's thread from:
Delete the #/init-error from the end of the URL and refresh. Be sure you are using the latest version of Chrome without a VPN. Lastly, go to settings and manually change your node under the Access.
I still have trouble connecting and usually have to refresh several times before I finally get a connection. I had the automatic setting under node access. Never could get Chrome to work with this, but Firefox seems to be the most reliable. I occasionally use a VPN, but that wasn't the problem these last few times. Is it a bandwidth issue with the VPN?
We did find a few items in the socket connection this sprint. I'll be interested to hear if it improves your experience once 170108 is released.