Add solution for haproxy issue

This was asked in #99 and the related haproxy issue (docker-library/haproxy#160) does have the solution -- as confirmed by the issue owner. Adding it to the FAQ for future questions.
WhatsApp · Jan 11, 2023 · f1f4738 · f1f4738
1 parent 49825e8
commit f1f4738
Showing 1 changed file with 5 additions and 1 deletion.
diff --git 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.
+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.