-
Notifications
You must be signed in to change notification settings - Fork 453
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
"Connected" but only can send text, can't send/receive pictures videos and documents #200
Comments
+1 |
We're presently rolling out the updated application which supports media proxying. There is an updated user-interface which and status on both chat + media connections for the proxy. It should be coming in the next couple of weeks to everyone. Unfortunately it's a 2-phased update, we can publish the proxy (this github) which supports media, but there's also client changes (Android + iOS applications) necessary to also support proxying media traffic. Thanks! |
Finally, there is a clear explanation. Will the Windows client have a proxy function? |
You mean the companion application? Unfortunately there are not (current) plans to add support to the companion apps (web/macOS/Windows/etc) at this time that I'm aware of. However I'll ask around. |
Yes, only the mobile app has this feature right now, not the desktop app. okay, thank you. |
Thanks so much for your update ,we will be waiting for the big improvement if media problem solved. also I have found a way to avoid the server getting blocked by establishing a secondary tunnel to encrpt the data and protect the port for long time use ,this needs another server in local ,which will be extra expense but effective. |
Hi @MikeStick! We have rolled out the media enabling feature to all users. After setting a media port (or leaving it as default), you should get feedback on the UI whether the proxy you are using supports media. |
I tried it, but it still doesn’t work. It’s supported by the application. Doesn’t this repository support it? |
Could you check the URL for the stats port the proxy you are using ( You will also need to enter the media port on your device that corresponds to the port(s) of |
I tried pre-built images and images built from the repository, also tried default ports and custom ports, IPV4 and IPV6; but all can only proxy text, not media. Waiting for other people's reports, I'm going to bed first. |
|
Today just tried again , media still not work. Chat port Default no problem text can send , but the media port default not working , I tried 587 or 7777, both no work . I tried to update the Whatsapp APP to latest version also reboot my phone . tried many times , still no working I checked the ports status on ping.pe . it shows all okay and the port is open all green . Now I really don't know what to do next , until now I don't see anyone can successfully work both in text and media , just some youtuber making useless tutorial video to be freeloaders by using public whatsapp proxy IPs not consiering any risk , just want to wait someone else do the hard work and feed the food to his month. |
When you say it shows "Connected", do you mean it is not showing "Media: unavailable"? If "Media: unavailable" is not shown, then media should work.
|
Looks like you do have an active media connection. ("WhatsApp Error" responses are expected when sending the curl request.) I am curious to see what the underlying issue is. Please make sure to submit a report! When you say media is not working, do you mean while proxy enabled, you can't send media messages (e.g., a photo) that are delivered (one-tick)? |
One other thing to check is whether the proxy still shows "Connected" as in the picture you shared after 15-30 seconds. |
Feedback from whatsapp offcial , they can't deal with it , so now we are back to the beginning, text works ,media no |
Really appreciate the debugging information shared here @MikeStick ! Can you please try connecting to the proxy and sending media again, and submit a bug report after? Thanks! |
Don't mail me more, please
…On Tue, 29 Aug 2023, 07:02 Ercan Ozturk, ***@***.***> wrote:
Really appreciate the debugging information shared here @MikeStick
<https://github.com/MikeStick> ! Can you please try connecting to the
proxy and sending media again, and submit a bug report after?
Thanks!
—
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6533DCX3VBDFBCPFLV6HWTXXVSTXANCNFSM6AAAAAAZU75AJQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi, could you please let me know the proxy address you are using and let me try if it works for me or not? Thanks! |
I can confirm Proxy only works for text |
Ok
Pada tanggal Sen, 4 Sep 2023 06.22, JellyVPN ***@***.***>
menulis:
… I can confirm Proxy only works for text
Video, Photo, Voice Call and Video Call not working
Incoming call will show but when answer stay in connecting
this is a huge issue
—
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BB4A44MJD7HBTVQJUFXHYV3XYT7JZANCNFSM6AAAAAAZU75AJQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Voice call and video call can use under proxy service. However, voice message, video message and other media message cannot be sent and received under proxy service. This is a big issue and MUST BE SOLVED asap. |
Voice and video calls are currently not supported via proxies. If you are using a proxy with media support -- i.e., the proxy page does not show "Media: unavailable", please create an issue on this repo regarding proxy set up issues, and file a bug report through WhatsApp help on the app. |
My wife in Mainland China uses one of the proxy server provided by https://whatsapp-proxy.com/ to connect to Whatsapp. She confirmed that voice call & video call CAN BE USED under proxy connection in Mainland China. However, voice messages, pictures & files cannot be sent & received under proxy connection. |
I have the same issue |
Hi, can I have the IP address of your proxy so that I can test if it works for me or not? Thanks! |
Could you please submit a bug report in the app and let us know in here when you do? |
Hi Guys, I am here in mainland china. I Don't know how to build my own proxy server. I just tested almost every free proxy listed on https://whatsapp-proxy.com/ |
Hi, my wife is also in mainland china. She also has the same problem. We also wish to have a proxy which works for media. Whatsapp introduced media supporting in June 2023. The free proxies listed on https://whatsapp-proxy.com/ were built in January 2023. I guess the owners of the proxy servers do not updated the function of the servers. This is a big problem for Whatsapp proxy service. They should make sure the proxy service which works for media before launched in January 2023. Now, they are lazy to update the servers since almost nobody complain for this issue. I wish a free media supporting Whatsapp proxy server will be available in the nearest future. |
I also have this problem, sometimes proxy is "connected" and texts send rapidly but medias don't, sometimes proxy for chat is connected but for media not, and sometimes everything works. This "sometimes" words are so random situations. For example, on a specific cellular network service provider it works great but on other providers don't. Also, minutes or location can be change the behavior of proxy. I think maybe it's a GFW issue, but I don't know why chats work well always but media not. Isn't their protocol and encryption the same? |
Like you, I changed the default port of WhatsApp and the solution was solved. frontend haproxy_v4_whatsapp_net bind ipv4@:587 default_backend wa_whatsapp_net backend wa_whatsapp_net backend wa backend wa_http Please do not modify g.whatsapp.net:5222 and g.whatsapp.net:80, this is the only channel to the WhatsApp server media files |
check \proxy-main\proxy\src\proxy_config.cfg file ` bind ipv4@:587 default_backend wa_whatsapp_net backend wa_whatsapp_net backend wa backend wa_http |
@JerichoWord |
Media proxy is currently implemented in a very bad (and non-standard) way. The client expect the proxy server to be a CDN endpoint of whatsapp media CDN and send plaintext whatsapp domain names in TLS SNI field, making it very easy to sniff and block connections to proxy servers. And SNI blocking has already been a known thing for some countries. The only way to solve this problem is to implement a highly anonymous proxy which immunes to MITM attack, which we all know there's been plenty of them. Also it's out of the responsibility of WhatsApp team to solve this problem, So the best way is to first establish a robust tunnel through the firewall, and deploy a whatsapp proxy server (better a private one) behind the firewall using this tunnel to access whatsapp server. I've added instructions to setup a private server (which won't be scanned and abused by script kiddos) in a PR (#229), you could probably check it out @thantez |
I see. I will test it and notice you and others. Thanks for your help. |
@ttimasdf Hello again. I tested your implementation by Traefik and till issue is there. Chat is ok, but media can't connect yet. I don't use any custom SSL and follow instruction. |
Can you give me the IP address of the proxy you are using so that I can
test if it works for me or not? Thanks!
…On Sat, 11 Nov 2023 at 23:04, M.Mahdi Bakhshi ***@***.***> wrote:
@ttimasdf <https://github.com/ttimasdf> Hello again. I tested your
implementation by Traefik and till issue is there. Chat is ok, but media
can't connect yet. I don't use any custom SSL and follow instruction.
—
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BCCWOEVUXYAHJGU7ZA5KHPTYD6HXBAVCNFSM6AAAAAAZU75AJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWHAZTQOBUHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
did you try your server ping to to |
因为我无法使用5000以下的端口,我把端口修改成了其他端口,然后我就发现了我无法使用媒体文件后来我才知道。 如果你修改了WhatsApp的默认端口80和443和5222和8080和8443和7777,那你要注意 你是否不小心修改到了\proxy-main\proxy\src\proxy_config.cfg这个文件,因为这个文件是把数据传递到WhatsApp服务器的,不要修改\proxy-main\proxy\src\proxy_config.cfg中的whatsapp.net:443和g.whatsapp.net:5222和g.whatsapp.net:80否则你将无法使用媒体文件 |
Yup. It's ok. |
After more than 6 months and still this is known bug and developers didn't fixed it yet |
Hi @JellyVPN, Can you please submit a bug report when you experience the issue and let me know here when you do? Thanks! |
Hello |
Hi @habibi1365, If the proxy you are connecting to supports media and you are not able send media -- even though the app shows "Connected", please file a bug and let us know, we will investigate! |
Thank you for your reply, please leave a telegram ID so that I can send you the proxy t.me/habibi1365 |
Que
Em qua., 22 de nov. de 2023, 11:29, JerichoWord ***@***.***>
escreveu:
… I also have this problem, sometimes proxy is "connected" and texts send
rapidly but medias don't, sometimes proxy for chat is connected but for
media not, and sometimes everything works. This "sometimes" words are so
random situations. For example, on a specific cellular network service
provider it works great but on other providers don't. Also, minutes or
location can be change the behavior of proxy. I think maybe it's a GFW
issue, but I don't know why chats work well always but media not. Isn't
their protocol and encryption the same?
check \proxy-main\proxy\src\proxy_config.cfg file
frontend haproxy_v4_whatsapp_net maxconn 27495 #PUBLIC_IP bind ipv4@_:587
bind ipv4@_:7777 default_backend wa_whatsapp_net backend wa_whatsapp_net
default-server check inter 60000 observe layer4 server whatsapp_net_443
whatsapp.net:443 backend wa default-server check inter 60000 observe
layer4 send-proxy server g_whatsapp_net_5222 g.whatsapp.net:5222 backend
wa_http default-server check inter 60000 observe layer4 send-proxy server
g_whatsapp_net_80 g.whatsapp.net:80
@JerichoWord <https://github.com/JerichoWord> Hi. I couldn't understand
your solution. Do you solve this issue by changing HAProxy config? If this
works for you, please write new config as code (by write triple ` around
code), I think some of your codes are compiled as Markdown and made the
text wrong! Thanks.
如果你修改了WhatsApp的默认端口80和443和5222和8080和8443和7777,那你要注意
你是否不小心修改到了\proxy-main\proxy\src\proxy_config.cfg这个文件,因为这个文件是把数据传递到WhatsApp服务器的,不要修改\proxy-main\proxy\src\
proxy_config.cfg中的whatsapp.net:443
<http://proxy_config.xn--cfgwhatsapp-218ql903b.net:443>和
g.whatsapp.net:5222和g.whatsapp.net:80否则你将无法使用媒体文件
—
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARMYLM2LZTMESMYTZUCUOV3YFYD4PAVCNFSM6AAAAAAZU75AJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSHA3TSNBYGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Still can't send media via proxy on andriod whatsapp |
I have some solution , try it and you can check live demo on FastWSapi.com Run this some command docker pull facebook/whatsapp_proxy:latest systemctl start docker docker run -d -p 8008:80 -p 8444:443 -p 5222:5222 -p 8080:8080 -p 8443:8443 -p 8222:8222 -p 8199:8199 -p 588:587 -p 7777:7777 --user root facebook/whatsapp_proxy:latest if any error example : Bind for 0.0.0.0:8008 failed: port is already allocated. Kill process running on specific ports in Ubuntu and windows | Fix error “Address already in use” How to kill ports in Ubuntu kill $(lsof -ti :$PORT) kill -9 $(lsof -ti :$PORT) sudo kill -9 $(lsof -ti :$PORT) More Info You Check Live demo on FastWSapi.com |
Only proxies that are set up on AWS servers work correctly.also on android can not send Media {i tested all ports} |
This is WhatsApp's problem, it should be fixed very quickly, but it doesn't think about it at all. |
|
Solution: HAProxy Port Binding Issue
Solution Change the binding ports for HAProxy to values greater than 5000, such as 587 and 7777. Update your configuration file with the following:
Check Configuration File: Ensure that you haven’t accidentally modified the WhatsApp server address in the \proxy-main\proxy\src\proxy_config.cfg file. Pay special attention to:
Do not change g.whatsapp.net:5222 and g.whatsapp.net:80, as these are the only channels to access WhatsApp media files. Security Reasons: Most operating systems treat ports below 1024 as privileged ports, only accessible by specific users (like root). This is to prevent misuse of system resources by regular users or processes. By setting HAProxy's binding ports to values above 5000 and ensuring the WhatsApp server settings in the configuration file are correct, you can resolve the port binding issue. |
I m using VPS to create a whatsapp proxy server following the tutorial all no problem . now showing "Connected" on my whatsapp
but only can send text, can't send/receive pictures videos and documents. it will be a great help and convenient if this can be fixed.
Telegram Proxy works perfectly by using SOCKS 5 / HTTPS/ MTP Proto Proxy . Learn from each other not a bad thing.
The text was updated successfully, but these errors were encountered: