Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

Parity shell white window #205

Open
goodstemy opened this issue Sep 4, 2018 · 14 comments
Open

Parity shell white window #205

goodstemy opened this issue Sep 4, 2018 · 14 comments

Comments

@goodstemy
Copy link

I'm running:

  • Parity client version: v2.0.3-beta-a0a2bed-20180831
  • Parity UI version: 0.4.0
  • Operating system: MacOS
  • Installed via: from source
  • Fully synchronized: es
  • Network: demo poa tutorial
  • I tried to restart both Parity UI and Parity Ethereum client: yes

I try to deploy my contract with truffle by steps below:

  1. Run parity via parity --config node0.toml
  2. Run shell via npm run electron
  3. Run truffle migrate --network local with truffle config:
module.exports = {
  networks: {
    local: {
      host: "127.0.0.1",
      port: 8540,
      network_id: "*", // Match any network id
      from: "0x478a981B238a87EF8263DD343E9564F44b8e3c85",
    },
    ganache: {
      host: "127.0.0.1",
      port: 7545,
      network_id: "*"
    }
  }
};
  1. Parity signer ask for select local key and type password
  2. After choosing local key and typing password I get

2018-09-04 17 29 46

@goodstemy
Copy link
Author

ETH transactions with selecting local key and typing password works fine

@Tbaut
Copy link
Contributor

Tbaut commented Sep 5, 2018

You should avoid using Parity UI/signer for this. Use personal_sendTransaction or unlock an account (insecure if your node is exposed to the outside) temporarily.

@kazushige359
Copy link

I've got the same issue. @Tbaut Could you explain more about how to use personal_sendTransaction instead of Parity UI/signer?

@Tbaut
Copy link
Contributor

Tbaut commented Oct 5, 2018

@kazushige359 you could use MyCrypto Desktop App if you're not confident with using the command line. The advice I gave above isn't meant to be the only way of doing things, and it is not user friendly at all.

@vn-linescode
Copy link

Hello, I have the same issue. I always use the Parity UI integrated in Parity version 1.x, now i'm using this shell and I'm no more able to send transfer.
I don't think using personal_sendTransaction is the solution, I know the RPC, I create an application on top of it, but when I need to transfer ether I like to do it from Parity UI since it's very easy and fast.

Thank you.

@kazushige359
Copy link

kazushige359 commented Oct 16, 2018

Thank you for the comment. I didn't use Parity UI, instead unlocked my account from terminal like this. It worked for me.

parity --unlock [account] --password password.txt

@vn-linescode
Copy link

Done, but now I have this error:
"Trusted Signer is disabled. This API is not available"

@stone212
Copy link

@vm-linescode When you unlock an account Parity disables the UI. At least that's what happened in the past when the UI was part of Parity. Try --force-ui and see if the UI comes back.

@Tbaut
Copy link
Contributor

Tbaut commented Oct 18, 2018

@vn-linescode we advise to use Metamask or MyCrypto Desktop wallet on to of a Parity full node to send transactions. Parity UI is not in a state where et can be advised unfortunately.

@vn-linescode
Copy link

@stone212 --force-ui works only in version 1.x which is no more usable due to the recents ropsten forks.
@Tbaut Ok, is there a way for Metamask to get the keys created in the partity folder?

@Tbaut
Copy link
Contributor

Tbaut commented Oct 18, 2018

is there a way for Metamask to get the keys created in the parity folder?

Sure, you have to select the JSON file in the key folder
https://support.dex.top/hc/en-us/articles/360004245533-How-to-Import-Account-with-Private-or-JSON-File-

@vn-linescode
Copy link

vn-linescode commented Oct 18, 2018

I'm using tons of wallets, MyCrypto seems not to fit my requirements :(
Is there a way to help you to fix this issue?

EDIT: I did a little java client that uses RPC to send transactions, i'm OK with it, I hope continue to use the UI for contract creation and invokation.

@stone212
Copy link

@vn-linescode

--force-ui works only in version 1.x which is no more usable due to the recents ropsten forks.

Okay thank you. So (unrelated to this ticket) can you tell me what the correct way is of allowing the Parity UI on nodes where an account is unlocked? This is a common use case for us. It is secured by SSH tunnel so no security risk.

@vn-linescode
Copy link

@vn-linescode

--force-ui works only in version 1.x which is no more usable due to the recents ropsten forks.

Okay thank you. So (unrelated to this ticket) can you tell me what the correct way is of allowing the Parity UI on nodes where an account is unlocked? This is a common use case for us. It is secured by SSH tunnel so no security risk.

I don't know how Parity UI connects to Parity, I used to have 2 parity listening into 2 different ports, but I can't see any configuration on UI.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants