Hallo,
Fehlermeldungen kann vom ALTEN System genug melden:
Da ich aber ein neues Debian habe, sind diese Meldungen nicht mehr aktuell.
Hast du im Wizard den korrekten Hostnamen deiner Installation / deines Computers verwendet und im Browser dann auch diesen Hostnamen in der URL verwendet?
Ich habe dort meine Dyndns Adresse eingetragen, Im Lan habe ich dann meine lokale IP Adresse aufgerufen, diese ging nicht. Auch am Jitsi Rechner selber konnte ich nicht auf die Seite zugreifen.
Die Hosts habe ich angepasst, name.mine.nu ist der Name meiner dyndns Adresse.
/etc/hosts
127.0.0.1 localhost name.mine.nu
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
dpkg -l | grep jitsi
ii jitsi-meet 2.0.5142-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.4466-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-turnserver 1.0.4466-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.4466-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.4466-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-376-g9f12bfe2-1 all WebRTC compatible Selective Forwarding Unit (SFU)
tail -F /var/log/jitsi/jvb.log
2020-11-12 21:14:03.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000009S. Sticky failure: false
2020-11-12 21:14:03.753 INFORMATION: [23] VideobridgeExpireThread.expire#140: Running expire()
2020-11-12 21:14:13.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000009S. Sticky failure: false
2020-11-12 21:14:23.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000009S. Sticky failure: false
2020-11-12 21:14:33.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
2020-11-12 21:14:43.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000012S. Sticky failure: false
2020-11-12 21:14:53.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
2020-11-12 21:15:03.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
2020-11-12 21:15:03.754 INFORMATION: [23] VideobridgeExpireThread.expire#140: Running expire()
2020-11-12 21:15:13.704 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
2020-11-12 21:15:23.703 INFORMATION: [24] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
tail -F /var/log/prosody/prosody.log
Nov 12 20:55:57 c2s55b2634fcca0 info Client connected
Nov 12 20:55:58 c2s55b2634fcca0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Nov 12 20:55:59 c2s55b2634fcca0 info Authenticated as
focus@auth.v.mine.nu
Nov 12 20:55:59 focus.videomeet.mine.nu:component warn Component not connected, bouncing error for: <iq type='get' from='focus@auth.videomeet.mine.nu/focus39133013337' to='focus.mine.nu' id='qyfge-36'>
Nov 12 20:55:59 jcp55b26352efb0 info Incoming Jabber component connection
Nov 12 20:55:59 focus.videomeet.mine.nu:component info External component successfully authenticated
Nov 12 20:56:03 conference.vit.mine.nu
uc_domain_mapper warn Session filters applied
Nov 12 20:56:03 c2s55b263521c90 info Client connected
Nov 12 20:56:04 c2s55b263521c90 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Nov 12 20:56:04 c2s55b263521c90 info Authenticated as
jvb@auth..mine.nu
tail -F /var/log/jitsi/jicofo.log
Jicofo 2020-11-12 20:55:59.734 INFORMATION: [1] org.jitsi.xmpp.component.ComponentBase.log() ping timeout: 5000 ms
Jicofo 2020-11-12 20:55:59.734 INFORMATION: [1] org.jitsi.xmpp.component.ComponentBase.log() ping threshold: 3
Jicofo 2020-11-12 20:56:08.867 INFORMATION: [31] org.jitsi.jicofo.xmpp.BaseBrewery.log() Added brewery instance:
jvbbrewery@internal.auth.videomeet.mine.nu/309014c1-84a5-4853-95d6-3590da7d341c
Jicofo 2020-11-12 20:56:08.925 INFORMATION: [31] org.jitsi.jicofo.bridge.BridgeSelector.log() Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.videomeet.mine.nu/309014c1-84a5-4853-95d6-3590da7d341c, relayId=null, region=null, stress=0,00]
Jicofo 2020-11-12 20:56:08.947 INFORMATION: [31] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for:
jvbbrewery@internal.auth.videomeet.mine.nu/309014c1-84a5-4853-95d6-3590da7d341c
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.dom4j.io.SAXContentHandler (file:/usr/share/jicofo/lib/dom4j-1.6.1.jar) to method com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of org.dom4j.io.SAXContentHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
/home/lockslay# tail -F /var/log/nginx/error.log
2020/11/12 20:53:35 [emerg] 4125#4125: BIO_new_file("/etc/ssl/videomeet.mine.nu.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/videomeet.mine.nu.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)
2020/11/12 20:55:54 [emerg] 574#574: BIO_new_file("/etc/ssl/videomeet.mine.nu.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/videomeet.mine.nu.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)
root@debianLockslay:/home/lockslay# apt install jitsi-meet
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
jitsi-meet ist schon die neueste Version (2.0.5142-1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.