Mobile can't see photo sent directly by the app and messages after until reloading/clearing cache

Community Support
1

Description

Mobile can’t see photo sent directly by the app and messages after until reloading/clearing cache, other do see it, same for android and iphone, reloading,clearing cache and locking/unlocking phone fix it

Server Setup Information

  • Server Setup Information
    • Version of Rocket.Chat Server: 8.5.0
    • Operating System: Linux (Amazon Linux 2023 - EKS)
    • Deployment Method: Helm (chart 6.23.2) via ArgoCD on AWS EKS
    • Number of Running Instances: 1
    • DB Replicaset Oplog: MongoDB Atlas 8.0.26, 3-node Replica Set
    • NodeJS Version: v22.22.3
    • MongoDB Version: 8.0.26
    • Proxy: AWS NLB → nginx-external ingress controller (2 pods, ingress-nginx 4.12.1) → RocketChat “one” pod
    • Firewalls involved: AWS Security Groups, Atlas IP Whitelist
    • File Storage: AWS S3 via IRSA
    • Kubernetes: AWS EKS
    • Node resources: 4 CPUs, 15.3GB RAM
    • Pod limits: 1000m CPU, 3Gi memory

Any additional Information

ingress:
enabled: true
ingressClassName: nginx-external
annotations:
nginx.ingress.kubernetes.io/affinity: “cookie”
nginx.ingress.kubernetes.io/affinity-mode: “persistent”
nginx.ingress.kubernetes.io/session-cookie-name: “rc_session”
nginx.ingress.kubernetes.io/session-cookie-max-age: “172800”
nginx.ingress.kubernetes.io/proxy-connect-timeout: “30”
nginx.ingress.kubernetes.io/proxy-read-timeout: “3600”
nginx.ingress.kubernetes.io/proxy-send-timeout: “3600”
nginx.ingress.kubernetes.io/proxy-http-version: “1.1”
nginx.ingress.kubernetes.io/proxy-buffering: “off”
nginx.ingress.kubernetes.io/upgrade: “websocket”
nginx.ingress.kubernetes.io/proxy-body-size: “50m”
nginx.ingress.kubernetes.io/proxy-request-buffering: “off”
nginx.ingress.kubernetes.io/proxy-next-upstream: “off”
nginx.ingress.kubernetes.io/proxy-next-upstream-timeout: “0”

Any one have encountered this issue?

2

As 8.5 only released today I doubt it.

If you have a production system then upgrading to a .0 release without serious testing is professional suicide. The Q&A here is very poor.

You make no mention of licence version or approximate number of users? Let us know both.

If you are on CE with a lot of users there are lots of warnings of the consequences here.

Check github to see if anything arises over the next few days, see what your browser consoles say, make sure you are not using mongo file storage, and have a really hard look at your complex proxy arrangements.

More information will be required.

3

Same issue on previous version, non premium user.
Issue happens even with one user ( testing with one user on several platforms or two different users = same result )
Using AWS S3 for storage.

Issue happens only on mobile, both iOS and Android - No issues with Browser and Desktop.
Tried different setting for the proxy but non of them having any effect on this issue.