Skip to content

Commit

Permalink
Add solution for haproxy issue (WhatsApp#103)
Browse files Browse the repository at this point in the history
  • Loading branch information
eozturk1 authored Jan 11, 2023
1 parent 49825e8 commit 61df60d
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,4 +42,8 @@ the container's port 80 binds to my machine's 8081, which is what will be expose
WhatsApp currently does **NOT** support anything besides TCP proxying. This is just copying the incoming bytes
to WhatsApp on the other end. So we don't support running through any intermediary that is a HTTP proxy.

You are free to run your own pure TCP proxy as you see fit however, as long as it forwards to `g.whatsapp.net`. You aren't required to use this realization.
You are free to run your own pure TCP proxy as you see fit however, as long as it forwards to `g.whatsapp.net`. You aren't required to use this realization.

### (6) haproxy `cannot bind socket (Permission denied)`

See https://github.com/docker-library/haproxy/issues/160 for possible solutions.

0 comments on commit 61df60d

Please sign in to comment.