After upgrading to 11.2.4 and attempting to upgrade Yunohost, the upgrade failed and now the subdomain is directed towards OnlyOffice

My YunoHost server

Hardware: dedicated server
YunoHost version: 11.2.4
I have access to my server : direct access
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Hello everybody, odd thing here:

I’m on Debian 11/ Bullseye.

I upgraded Yunohost to the latest version, and afterwards, tried to upgrade Invidious to the latest version - the upgrade failed - here are the logs:

However, this screenshot is the result of the rollback:

Here are the restore logs for Invidious -

Not sure what happened… any ideas?

Nextcloud upgrade failed also -

I have a similar problem, with both Onlyoffice and Invidious. This is not the first time it happens, that’s weird.

After investigating a bit, it turns out nginx proxies invidious requests to, which is answered by OnlyOffice.

Double-checking in /etc/yunohost/apps/invidious/settings.yml and /etc/yunohost/apps/onlyoffice/settings.yml, Invidious is set to use port 3000 (so the nginx config is correct), and OnlyOffice port 8095.

On the server, curl -v reveals that onlyoffice listens on 8095 as well. So, what gives? What listens on port 3000?

netstat -tnlp |grep 3000 gives the answer 2672932/example, which is very vague, but when looking at the list of process I see both documentserver and documentserver-example, which must be the culprit :thinking:

Associated with the path /var/www/onlyoffice/documentserver-example/example.

Apparently this is started by the ds-example service. So I did systemctl disable --now ds-example.service, and it looks like invidious is working now.

OnlyOffice is working as well, so I guess I’ll report this :person_shrugging: (edit: reported here)

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.