New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ToxProxy AppImage generates (apparently) invalid ToxIDs #239
Comments
Is it required to make firewall adjustments to allow incoming connections on the host of the AppImage |
can you post a screenshot of trifa when it says the ID is invalid? |
just tried it again on the emulator, and it works fine. if it's still not working, please make screenshots and post more details |
I only capture the part after the "ToxID:" and I have pasted the same string into QTox which seemed happy.
|
can you scroll the text fully to the left, to show the start of the pasted ToxID please? |
there must be something wrong with the text you copied. |
did you copy the final "\n" or something? maybe remove the front letter and type it in manually and remove the end letter and type that in manually. can you join the matrix channel? |
Yeah. It's like there's some sort of invisible char captured. If I delete the final char of the string (or any single char) the "incorrect ToxID" message goes away. |
Just joined the Matrix channel BTW ... |
it can only be the "\r" or "\n" when you select the line ending when you copy. |
note to self: remove any \r and \n in pasted ToxIDs (if not already done) |
should be fixed by e765b9b |
Describe the bug
The output of running the ToxProxy AppImage produces a ToxID, that when pasted into TRIfA reports that the ID is invalid.
To Reproduce
Steps to reproduce the behavior:
I ran the AppImage on a Debian stable box.
Subsequently, I deleted the files the AppImage produced in the directory it lives in, and ran it again (as new) to produce a different Tox ID. This new ID was still invalid, according to TRIfA.
Expected behavior
Pasting the generated ToxID into the "Add Friend" dialog would result in the ToxProxy ID being accepted.
Your system information:
Add screenshots, if possible
Additional context
This may be a problem with TRIfA itself - as pasting the IDs into another Tox client seemed to accept them. They appear to be 76 chars long, and with no unusual chars ...
Strangely - deleting the last character of the generated ToxID allowed the ID to be claimed as valid in TRIfA - but it still didn't add a friend or work correctly.
Could this be a validation issue in TRIfA?
Also - Regarding firewalls:
Is it required to make firewall adjustments to allow incoming connections on the host of the AppImage for UDP on port 33445? I noticed it was listening on port 33445 so I allowed incoming cxns in the firewall rules.
Thanks
The text was updated successfully, but these errors were encountered: