You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a few weeks, more and more videos have refused to play (all videos now) and display the error "The media could not be loaded, either because the server or network failed or because the format is not supported." The rest of the interface, including the comments, are displayed.
Context
It is a documented bug on upstream Invidious, that has been marked as resolved. I thought the latest upgrade (2024.09.28-53e8a5d6) would resolve the issue for Yunohost users, but no (at least for me). As far as I understand, installation process has changed, so the Yunohost install script should reflect that. I’ve not seen anything in the pull requests that indicate such a change, but maybe I’m wrong.
Do you experience the same issue? If yes, have you an idea on how to solve it?
The text was updated successfully, but these errors were encountered:
TLDR: Move the instance to another server if you can (else I'd try changing the container's names), use gluetun if possible and in that case configure sig_helper to use gluetun too
Hi,
Describe the bug
For a few weeks, more and more videos have refused to play (all videos now) and display the error "The media could not be loaded, either because the server or network failed or because the format is not supported." The rest of the interface, including the comments, are displayed.
Context
It is a documented bug on upstream Invidious, that has been marked as resolved. I thought the latest upgrade (2024.09.28-53e8a5d6) would resolve the issue for Yunohost users, but no (at least for me). As far as I understand, installation process has changed, so the Yunohost install script should reflect that. I’ve not seen anything in the pull requests that indicate such a change, but maybe I’m wrong.
Do you experience the same issue? If yes, have you an idea on how to solve it?
The text was updated successfully, but these errors were encountered: