Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

After update Jitsi Meet: You have been disconnected, and not able to reinstall/install #131

Open
stepcellwolf opened this issue Dec 6, 2023 · 10 comments
Open

After update Jitsi Meet: You have been disconnected, and not able to reinstall/install #131

stepcellwolf opened this issue Dec 6, 2023 · 10 comments

Comments

@stepcellwolf
Copy link

Describe the bug

After the upgrade I got the same error messages as described in "You have been disconnected" Forum

Not able to re-install, or even install a fresh latest version of Jitsi Meet into new subdomain.
Jitsi Meet 2.0.9111~ynh1

Context

  • Hardware: VPS bought online
  • YunoHost version: YunoHost 11.2.8 (stable)
  • I have access to my server: Through SSH and through the webadmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: Jitsi Meet 2.0.9111~ynh1

Steps to reproduce

After updating the Jitsi Meet and prosody I get the You have been disconnected after providing the credentials.
Tried to deleted and reinstall, or even install the latest version on a different subdomain, still not working getting the same error message provided below int he log section.

ERROR - Unable to install jitsi: An error occurred inside the app installation script

No success with reload the firewall either: [ sudo yunohost firewall reload ]

Logs

ERROR - Unable to install jitsi: An error occurred inside the app installation script

Full logs available at link.
@stepcellwolf
Copy link
Author

stepcellwolf commented Dec 6, 2023 •
edited
Loading

More details on the troubleshooting.
I also tried to install it with test branch and debug output, still failing. I guess problem with Metronome. See below
sudo yunohost app install https://github.com/YunoHost-Apps/jitsi_ynh/tree/testing --debug

118253 DEBUG [##########+++++.....] > Enabling Metronome...
119338 WARNING Job for metronome.service failed because the control process exited with error code.
119338 WARNING See "systemctl status metronome.service" and "journalctl -xe" for details.
119824 WARNING [Error] Dec 06 13:26:37 systemd[1]: metronome.service: Failed with result 'exit-code'.
119825 WARNING Dec 06 13:26:37 systemd[1]: Failed to start LSB: Metronome XMPP Server.
119825 WARNING Dec 06 13:30:25 systemd[1]: Starting LSB: Metronome XMPP Server...
119826 WARNING Dec 06 13:30:25 metronome[929203]: Starting Metronome XMPP Server: metronome
119827 WARNING Dec 06 13:30:25 metronome[929220]:  failed!
119827 WARNING Dec 06 13:30:25 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
119828 WARNING Dec 06 13:30:25 systemd[1]: metronome.service: Failed with result 'exit-code'.
119828 WARNING Dec 06 13:30:25 systemd[1]: Failed to start LSB: Metronome XMPP Server.
119829 WARNING Dec 06 16:47:43 systemd[1]: Starting LSB: Metronome XMPP Server...
119829 WARNING Dec 06 16:47:43 metronome[989712]: Starting Metronome XMPP Server: metronome
119830 WARNING Dec 06 16:47:43 metronome[989724]:  failed!
119830 WARNING Dec 06 16:47:43 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
119831 WARNING Dec 06 16:47:43 systemd[1]: metronome.service: Failed with result 'exit-code'.
119831 WARNING Dec 06 16:47:43 systemd[1]: Failed to start LSB: Metronome XMPP Server.
119831 WARNING Dec 06 22:46:58 systemd[1]: Starting LSB: Metronome XMPP Server...
119831 WARNING Dec 06 22:46:58 metronome[1076374]: Starting Metronome XMPP Server: metronome
119832 WARNING Dec 06 22:46:58 metronome[1076386]:  failed!
119832 WARNING Dec 06 22:46:58 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
119832 WARNING Dec 06 22:46:58 systemd[1]: metronome.service: Failed with result 'exit-code'.
119833 WARNING Dec 06 22:46:58 systemd[1]: Failed to start LSB: Metronome XMPP Server.
119850 WARNING [Error] Dec 06 11:00:40 general	error	No enabled VirtualHost entries found in the config file.
119851 WARNING Dec 06 11:00:40 general	error	At least one active host is required for Metronome to function. Exiting...
119852 WARNING Dec 06 11:03:06 general	error	No enabled VirtualHost entries found in the config file.
119853 WARNING Dec 06 11:03:06 general	error	At least one active host is required for Metronome to function. Exiting...
119853 WARNING Dec 06 11:20:36 general	error	No enabled VirtualHost entries found in the config file.
119854 WARNING Dec 06 11:20:36 general	error	At least one active host is required for Metronome to function. Exiting...
119855 WARNING Dec 06 11:23:30 general	error	No enabled VirtualHost entries found in the config file.
119855 WARNING Dec 06 11:23:30 general	error	At least one active host is required for Metronome to function. Exiting...
119856 WARNING Dec 06 11:35:09 general	error	No enabled VirtualHost entries found in the config file.
119856 WARNING Dec 06 11:35:09 general	error	At least one active host is required for Metronome to function. Exiting...
119857 WARNING Dec 06 11:38:18 general	error	No enabled VirtualHost entries found in the config file.
119858 WARNING Dec 06 11:38:18 general	error	At least one active host is required for Metronome to function. Exiting...
119858 WARNING Dec 06 13:26:37 general	error	No enabled VirtualHost entries found in the config file.
119859 WARNING Dec 06 13:26:37 general	error	At least one active host is required for Metronome to function. Exiting...
119859 WARNING Dec 06 13:30:25 general	error	No enabled VirtualHost entries found in the config file.
119860 WARNING Dec 06 13:30:25 general	error	At least one active host is required for Metronome to function. Exiting...
119861 WARNING Dec 06 16:47:43 general	error	No enabled VirtualHost entries found in the config file.
119861 WARNING Dec 06 16:47:43 general	error	At least one active host is required for Metronome to function. Exiting...
119862 WARNING Dec 06 22:46:58 general	error	No enabled VirtualHost entries found in the config file.
119862 WARNING Dec 06 22:46:58 general	error	At least one active host is required for Metronome to function. Exiting...
119919 DEBUG [###############+++++] > Removal of prosody completed

@stepcellwolf
Copy link
Author

And restore from backup is not working too. Link to the logs.

@JB6398
Copy link

JB6398 commented Dec 10, 2023

Hello, same problem.
I might add that a message says the login password or identification is incorrect.

@CodeShakingSheep
Copy link
Member

CodeShakingSheep commented Dec 15, 2023 •
edited
Loading

Same here. Cannot start a meeting after the last Jitsi + Prosody update. The Prosody logs indicate that there is a problem with the certificate manager.

LOGFILE: journalctl
-- Journal begins at Fri 2023-10-27 17:31:06 UTC, ends at Fri 2023-12-15 16:13:46 UTC. --
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for breakout.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: breakout.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for conferenceduration.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conferenceduration.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for conferenceduration.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conferenceduration.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for conferenceduration.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conferenceduration.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for focus.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: focus.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for focus.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: focus.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for focus.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: focus.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for guest.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: guest.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for guest.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: guest.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for guest.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: guest.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/auth.meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for internal.auth.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: internal.auth.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/auth.meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for internal.auth.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: internal.auth.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/auth.meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for internal.auth.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: internal.auth.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for conference.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conference.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for conference.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conference.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for conference.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: conference.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for lobby.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: lobby.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for lobby.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: lobby.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for lobby.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: lobby.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Check that the path is correct, and the file exists. (for speakerstats.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: speakerstats.meet.[JITSI-DOMAIN.TLD]:tls: Error creating context for c2s: error loading private key (No such file or directory)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for speakerstats.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: speakerstats.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sout: error loading private key (system lib)
Dec 15 16:13:46 prosody[3501709]: certmanager: SSL/TLS: Failed to load '/etc/prosody/certs/meet.[JITSI-DOMAIN.TLD].key': Previous error (see logs), or other system error. (for speakerstats.meet.[JITSI-DOMAIN.TLD])
Dec 15 16:13:46 prosody[3501709]: speakerstats.meet.[JITSI-DOMAIN.TLD]:tls: Error creating contexts for s2sin: error loading private key (system lib)

Edit: Now the Prosody error changed.

Dec 16 11:40:25 prosody[3501709]: c2s55fbb600a5f0: No TLS context available for c2s. Earlier error was: error loading private key (No such file or directory)

See https://paste.yunohost.org/qofunomoyo

@RaggedStaff
Copy link

Same story ofor me... encountering similar SSO/Prosody errors removal & attempting to reinstall fails.

For one reason or another, I tried reinstalling from the testing branch (using cli cmd from the bottom of the README.md), that install works & jitsi seems to be working ok for me now, hoping that might be useful to others.

@trendless
Copy link

trendless commented Dec 17, 2023 •
edited
Loading

The files it's looking for in /etc/prosody/certs are links to files in /var/lib/prosody that aren't there. For whatever reason, the files that should be in /var/lib/prosody are actually in /home/yunohost.app/prosody.

I'm not sure if they're supposed to be linked or copied, so I copied them over, set them all to be owned by prosody, then restarted the service.

@stepcellwolf
Copy link
Author

I can confirm that the workaround is working by installing the test branch
sudo yunohost app install https://github.com/YunoHost-Apps/jitsi_ynh/tree/testing --debug

@artybdrlt
Copy link

I can confirm that the workaround is working by installing the test branch sudo yunohost app install https://github.com/YunoHost-Apps/jitsi_ynh/tree/testing --debug

Thanks for the workaround. It's working on my end as well. I guess this will get fixed eventually.

@hermann-san
Copy link

I can confirm that the workaround is working by installing the test branch
sudo yunohost app install https://github.com/YunoHost-Apps/jitsi_ynh/tree/testing --debug

I've tried this , but it' s not working for me

26275 DEBUG action [35827.1] executed in 26.023s
26276 DEBUG lock has been released
26276 ERROR Aborting.

@hermann-san
Copy link

today I did try it again to install Jitsi. This time I've remove Metronom, as mention when installing Jitsi. Maybe I've missed that last time.
sudo apt remove metronome
After I did that on the SSH Terminal , I've used the admin gui to start the installation and things went fine. The conference is working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@trendless @stepcellwolf @hermann-san @RaggedStaff @CodeShakingSheep @artybdrlt @JB6398