This is for some legacy branded fairmeeting instances. Sine Dec 2023 we run most fairmeeting instances on kubernetes https://git.fairkom.net/hosting/k8s-deployments/fairmeeting/.
This is for some legacy branded fairmeeting instances. Sine Dec 2023 we run most fairmeeting instances on kubernetes https://git.fairkom.net/hosting/k8s-deployments/fairmeeting/.
### Installation Notes
### Installation Notes
Code is in `/usr/share/jitsi-meet/`
Code is in `/usr/share/jitsi-meet/`
Settings are in `/etc/jitsi`
Settings are in `/etc/jitsi`
TURN server settings in https://git.fairkom.net/hosting/coturn/-/wikis/home
TURN server settings in https://git.fairkom.net/hosting/coturn/-/wikis/home
## Jitsi Meet installation
## Jitsi Meet installation
new installation on Hetzner Cloud Server run 2021
new installation on Hetzner Cloud Server run 2021
~~new installation 02MAY2020 on internex server based in Austria~~
~~new installation 02MAY2020 on internex server based in Austria~~
~~installation 16JUN2018 on an OVH VPS, goal was to test, if performance is better then on heu20 VPS, which always had a lot of video packet dropouts and yes, it was much better~~
~~installation 16JUN2018 on an OVH VPS, goal was to test, if performance is better then on heu20 VPS, which always had a lot of video packet dropouts and yes, it was much better~~
following video guideline here https://jitsi.org/news/new-tutorial-installing-jitsi-meet-on-your-own-linux-server/
following video guideline here https://jitsi.org/news/new-tutorial-installing-jitsi-meet-on-your-own-linux-server/
installing stable build https://jitsi.org/downloads/ with nginx
installing stable build https://jitsi.org/downloads/ with nginx
[apt install log auf vanilla Debian stretch](jitsiaptlog)
[apt install log auf vanilla Debian stretch](jitsiaptlog)
### ufw
### ufw
```
```
22/tcp ALLOW Anywhere
22/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
10000:20000/udp ALLOW Anywhere
10000:20000/udp ALLOW Anywhere
4443 ALLOW Anywhere fallback jitsi?
4443 ALLOW Anywhere fallback jitsi?
50600 ALLOW Anywhere SIP
50600 ALLOW Anywhere SIP
178.63.167.177 50600 ALLOW FWD 127.0.0.1 5060 forward to Asterisk
178.63.167.177 50600 ALLOW FWD 127.0.0.1 5060 forward to Asterisk
Monitoring access from:
Monitoring access from:
92.222.184.0/24
92.222.184.0/24
92.222.185.0/24
92.222.185.0/24
92.222.186.0/24
92.222.186.0/24
167.114.37.0/24
167.114.37.0/24
54.37.72.135/32
54.37.72.135/32
```
```
### restart
### restart
```
```
service jitsi-videobridge restart
service jitsi-videobridge restart
service jicofo restart
service jicofo restart
service jigasi restart
service jigasi restart
```
```
## Upgrading
## Upgrading
Clone production to a [staging VM](staging-server) and test there all changes that come with the new release.
Clone production to a [staging VM](staging-server) and test there all changes that come with the new release.
Check new config variables with https://shawnchin.github.io/jitsi-config-differ/
Check new config variables with https://shawnchin.github.io/jitsi-config-differ/
### CSS handling
Check env variables at https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml
We have set from each brand a symbolic link to `/usr/share/jitsi-meet/css/all-fixed.css` in case we need to fix several classes in the generic `all.css` file. ~~ No more need to adapt `all.css` as described here https://git.fairkom.net/hosting/fairmeeting/-/issues/169 ~~
### CSS handling
```
We have set from each brand a symbolic link to `/usr/share/jitsi-meet/css/all-fixed.css` in case we need to fix several classes in the generic `all.css` file. ~~ No more need to adapt `all.css` as described here https://git.fairkom.net/hosting/fairmeeting/-/issues/169 ~~
root@staging:/usr/share/jitsi-meet/css
cp all.css all-fixed.css
```
```
root@staging:/usr/share/jitsi-meet/css
cp all.css all-fixed.css
We have now in each brand an extra `custom.css` with custom classes only. It might be necessary to do some fixes there.
```
Check if `/usr/share/jitsi-meet/plugin.head.html` still has the line `<link rel="stylesheet" href="css/custom.css">`.
We have now in each brand an extra `custom.css` with custom classes only. It might be necessary to do some fixes there.
### Language files + patch
Check if `/usr/share/jitsi-meet/plugin.head.html` still has the line `<link rel="stylesheet" href="css/custom.css">`.
You may need to update [Language adoptions DE](main-de-changes) and [Interface config changes](interface-config), compare with DISTRO.
### Language files + patch
We need to **patch** (use `nano`) `app.bundle.min.js`: replace the headerTitle "Jitsi Meet" with "Start your conference now" (as any change in `main.json` has no effect) ~~and remove the `#` after the dial-in PIN as described in https://git.fairkom.net/hosting/fairmeeting/-/issues/3#note_41814 (dial-in is deprecated since April 2023 see #203 ~~ .
You may need to update [Language adoptions DE](main-de-changes) and [Interface config changes](interface-config), compare with DISTRO.
~~At all brands we have a custom static folder, which usually does not change at updates. Some of the static pages do not fit well to our color and background scheme we have defined in the body of `all-fixed.css`, so we replace the CSS link e.g. for the page `dialInInfo.html` with the original `all.css`:
We need to **patch** (use `nano`) `app.bundle.min.js`: replace the headerTitle "Jitsi Meet" with "Start your conference now" (as any change in `main.json` has no effect) ~~and remove the `#` after the dial-in PIN as described in https://git.fairkom.net/hosting/fairmeeting/-/issues/3#note_41814 (dial-in is deprecated since April 2023 see #203 ~~ .
~~At all brands we have a custom static folder, which usually does not change at updates. Some of the static pages do not fit well to our color and background scheme we have defined in the body of `all-fixed.css`, so we replace the CSS link e.g. for the page `dialInInfo.html` with the original `all.css`:
Check `/etc/jitsi/jicofo/jicofo.conf` if jigasi has been activated by an update script.
Check `/etc/jitsi/jicofo/jicofo.conf` if jigasi has been activated by an update script.
These were the manual steps which we had to do after updates before we had the brand structure and used custom.css (unless you have set `apt-mark hold jitsi-meet`)
### post installation
**DEPRECATED** below
These were the manual steps which we had to do after updates before we had the brand structure and used custom.css (unless you have set `apt-mark hold jitsi-meet`)
We have automated this partially with an [update scripts](https://git.fairkom.net/operations/fairmeeting) or see the example [here](https://scheible.it/jitsi-meet-server-update-script/).
in interface_config.js you can define which functions are presented, e.g. removed for now "invite by phone"
### add domains and LE certs
We have automated this partially with an [update scripts](https://git.fairkom.net/operations/fairmeeting) or see the example [here](https://scheible.it/jitsi-meet-server-update-script/).
Let’s Encrypt certificate is being added for main domain automagically with: /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh and is also used by coturn server on same machine
### add domains and LE certs
Let’s Encrypt certificate is being added for main domain automagically with: /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh and is also used by coturn server on same machine
Adding additional domain on same server see https://git.fairkom.net/hosting/fairmeeting/-/issues/84
Adding additional domain on same server see https://git.fairkom.net/hosting/fairmeeting/-/issues/84
