[jitsi-users] errors installing jitsi-meet via deb package


#1

sry to break the thread i had digest on - could not reply to my OP

i managed to install the deb package on the raring box though the first
atempt was broken because apache was running

Setting up jitsi-meet (1.0.1-97) ...
* Restarting nginx nginx
               nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address
already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
invoke-rc.d: initscript nginx, action "restart" failed.
dpkg: error processing jitsi-meet (--configure):
subprocess installed post-installation script returned error exit status 1

after stopping apache and purging the failed jitsi-meet - it seems to have
installed correctly - though chromium shows me a sad face when browing to
port 80 with "This webpage has a redirect loop"

on the trusty box i got the same errors as my OP - tho it seems to have
installed in a different order this time - the only significant difference
i see is on the line follow ssl key generation was previopusly:

    writing new private key to '/var/lib/prosody/localhost.key'

this now has correctly the host name i supplied at the prompt instead of
localhost.key - as a side note i aso tried earlier to install on the trusty
box as i did successfully on raring using the INSTALL.md recipe but ran
into problem - something about lua-sec-prosody trying to clobber an
existing ssl cert