Webserver on port 443 not reacting after update


#1

Hi,

I did an usual update today on my Jitsi-Meet VM using the repo’s (apt-get dist-upgrade):

Unpacking jitsi-meet (1.0.3344-1) over (1.0.3229-1) ...
Preparing to unpack .../jicofo_1.0-437-1_amd64.deb ...
Unpacking jicofo (1.0-437-1) over (1.0-425-1) ...
Preparing to unpack .../jitsi-meet-web_1.0.3036-1_all.deb ...
Unpacking jitsi-meet-web (1.0.3036-1) over (1.0.2942-1) ...
Preparing to unpack .../jitsi-meet-web-config_1.0.3036-1_all.deb ...
Unpacking jitsi-meet-web-config (1.0.3036-1) over (1.0.2942-1) ...
Preparing to unpack .../jitsi-meet-prosody_1.0.3036-1_all.deb ...
Unpacking jitsi-meet-prosody (1.0.3036-1) over (1.0.2942-1) ...
Preparing to unpack .../jitsi-videobridge_1087-1_amd64.deb ...
Unpacking jitsi-videobridge (1087-1) over (1077-1) ...

After the update I can’t reach my Jitsi installation via browser anymore. The https://meet.mydomain.de is not reacting anymore. I have no clue how a simple update can break this completely.

The only difference I see is that the port 443 is now bound to my IP address.
This is before the update:

root@turnserver:~# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
....
tcp6       0      0 :::5222                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::8080                 :::*                    LISTEN      1229/java       
tcp6       0      0 :::5269                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::22                   :::*                    LISTEN      1076/sshd       
tcp6       0      0 :::8888                 :::*                    LISTEN      1237/java       
tcp6       0      0 :::443                  :::*                    LISTEN      1229/java       
tcp6       0      0 :::5280                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::5281                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::10050                :::*                    LISTEN      1273/zabbix_agentd
tcp6       0      0 ::1:5347                :::*                    LISTEN      1327/lua5.1     

Turned into this after the update:

root@turnserver:~# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
....
tcp6       0      0 :::5222                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::8080                 :::*                    LISTEN      3576/java       
tcp6       0      0 :::5269                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::22                   :::*                    LISTEN      1076/sshd       
tcp6       0      0 :::8888                 :::*                    LISTEN      3721/java       
tcp6       0      0 xxx.xx.xxx.xx:443        :::*                    LISTEN      3576/java       
tcp6       0      0 :::5280                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::5281                 :::*                    LISTEN      1327/lua5.1     
tcp6       0      0 :::10050                :::*                    LISTEN      1273/zabbix_agentd
tcp6       0      0 ::1:5347                :::*                    LISTEN      1327/lua5.1     

Any ideas to help me fixing this are appreciated.


#2

This is a known issue that we are working on fixing.
I think there is a workaround: https://github.com/jitsi/jitsi-meet/issues/3512#issuecomment-429047429
org.jitsi.videobridge.rest.jetty.host=xxx.xx.xxx.xx edit this in /etc/jitsi/videobridge/sip-communicator.properties, does it work for you?


#3

I’ve found a forum entry somewhere, mentioning to set the “org.jitsi.videobridge.rest.jetty.host” entry to my FQDN. That seems to work for now.

Thank you for your reply.