Hello! I successfully implemented a reverse proxy service, Squid, for recording sessions using Jibri on the Jitsi-meet server configured with a custom port. The Squid listens to access from Jibri on port 443 and transfers the packets to Jitsi-meet listening on the custom port 8443, as shown in the figure below. We need not configure to transfer web socket data since the Squid doesn’t distinguish web sockets from other HTTPS connections. The configuration file of the Squid is as follows;
https_port 443 accel no-vhost defaultsite=www.mysite.com tls-cert=fullchain.pem tls-key=privkey.pem
acl mysites dst 127.0.0.1 port 8443 url_regex www.mysite.com
http_access allow mysites
cache_peer www.mysite.com parent 8443 0 no-query originserver ssl no-digest no-netdb-exchange name=proxy_SSL
cache_peer_access proxy_SSL allow mysites
cache_peer_access proxy_SSL deny !mysites
Secondary, I added two lines to the Nginx configuration file for Jitsi, /etc/nginx/sites-available/www.mysite.com.conf, to avoid error 400, “The plain HTTP request was sent to HTTPS port” on the Nginx as follows.
listen 8443 ssl;
listen [::]:8443 ssl;
ssl on; # <— added
error_page 497 https://$host:8443$request_uri; # <— added
I believe that the method is the easiest and minimum load for servers to record sessions on the stable version of Jitsi-meet with a custom port.
Web portal: BEYOND THE NET: TOOLS