Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

WebUI: Channel does not exists in webui #37

Closed
pcppcp opened this issue Aug 21, 2017 · 2 comments
Closed

WebUI: Channel does not exists in webui #37

pcppcp opened this issue Aug 21, 2017 · 2 comments

Comments

@pcppcp
Copy link
Contributor

pcppcp commented Aug 21, 2017

Problem:
If webui cached state uses a saved state of a channel that has been closed already, only a server reply "Channel does not exist or has been closed(sender=0x0052d7b657553e7f47239d8c4431fef001a7f99c, open_block_number=3261525)" is displayed.
The message goes away only after deleting the cookies.

Solution:
The webUI should display either a button to forget/settle the channel or forget the saved data automagically.

@andrevmatos
Copy link
Contributor

andrevmatos commented Aug 21, 2017

The webUI already provides those options, but they are, of course, only displayed when the webUI is served. As the signed balance proof is sent to the server through cookies, it persists across sessions, so the server thinks it is trying to send BP again for old/closed channel (which isn't the case).
Solution is for the proxy to serve the webUI even in the above exception, so the user has its options.

@pcppcp
Copy link
Contributor Author

pcppcp commented Aug 29, 2017

fixed

@pcppcp pcppcp closed this as completed Aug 29, 2017
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

2 participants