Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Still no media? #228

Open
richardgohth opened this issue Oct 24, 2023 · 13 comments
Open

Still no media? #228

richardgohth opened this issue Oct 24, 2023 · 13 comments

Comments

@richardgohth
Copy link

richardgohth commented Oct 24, 2023 •
edited
Loading

just downloaded and run on Ubuntu 20.
Proxy shows connected
But cannot send photos.
Is it supposed to be like this?
@richardgohth richardgohth reopened this Oct 24, 2023
@eozturk1
Copy link
Contributor

eozturk1 commented Nov 13, 2023 •
edited
Loading

  • You should see the media endpoint on the statistics page (See https:/WhatsApp/proxy#check-your-connection for how to reach that page).
  • Your WhatsApp proxy page should display "Connected" and it should NOT show "Media: unavailable".
  • Your Internet provider may be filtering your packets based on ports. The default port for media is 587 and changing it might help. For this, you will need to update the HaProxy configuration to bind to a different port and update the media port settings on your phone.

@richardgohth
Copy link
Author

Hi

Thanks for support.

Got progress

Now able to receive images but unable to send.

using this to invoke

docker run -it -p80:80 -p 443:443 -p 5222:5222 -p 8080:8080 -p 8443:8443 -p 8222:8222 -p 8199:8199 -p 587:587 -p 7777:7777 facebook/whatsapp_proxy:latest

Any ideas?

Thanks

Rgds

Richard, Singapore

  • You should see the media endpoint on the statistics page (See https:/WhatsApp/proxy#check-your-connection for how to reach that page).
  • Your WhatsApp proxy page should display "Connected" and it should NOT show "Media: unavailable".
  • Your Internet provider may be filtering your packets based on ports. The default port for media is 587 and changing it might help. For this, you will need to update the HaProxy configuration to bind to a different port and update the media port settings on your phone.

@fungjigroup
Copy link

Can I have the WhatsApp proxy IP address you are using?

@richardgohth
Copy link
Author

richardgohth commented Nov 23, 2023 via email

@fungjigroup
Copy link

I am from Hong Kong. Would you mind if you can provide the IP address for us to test as well? My wife is in Mainland China. I want to test if the WhatsApp proxy IP address can be used in Mainland China or not. Thanks!

@richardgohth
Copy link
Author

richardgohth commented Nov 26, 2023 via email

@fungjigroup
Copy link

fungjigroup commented Nov 26, 2023 via email

@fungjigroup
Copy link

fungjigroup commented Nov 29, 2023 via email

@fungjigroup
Copy link

Hello, I try to ping Anpr.optasia.com.sg on my computer and it replies but it cannot connect to the WhatsApp proxy in WhatsApp.

Any ideas?

Thanks!

Best Regards,

Albert, Hong Kong

@richardgohth
Copy link
Author

richardgohth commented Nov 30, 2023 via email

@offer1983
Copy link

offer1983 commented Aug 5, 2024 •
edited
Loading

#281
WhatsApp proxy hasn't been updated for a long time and is outdated.
When using curl to connect to port 587, WhatsApp's certificate is displayed, which seems relevant to your issue.
According to your description, the session is using a self-signed certificate, while the media part is using WhatsApp's certificate.

@dephea
Copy link

dephea commented Aug 5, 2024

#281 WhatsApp proxy hasn't been updated for a long time and is outdated. When using curl to connect to port 587, WhatsApp's certificate is displayed, which seems relevant to your issue. According to your description, the session is using a self-signed certificate, while the media part is using WhatsApp's certificate.

Could you please clarify if I'm supposed to host a separate ip:port for media? The thing is I'm forwarding it through free version Ngrok and I can't use two ports simultaniously

@wpyoga
Copy link

wpyoga commented Sep 11, 2024

the session is using a self-signed certificate, while the media part is using WhatsApp's certificate.

I'm having the same issue. This is what I get with curl on port 443:

* Server certificate:
*  subject: CN=1iCBLvVF330N.net
*  start date: Aug 14 03:42:48 2024 GMT
*  expire date: Aug 12 03:42:48 2034 GMT
*  issuer: CN=gYSkf3n0Uxybzdlam

This is what I get with curl on port 587:

* Server certificate:
*  subject: C=US; ST=California; L=Menlo Park; O=Meta Platforms, Inc.; CN=*.whatsapp.net
*  start date: Jun 20 00:00:00 2024 GMT
*  expire date: Sep 18 23:59:59 2024 GMT
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA

I'm guessing that at least in China, packets are scanned and HTTPS connections with certificates with CN=*.whatsapp.net are denied.

I tried to use a HTTPS reverse proxy to override the certificate, and curl seems to be able to get all the info. However, WhatsApp couldn't connect to the port for media.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@eozturk1 @wpyoga @offer1983 @dephea @richardgohth @fungjigroup