Parity-ethereum: Unable to make a connection to the Parity Secure API

[MeganerdNL]

Followed https://github.com/paritytech/parity/wiki/Wallet-Remote-Access this guide to connect to my linux box running parity with UI. Worked wirh 1.6.x but with 1.7.0 it will not accept any tokens generated with

parity signer new-token

Time is exact on both the linux box and the pc where I connect from, it comes back with: Unable to make a connection to the Parity Secure API
Reverted back to 1.6.10 --> That works.
I start with commandline:

parity --nat extip:[MYIP] --identity SomeName

[tomusdrw]

Additional ports are required to be exposed on Parity 1.7.
I've updated documentation, thanks for the heads up.

[sonpython]

I have the same problem

[5chdn]

@sonpython what's your exact problem?

[sonpython]

@5chdn The parity GUI does not accept the new created token using
parity signer new-token

Unable to make a connection to the Parity Secure API

I'm using parity 1.7
It used to work before

[5chdn]

@sonpython which operating system? which user is running the parity client?

[sonpython]

@5chdn

Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

I'm running parity under root

[5chdn]

@sonpython so you have to run sudo parity signer new-token (or simply as root)

or grab one valid token from /root/.local/share/io.parity.ethereum/signer/authcodes

[sonpython]

@5chdn

sudo parity signer new-token ==> also NOT WORK

but the token grabbed from /root/.local/share/io.parity.ethereum/signer/authcodes worked

thank you man!!

[PavelNiedoba]

Which ports needs to be open and where's the documentation ?

[folsen]

@PavelNiedoba Link to documentation is in original post: https://github.com/paritytech/parity/wiki/Wallet-Remote-Access
The ports required are 8180, 8545 and 8546

[PavelNiedoba]

@folsen thank you. I stil cannot figure out how to access wallet thorough corporate proxy which allows only ports 433 (and 80 which is not an option). I can open parity on https default port, but "parity signer new-token" will not work even when time is right

[tomusdrw]

@PavelNiedoba IMHO the best way to access the node in such restricted environment would be:

1. Start an SSH server on port 443 on the host machine.
2. Create an SSH tunnel from Client to Host (since 443 is open that should go through, unless there is some http-only proxy on the way)
3. Setup port mapping as described in the docs.

If that's not an option you need to:

1. Setup two domains pointing to the host machine (say, 'parity' and 'ws-parity').
2. Setup an nginx server running on Host machine.
3. Use VirtualHosts and proxy_pass parity to localhost:8180 and ws-parity to localhost:8546
4. Run parity with --ws-hosts ws-parity and --ui-hosts parity.

[PavelNiedoba]

Thank you, I got it working. I had to add --ws-origins=all to make it work

```
/opt/parity/parity \
--chain=ropsten \
--db-path=/disk2/ethereumBlockchain \
--jsonrpc-apis=all \
--jsonrpc-interface=127.0.0.1 \
--ws-hosts parity-ws.domain.com \
--ws-origins all \
--ui-hosts parity-web.domain.com
````

[Office-Julia]

@tomusdrw could you please paste link here for the documentation resolving this problem on Windows
It may help for further reference of the users who stuck with this issue.
Thanks.

[lucas7788]

how to solve this problem???

[shadowpho]

Same issue... followed the wiki for Nginx setup.

I'm running parity on a local server and connect to the UI with my laptop. The clocks on both machines are in sync.

Local server runs debian 9 with nginx 1.10.3, andParity/v1.8.6-beta-2d051e4-20180109/x86_64-linux-gnu/rustc1.22.1

[CorentinPacaud]

I am stuck with this issue too.
Parity version : v1.11.8-stable-c754a028e-20180725
parity UI version : 0.3.4
OS : Win 10.

Sometimes, I have this error in the peer logs :
writing illegal frame; state=Init, frame=Body { bytes: 47 }

[Tbaut]

@CorentinPacaud this is a very old and closed issue. Could you please open your own with your details what did you do, what happen etc..