Jitsi installer Debian

How can I fix this?

To activate the new configuration, you need to run:
systemctl restart apache2
Enabling site jistsimeet.acceptit.lan.
To activate the new configuration, you need to run:
systemctl reload apache2
Job for apache2.service failed.
See “systemctl status apache2.service” and “journalctl -xe” for details.
invoke-rc.d: initscript apache2, action “reload” failed.
dpkg: error processing package jitsi-meet-web-config (–configure):
installed jitsi-meet-web-config package post-installation script subprocess returned error exit status 1
Setting up jicofo (1.0-508-1) …
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-web-config (= 1.0.3729-1); however:
Package jitsi-meet-web-config is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
Setting up jitsi-meet-web (1.0.3729-1) …
Processing triggers for systemd (241-7~deb10u3) …
Processing triggers for man-db (2.8.5-2) …
Processing triggers for ca-certificates (20190110) …
Updating certificates in /etc/ssl/certs…
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d…

done.
done.
Processing triggers for libc-bin (2.28-10) …
Errors were encountered while processing:
jitsi-meet-web-config
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

What is the output of this command, also check apache logs for errors. Seems apache config is wrong, for some reason.

i have reinstalled an th error didnt came again but its still not good i cant connect from the browser

journalctl -xe
gives this:


– The job identifier is 1455 and the job result is done.
Mar 13 15:12:46 jitsimeet systemd[1]: Started Prosody XMPP Server.
– Subject: A start job for unit prosody.service has finished successfully
– Defined-By: systemd
– Support: https://www.debian.org/support

– A start job for unit prosody.service has finished successfully.

– The job identifier is 1455.
Mar 13 15:12:46 jitsimeet prosody[5907]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Mar 13 15:12:46 jitsimeet prosody[5907]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Mar 13 15:12:50 jitsimeet systemd[1]: Reloading.
Mar 13 15:12:50 jitsimeet systemd[1]: /lib/systemd/system/jitsi-videobridge.service:11: PIDFile= references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid → /run/jitsi-videobridge/jitsi-v
Mar 13 15:12:50 jitsimeet systemd[1]: Reloading The Apache HTTP Server.
– Subject: A reload job for unit apache2.service has begun execution
– Defined-By: systemd
– Support: https://www.debian.org/support

– A reload job for unit apache2.service has begun execution.

– The job identifier is 1567.
Mar 13 15:12:51 jitsimeet systemd[1]: Reloaded The Apache HTTP Server.
– Subject: A reload job for unit apache2.service has finished
– Defined-By: systemd
– Support: https://www.debian.org/support

– A reload job for unit apache2.service has finished.

– The job identifier is 1567 and the job result is done.
Mar 13 15:12:51 jitsimeet systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
– Subject: Unit process exited
– Defined-By: systemd
– Support: https://www.debian.org/support

– An ExecStart= process belonging to unit apache2.service has exited.

– The process’ exit code is ‘exited’ and its exit status is 1.
Mar 13 15:12:51 jitsimeet systemd[1]: apache2.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: https://www.debian.org/support

– The unit apache2.service has entered the ‘failed’ state with result ‘exit-code’.
Mar 13 15:12:51 jitsimeet useradd[6027]: new user: name=jicofo, UID=997, GID=1001, home=/usr/share/jicofo, shell=/bin/bash
Mar 13 15:12:51 jitsimeet systemd[1]: Reloading.
Mar 13 15:12:51 jitsimeet systemd[1]: /lib/systemd/system/jitsi-videobridge.service:11: PIDFile= references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid → /run/jitsi-videobridge/jitsi-v
Mar 13 15:12:51 jitsimeet systemd[1]: Reloading.
Mar 13 15:12:51 jitsimeet systemd[1]: /lib/systemd/system/jitsi-videobridge.service:11: PIDFile= references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid → /run/jitsi-videobridge/jitsi-v
Mar 13 15:12:51 jitsimeet systemd[1]: Reloading.
Mar 13 15:12:51 jitsimeet systemd[1]: /lib/systemd/system/jitsi-videobridge.service:11: PIDFile= references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid → /run/jitsi-videobridge/jitsi-v
Mar 13 15:12:51 jitsimeet systemd[1]: Starting LSB: Jitsi conference Focus…
– Subject: A start job for unit jicofo.service has begun execution
– Defined-By: systemd
– Support: https://www.debian.org/support

– A start job for unit jicofo.service has begun execution.

– The job identifier is 1736.
Mar 13 15:12:51 jitsimeet jicofo[6106]: Starting jicofo: jicofo started.
Mar 13 15:12:51 jitsimeet systemd[1]: Started LSB: Jitsi conference Focus.
– Subject: A start job for unit jicofo.service has finished successfully
– Defined-By: systemd
– Support: https://www.debian.org/support

– A start job for unit jicofo.service has finished successfully.

– The job identifier is 1736.
Mar 13 15:12:52 jitsimeet systemd[1]: Reloading.
Mar 13 15:12:52 jitsimeet systemd[1]: /lib/systemd/system/jitsi-videobridge.service:11: PIDFile= references path below legacy directory /var/run/, updating /var/run/jitsi-videobridge/jitsi-videobridge.pid → /run/jitsi-videobridge/jitsi-v

appache log:

[Thu Mar 12 16:40:19.600547 2020] [mpm_event:notice] [pid 707:tid 140710224491648] AH00489: Apache/2.4.38 (Debian) configured – resuming normal operations
[Thu Mar 12 16:40:19.600764 2020] [core:notice] [pid 707:tid 140710224491648] AH00094: Command line: ‘/usr/sbin/apache2’
[Thu Mar 12 16:51:02.622138 2020] [mpm_event:notice] [pid 707:tid 140710224491648] AH00491: caught SIGTERM, shutting down
[Thu Mar 12 16:51:16.403756 2020] [mpm_event:notice] [pid 683:tid 140529280013440] AH00489: Apache/2.4.38 (Debian) configured – resuming normal operations
[Thu Mar 12 16:51:16.404654 2020] [core:notice] [pid 683:tid 140529280013440] AH00094: Command line: ‘/usr/sbin/apache2’
[Thu Mar 12 16:52:24.533877 2020] [mpm_event:notice] [pid 683:tid 140529280013440] AH00491: caught SIGTERM, shutting down
[Thu Mar 12 16:52:38.008673 2020] [mpm_event:notice] [pid 699:tid 140650491155584] AH00489: Apache/2.4.38 (Debian) configured – resuming normal operations
[Thu Mar 12 16:52:38.009806 2020] [core:notice] [pid 699:tid 140650491155584] AH00094: Command line: ‘/usr/sbin/apache2’
[Thu Mar 12 16:54:06.415026 2020] [mpm_event:notice] [pid 699:tid 140650491155584] AH00491: caught SIGTERM, shutting down
[Thu Mar 12 16:54:18.756188 2020] [mpm_event:notice] [pid 685:tid 139627157419136] AH00489: Apache/2.4.38 (Debian) configured – resuming normal operations
[Thu Mar 12 16:54:18.756805 2020] [core:notice] [pid 685:tid 139627157419136] AH00094: Command line: ‘/usr/sbin/apache2’
[Fri Mar 13 15:12:51.000410 2020] [mpm_event:notice] [pid 685:tid 139627157419136] AH00493: SIGUSR1 received. Doing graceful restart
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
[Fri Mar 13 15:12:51.024318 2020] [mpm_event:alert] [pid 685:tid 139627157419136] no listening sockets available, shutting down
[Fri Mar 13 15:12:51.024328 2020] [:emerg] [pid 685:tid 139627157419136] AH00019: Unable to open logs, exiting

Apparently jvb has taken over port 443 before apache being able to use it.
You can try adding this to jvb config org.jitsi.videobridge.DISABLE_TCP_HARVESTER=true in /etc/jitsi/videobridge/sip-communicator.properties, restart jvb and restart apache.

apache is working now,
but this site shows up

Then your apache config for jitsi-meet is not working.