Example configuration for Jitsi + Coturn?

[andreas1107 (Andreas)]

1. The problem I’m having:

I’m trying to set up reverse proxy for three services, each with their own domain/subdomain

1. Jitsi meet
2. Coturn
3. Web

On the same machine.

I found a few adjacent examples:

Using Coturn with other services that are reverse proxied?

I’m looking for a quick start on how to use caddy for reverse proxy while coturn is also running on the host. This is all done in a docker-compose. Coturn is generally run in docker host mode because it uses a lot of ports and large port ranges don’t work well in docker. It’s not clear to me if the coturn traffic can just completely avoid caddy or if it would have to be proxied to the coturn container - and if so, is that a reasonable thing to do?

Creating and managing a PEM certificate for another container

1. Caddy version (caddy version): v2.4.3 h1:Y1FaV2N4WO3rBqxSYA8UZsZTQdN+PwcoOcAiZTM8C0I= 2. How I run Caddy: via docker compose a. System environment: ubuntu c. Service/unit/compose file: services: caddy: image: caddy:2 ports: - "80:80" - "443:443" volumes: - ./Caddyfile:/etc/caddy/Caddyfile - ./data/caddy/data:/data - ./data/caddy/config:/config - ./data/caddy/log:/var/log 3. The problem I’m having: I want to secure my coturn server…

But not 100% about the use case of TURN+Jitsi onthe same machine.

Caddy is what the Jitsi team recommends people to use. I use Apache today but couldn’t get coturn working on the same machine, so I thought I’d check out Caddy instead. Hopefully the findings here will be useful to others

Thanks!
Andreas

[francislavoie]

I don’t think Coturn is HTTP, right? It’s a separate TCP or UDP protocol.

Caddy only ships with an HTTP server, so it can’t be used to proxy TURN traffic unless you use something like GitHub - mholt/caddy-l4: Layer 4 (TCP/UDP) app for Caddy.

You should just expose the port of your Coturn server publicly, don’t try to proxy it. It doesn’t use TLS anyway (I think) so there would be no benefit to proxying it anyway.

The other HTTP parts should be trivial to proxy with the reverse_proxy directive.

What did you try? Please completely fill out the help topic template as per the forum rules.