After spending all day trying to fight off users naming meeting rooms “test” and “Meeting” i threw this hack job together to try and restrict it:
Add the below to your nginix config AFTER the static content and BEFORE the BOSH config:
# Landing for blocking bad meeting locations
location ~ ^/(for-your-safety)/(.*)$
{
add_header 'Access-Control-Allow-Origin' '*';
alias /usr/share/jitsi-meet/$1/$2;
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php/php7.3-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
}
# Block known bad meeting names to prevent Zoomboming
location ~* ^/(test|testmeeting|staffmeeting|meeting|test[0-9]+)$
{
rewrite ^/(.*)$ https://<YOUR FULL URL>/for-your-safety/index.php permanent;
}
Add more names as you please separated by |
If you are not running PHP (i am so that i can do some fun stuff and generate random strings) remove the PHP stanza and adjust as needed.
Make a folder in the webroot (mkdir /usr/share/jitsi-meet/for-your-safety) and add your file as needed
Someone with more nginx chops could probably change it so you don’t need the Full URL, but at 10:30 on launch day i cracked it and needed a quick fix.
I made a page that says
For an extra layer of security, name your meeting something completely random such as bfedwbgtrweberf
Click here to start a meeting using that random name -OR- Click here to go back to the homepage and pick your own name
Users! Bloody users!!! No matter how many times you say “Set a password” they still don’t!
