-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
[v2.0.0-beta3][CONNECTION] App connection issue to the RC server #10363
Comments
@mmarif4u @HammyHavoc @ccfiel can you check your server logs when you request avatars in jpeg format? Or could I have access to your server? Thanks |
@rodrigok I can give you access. Where can I send the credentials? |
@rodrigok I have provided the logs in the thread above. That are the exact logs when this happens. Hope it is of some help to debug. |
@rodrigok I have email you the credentials. Hope it can help |
@ccfiel please contact me at https://open.rocket.chat/direct/rodrigo.nascimento |
@rodrigok @sampaiodiego Added to 0.64.0 but I would say we need a patch in order to fix this one. |
Fixed in: #10390 Triggered a build will do quick test and push it out before 0.64.0 |
Please |
this fixed my issue #1057 but is it normal i can't send video or audio messages in this android client? |
fix :) |
@mmarif4u commented on Wed Apr 04 2018
Your Rocket.Chat.Android version: 2.0.0 beta 3
Last time i bring this issue to the RC open chat android channel too. And that issue continues, where the app trying to connect to the RC server. While connecting it crash the RC server instance too. I have checked the server logs and found this at the time when it was attempting to connect.
Something to do with retrieving channel/user avatars?. The app also some time shows JSON errors while connecting. Which i assume is related to the json output from the API call.
Android logs, https://open.rocket.chat/channel/androidnativeapp?msg=ACg2JZC6EdKpKcgYi
@rafaelks
@mmarif4u commented on Wed Apr 04 2018
RC snap is updated to 0.63.0, and after checking this morning, this is the error now:
2018/04/05 10:48:02 [error] 8297#8297: *135538 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.yyy.xx.yy, server: team.WEBSITE.com, request: "GET /sockjs/info?cb=izp3r5sdg2eh HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=izp3r5sdg2eh", host: "team.WEBSITE.com", referrer: "https://team.WEBSITE.com/channel/CHANNEL-NAME"
@HammyHavoc commented on Thu Apr 05 2018
I get endless "connecting" with countdown messages on my Android phone before it eventually crashes.
@ccfiel commented on Thu Apr 05 2018
same here :(
@rafaelks commented on Fri Apr 06 2018
@mmarif4u @HammyHavoc @ccfiel Thank you guys for opening the issue! So the problem is that your instance is dying when connecting to the Android app? I'm imagining that the issue related to the request that we're doing for the image in JPEG format. If that's the case, I'll move this issue to our back-end repository. Can you please confirm?
@HammyHavoc commented on Fri Apr 06 2018
@rafaelks Spot on! :- ) This is correct.
The text was updated successfully, but these errors were encountered: