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: https://paste.yunohost.org/raw/uniredegux
However, this screenshot is the result of the rollback:
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 http://127.0.0.1:3000, 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 http://127.0.0.1:8095 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
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 (edit: reported here)
(edit: