From f1f4738c7e8e3e52bb8ebc5e74d82c16400d6470 Mon Sep 17 00:00:00 2001 From: Ercan Ozturk Date: Tue, 10 Jan 2023 21:33:53 -0800 Subject: [PATCH] Add solution for haproxy issue This was asked in https://github.com/WhatsApp/proxy/issues/99 and the related haproxy issue (https://github.com/docker-library/haproxy/issues/160) does have the solution -- as confirmed by the issue owner. Adding it to the FAQ for future questions. --- FAQ.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 82cc05b..b1a9708 100644 --- a/FAQ.md +++ b/FAQ.md @@ -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. \ No newline at end of file +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.