Closed 3esmit closed 7 years ago
Any errors in Parity log? Are you using the latest version of extension and are the options pointing to correct URL?
Using 2.7.1 browser extension. I was looking better here now, and it show some errors at extension
and if I check in advanced it shows this
What is parity log? at console screen no errors, just regular sync stuff.
With new version you need to point the node to 127.0.0.1:8546
. It should be done automatically unless you have edited those fields in the paste.
I just checked that box, show advanced options, to print screen, I never touched any of that fields. Maybe it's not automatically doing this, at least for me.
Sorry, I confused the settings. They are correct, although your extension is too old for 1.7.2. Please update to 2.7.3.
Oh, nice. Would be nice if the extension warned me about this, because for me I'm using latest version https://github.com/paritytech/parity-extension/releases
Sorry, too tired today :( There were some code changes in 1.7.2 that caused incompatibility with the extension. The extension has been updated in chrome store and I was expecting it to auto-update for everyone. I've created a new release right now. Feel free to update manually - out of curiosity, why do you use a manually built version?
Because I googled 'parity chrome extension' and this was the path forward, I'm not sure why parity didn't offerd me, maybe because I use Chromium Browser, and not Google Chrome.
BTW, everything works fine in 2.7.3
I followed the instructions here https://github.com/paritytech/parity/wiki/Wallet-Remote-Access I'm using parity 1.7.2 at ubuntu 16.04 and used the command exactly as in the wiki. All works fine expect for parity-extension that can't connect.