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

The UI needs a page refresh to start working with no pre-existing authcodes #3620

Closed
jesuscript opened this issue Nov 25, 2016 · 6 comments
Closed
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@jesuscript
Copy link
Contributor

To reproduce:

  1. delete ~/.parity/signer/authcodes
  2. start parity as parity (note: without the "ui" command, or the bug won't show itself)
  3. open 127.0.0.1:8180 in your browser
  4. the UI gets stuck at "Connecting to the Parity Secure API" until the page is refreshed
@keorn
Copy link

keorn commented Nov 25, 2016

I think you need to go to localhost:8080 which redirects you to 8180.

@jesuscript
Copy link
Contributor Author

the hostname has to be 127.0.0.1, not localhost. Not sure how this makes a difference anyway, the page still won't update

@jacogr jacogr added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Nov 28, 2016
@derhuerst
Copy link
Contributor

Cannot confirm. localhost:8080 and 127.0.0.1:8080 both redirect me to 127.0.0.1:8180, which connects successfully and then shows "generate a Signer token". Tested on master.

@derhuerst
Copy link
Contributor

Can confirm actually (on :3000), but had to delete restart parity twice after deleting ~/.parity/signer/authcodes for some reason. Will look into it.

@ngotchac
Copy link
Contributor

Should be fixed with #3927

@derhuerst
Copy link
Contributor

Please reopen if the problem shows up again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

5 participants