Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Franck Routier <alci@mecadu.org>
To: galene@lists.galene.org
Subject: [Galene] Help needed on network settings
Date: Wed, 23 Oct 2024 08:42:33 +0200	[thread overview]
Message-ID: <1987495.PYKUYFuaPT@tibook> (raw)

[-- Attachment #1: Type: text/plain, Size: 4195 bytes --]

Hi,

I'm trying to setup a galene instance in the following context:

* one physical server (hosted at OVH) with public IP ww.xx.yy.zz
* on this server, incus (https://linuxcontainers.org/incus/docs/main/) is used to handle different containers: galene is in one of this containers (running Ubuntu)
* another container is running nginx as a reverse proxy
* dns name galene.mydomain.net points to ww.xx.yy.zz

What I did is:

* on the main server, forward ports tcp/1194, upd/1194 and udp/18100-19100 to same ports on galene container
(I tested with netcat that this port forwarding is effective)

* on nginx, proxypass url https://galene.mydomain.net to galene container on port 10000:

server { 
   if ($host = galene.mydomain.net) { 
       return 301 https://$host$request_uri; 
   }
   listen 80; 
   server_name galene.mydomain.net; 
   return 301 https://$host$request_uri; 
}

server { 
   listen  443 http2 ssl; 
   server_name galene.mydomain.net; 

   location / { 
       proxy_pass http://10.87.94.201:10000/; 
       proxy_set_header Host $http_host; 
       proxy_set_header X-Forwarded-Host $host:$server_port; 
       proxy_set_header X-Forwarded-Server $host; 
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
       proxy_set_header  X-Real-IP $remote_addr; 
       proxy_set_header Upgrade $http_upgrade; 
       proxy_set_header Connection "Upgrade"; 
   } 

   ssl_certificate /etc/letsencrypt/live/several.mydomain.net/fullchain.pem; # managed by Certbot 
   ssl_certificate_key /etc/letsencrypt/live/several.mydomain.net/privkey.pem; # managed by Certbot

* on galene container, systemd service is launched with 'galene -http 10.87.94.201:10000 -insecure -turn ww.xx.yy.zz
:1194 -udp-range 18100-19100'

systemctl status galene says:

● galene.service - Galene 
    Loaded: loaded (/etc/systemd/system/galene.service; enabled; preset: enabled) 
   Drop-In: /run/systemd/system/service.d 
            └─zzz-lxc-service.conf 
    Active: active (running) since Tue 2024-10-22 11:57:07 UTC; 18h ago 
  Main PID: 535 (galene) 
     Tasks: 17 (limit: 76943) 
    Memory: 4.9M (peak: 9.5M) 
       CPU: 2.413s 
    CGroup: /system.slice/galene.service 
            └─535 /home/ubuntu/galene/galene -http 10.87.94.201:10000 -insecure -turn ww.xx.yy.zz:1194 -udp-range 18100-19100 

Oct 22 11:57:07 galene galene[535]: 2024/10/22 11:57:07 Starting built-in TURN server on ww.xx.yy.zz:1194 
Oct 22 11:57:07 galene galene[535]: 2024/10/22 11:57:07 Relay test successful in 12.038506ms, RTT = 162.921µs 
Oct 22 14:54:17 galene galene[535]: turn ERROR: 2024/10/22 14:54:17 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 22 18:00:47 galene galene[535]: turn ERROR: 2024/10/22 18:00:47 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 22 21:26:00 galene galene[535]: turn ERROR: 2024/10/22 21:26:00 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 22 22:37:18 galene galene[535]: turn ERROR: 2024/10/22 22:37:18 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 22 23:57:07 galene galene[535]: 2024/10/22 23:57:07 Relay test successful in 18.841846ms, RTT = 203.679µs 
Oct 23 01:02:12 galene galene[535]: turn ERROR: 2024/10/23 01:02:12 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 23 05:03:13 galene galene[535]: turn ERROR: 2024/10/23 05:03:13 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header 
Oct 23 06:29:59 galene galene[535]: turn ERROR: 2024/10/23 06:29:59 Failed to handle datagram: failed to create stun message from packet: unexpected EOF: not enough bytes to read header

Now, I can access the web UI, but it seems RTC cannot be established.

What am I missed ?
I'm not a network wizard, any help is appreciated :-)

Franck

[-- Attachment #2: Type: text/html, Size: 7148 bytes --]

             reply	other threads:[~2024-10-23  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  6:42 Franck Routier [this message]
2024-10-24  8:11 ` [Galene] " Franck Routier
     [not found] ` <172975749182.1024.2812222916835422030@gauss.local>
2024-10-24  8:18   ` Franck Routier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1987495.PYKUYFuaPT@tibook \
    --to=alci@mecadu.org \
    --cc=galene@lists.galene.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox