@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.

"http://127.0.0.1:3000/avatar/@CHANNEL?format=jpeg", host: "team.WEBSITE.com"
2018/04/04 13:06:05 [error] 8297#8297: *121687 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.yy.xxx.yy, server: team.WEBSITE.com, request: "GET /avatar/@CHANNEL?format=jpeg HTTP/1.1", upstream: "http://127.0.0.1:3000/avatar/@CHANNEL?format=jpeg", host: "team.WEBSITE.com"
2018/04/04 13:06:05 [error] 8297#8297: *121687 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.yy.xxx.yy, server: team.WEBSITE.com, request: "GET /avatar/@CHANNEL?format=jpeg HTTP/1.1", upstream: "http://127.0.0.1:3000/avatar/@CHANNEL?format=jpeg", host: "team.WEBSITE.com"

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.