Media not working on Android app

[sas-w]

I installed WAproxy on my server. It was easy to do.

I am using standard ports: 443 for messages and 7777 for media. This configuration is the only one that works for me. Media on the default port 587 does not work.

At the same time, everything works perfectly on iOS. However, on Android, I can see that the connection is established, but media files are neither sent nor loaded — only messages work.

I tried running WAproxy with different default ports, but it didn’t work for me.

Could you help me figure out the problem with the Android app?

[ayk00000000]

ثبّتُ WAproxy على خادمي. كان الأمر سهلاً.

أستخدم المنفذين القياسيين: ٤٤٣ للرسائل و٧٧٧٧ للوسائط. هذا الإعداد هو الوحيد الذي يناسبني. الوسائط على المنفذ الافتراضي ٥٨٧ لا تعمل.

في الوقت نفسه، يعمل كل شيء بسلاسة على نظام iOS. أما على نظام أندرويد، فأرى أن الاتصال مُنشأ، ولكن ملفات الوسائط لا تُرسل ولا تُحمّل، والرسائل فقط هي التي تعمل.

لقد حاولت تشغيل WAproxy مع منافذ افتراضية مختلفة، لكنه لم ينجح معي.

هل بإمكانك مساعدتي في معرفة المشكلة المتعلقة بتطبيق Android؟

تغير
يوجد مخترق

[ion-lane]

I have the same problem. Media doesn't work on Android, but works fine on iOS. The proxy status shows it's connected. There's no message indicating media is unavailable. However, media can take a very long time to load/send, or not load/send at all. Changing the port to 7777 doesn't solve the problem. I tested it on WiFi, where WhatsApp isn't blocked.
I sent feedback from the app.
WhatsApp version 2.25.35.79
Android 13

[ion-lane]

I may have found the reason why media traffic is blocked on Android.
I collected a traffic dump on port 587 and found a packet containing the WhatsApp CDN server address.

On Android, data is transferred via http/1.1, and the WhatsApp server address is visible in it. This packet is followed by multiple retransmissions, indicating that the traffic was blocked by TSPU (DPI).

On iOS, data is transferred via http/2, and the server address is encrypted in the packet. And the traffic successfully passes through to the proxy.

[sas-w]

As far as I understand, there’s nothing we can do from our side? We’ll have to wait for a WhatsApp update for Android.

[yarolan-tech]

It seems, we have problem with DPI of RosComNadzor (TSPU). I wolud ask everybody, who have a problem: you are from Russia?
FYI: Proxy connection to whatsup easy to detect using, SNI, which is not encrypted.

[ion-lane]

@sas-w

As far as I understand, there’s nothing we can do from our side? We’ll have to wait for a WhatsApp update for Android.

I don't know yet how we can resolve this issue on our side. All I did was write a review in the Play Store and provide a link to this issue.
I checked the WA proxy on WhatsApp for Business, and it's also blocked on Android.

[Bardissimo]

same issue from Russia

[imanihb2007]

same issue from iran

[Siavash1291]

Same problem from Iran

[michaelbrucelin]

It's May 18, 2026, and the problem still persists.

[mdshowrav352-hue]

I installed WAproxy on my server. It was easy to do.

I am using standard ports: 443 for messages and 7777 for media. This configuration is the only one that works for me. Media on the default port 587 does not work.

At the same time, everything works perfectly on iOS. However, on Android, I can see that the connection is established, but media files are neither sent nor loaded — only messages work.

I tried running WAproxy with different default ports, but it didn’t work for me.

Could you help me figure out the problem with the Android app?