jitsi / docker-jitsi-meet

Jitsi Meet on Docker
https://hub.docker.com/u/jitsi/
Apache License 2.0
3.09k stars 1.37k forks source link

Problem with connection to the room #410

Open dmytroshokha opened 4 years ago

dmytroshokha commented 4 years ago

Hello, I installed jitsi with a quick installation, all components are working but I can’t connect to the room. SSl is not pulled. I even raised a virtual machine for this official guide I use the ip address instead of the dns name, but still I can’t connect , what am I doing wrong?

` saslauthd[220] :socket removed: /var/run/saslauthd/mux

saslauthd[220] :master exited: 0

mod_posix warn Received SIGTERM

startup info Shutting down: Received SIGTERM

general info Shutting down...

general info Shutdown status: Cleaning up

[cont-finish.d] executing container finish scripts...

[cont-finish.d] done.

[s6-finish] waiting for services.

general info Shutdown complete

[s6-finish] sending all processes the TERM signal.

[s6-finish] sending all processes the KILL signal and exiting.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[s6-init] ensuring user provided files have correct perms...exited 0.

[fix-attrs.d] applying ownership & permissions fixes...

[fix-attrs.d] done.

[cont-init.d] executing container initialization scripts...

[cont-init.d] 01-set-timezone: executing...

[cont-init.d] 01-set-timezone: exited 0.

[cont-init.d] 10-config: executing...

The directory /config/data is not owned by the current user, won't be able to write files to it

mv: cannot stat '/config/data/*.crt': No such file or directory

mv: cannot stat '/config/data/*.key': No such file or directory

[cont-init.d] 10-config: exited 0.

[cont-init.d] done.

[services.d] starting services

[services.d] done.

saslauthd[219] :num_procs : 5

saslauthd[219] :mech_option: /etc/saslauthd.conf

saslauthd[219] :run_path : /var/run/saslauthd

saslauthd[219] :auth_mech : ldap

saslauthd[219] :mmaped shared memory segment on file: /var/run/saslauthd/cache.mmap

saslauthd[219] :bucket size: 96 bytes

saslauthd[219] :stats size : 36 bytes

saslauthd[219] :timeout : 28800 seconds

saslauthd[219] :cache table: 985828 total bytes

saslauthd[219] :cache table: 1711 slots

saslauthd[219] :cache table: 10266 buckets

saslauthd[219] :flock file opened at /var/run/saslauthd/cache.flock

saslauthd[219] :using accept lock file: /var/run/saslauthd/mux.accept

saslauthd[219] :master pid is: 0

saslauthd[219] :listening on socket: /var/run/saslauthd/mux

saslauthd[219] :using process model

saslauthd[219] :forked child: 234

saslauthd[219] :forked child: 235

saslauthd[219] :forked child: 236

startup info Hello and welcome to Prosody version 0.11.5

saslauthd[236] :acquired accept lock

saslauthd[219] :forked child: 237

startup info Prosody is using the epoll backend for connection handling

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for meet.jitsi)

meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for meet.jitsi)

meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (system lib)

meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (system lib)

portmanager info Activated service 's2s' on [::]:5269, [*]:5269

portmanager info Activated service 'http' on [::]:5280, [*]:5280

portmanager info Activated service 'https' on no ports

portmanager info Activated service 'c2s' on [::]:5222, [*]:5222

portmanager info Activated service 'legacy_ssl' on no ports

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for internal-muc.meet.jitsi)

internal-muc.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for internal-muc.meet.jitsi)

internal-muc.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (system lib)

internal-muc.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (system lib)

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for recorder.meet.jitsi)

recorder.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

recorder.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)

recorder.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)

portmanager info Activated service 'component' on [*]:5347

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for focus.meet.jitsi)

focus.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

focus.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)

focus.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)

certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for muc.meet.jitsi)

muc.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

muc.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)

muc.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)

certmanager error SSL/TLS: Failed to load '/config/certs/auth.meet.jitsi.key': Check that the path is correct, and the file exists. (for auth.meet.jitsi)

auth.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

auth.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)

auth.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)

c2s563ef8a17f10 info Client connected

c2s563ef8a17f10 info Authenticated as focus@auth.meet.jitsi

focus.meet.jitsi:component warn Component not connected, bouncing error for:

c2s563ef8d6c410 info Client connected

c2s563ef8d6c410 info Authenticated as jvb@auth.meet.jitsi

jcp563ef8e9ac70 info Incoming Jabber component connection

focus.meet.jitsi:component info External component successfully authenticated `

saghul commented 4 years ago

What exacct sstepss did you follow? Please type them here.

Echolon commented 4 years ago

@dmytroshokha can you provide more details as requested?