Различия

Показаны различия между двумя версиями страницы.

--- service:haproxy [17.07.2025 12:22] – [Docker] viacheslav
+++ service:haproxy [27.08.2025 04:18] (текущий) – [Coturn] viacheslav
@@ Строка 812: / Строка 812: @@
 [[https://www.haproxy.com/blog/how-to-run-haproxy-with-docker|How to Run HAProxy With Docker (In-Depth Guide)]]\\
 https://hub.docker.com/r/jmalloc/echo-server
+===== Coturn =====
+> It's totally possible to run coturn behind a load balancer successfully. The problem with op's approach is that they're trying to use the wrong type of load balancer,
+> specifically one that load-balances HTTP/S traffic (layer 7), instead of TCP/UDP (layer 4) traffic. [...] you should use a load balancer that routes UDP/TCP traffic (layer 4)
+[[https://github.com/coturn/coturn/issues/876#issuecomment-2427353771|coTURN behind load balancer in kubernetes]]
+[[https://github.com/coturn/coturn/blob/master/README.turnserver|Документация по ключам запуска]]\\
+https://github.com/steveseguin/vdo.ninja/blob/develop/turnserver.md\\
+[[https://github.com/coturn/coturn/issues/882|Help configuring haproxy reverse proxy with coturn?]]\\
+https://element-hq.github.io/synapse/latest/setup/turn/coturn.html\\
+https://element-hq.github.io/synapse/latest/setup/turn/eturnal.html
 ===== Шпаргалки =====
@@ Строка 817: / Строка 828: @@
 |URL (absolute URI) |%%http://192.168.0.12:8080/serv/login.php?lang=en&profile=2%% |
 |Scheme |http |
-|address:port |192.168.0.12:8080 |
+|Address:port |192.168.0.12:8080 |
 |Relative URI |/serv/login.php?lang=en&profile=2 |
 |Path (relative URI before "?") |/serv/login.php |