show help in debugging connection problems

[thammi]

Issue by payload Sunday Jan 05, 2014 at 22:28 GMT Originally opened as https://github.com/palavatv/palava-portal/issues/4

---

When somebody notices connection problems, it is sometimes not obvious why there are problems.

• hole punching didn't do its job (why?)
• slow connection
• is there another possible and detectable issue?

I propose, the cause of such problems should be detected and a user should get the opportunity to see these causes and maybe a helping link how to fix it.

This involves adding detection of errors in the palava-machine, passing information to the clients (palava-client) and integrating a possibility to see this information in the UI (palava-portal). Maybe it also involves adding a little test setup for palava-machine to generate such errors.

What do you think about it?

[thammi]

Comment by payload Sunday Jan 05, 2014 at 22:37 GMT

---

• when clients try to establish connections to each other and it fails, this information should go to the server and back to the other client, so both know, there is an error between them

[farao]

Duplicate of https://github.com/palavatv/palava/issues/2