2024-10-14, 05:37 PM
Thank you Pirate,
I did as you wrote*.
Result: same situation as previously described - server inaccessible.
Freshly installed server worked fine and was perfectly accessible until/before the restore of the original instance:
After I restored the ~8GB etc, cache and lib, server is - yet again - inaccessible, showing again splash-screen -> selectserver.html -> "cannot connect, try later".
I see "[ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings"
On " : / # jellyfin --nowebclient" on the server I get http://10.3.3.3:8096/api-docs/swagger/index.html in Browser which I have never seen before. Seems to be about the API. But at least I get a response, even though not the one expected...
In logs:
*) For the record a lil detail:
When purging the old install also the jelly apt-sources and keys should be removed to prevent this error triggered by the install-debuntu.sh:
I did as you wrote*.
Result: same situation as previously described - server inaccessible.
Freshly installed server worked fine and was perfectly accessible until/before the restore of the original instance:
After I restored the ~8GB etc, cache and lib, server is - yet again - inaccessible, showing again splash-screen -> selectserver.html -> "cannot connect, try later".
I see "[ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings"
On " : / # jellyfin --nowebclient" on the server I get http://10.3.3.3:8096/api-docs/swagger/index.html in Browser which I have never seen before. Seems to be about the API. But at least I get a response, even though not the one expected...
In logs:
Code:
[WRN] An operation of type '"SqlOperation"' will be attempted while a rebuild of table '"ImageInfos"' is pending. The database may not be in an expected state. Review the SQL generated by this migration to help diagnose any failures. Consider moving these operations to a subsequent migration.
[WRN] An operation of type '"SqlOperation"' will be attempted while a rebuild of table '"Permissions"' is pending. The database may not be in an expected state. Review the SQL generated by this migration to help diagnose any failures. Consider moving these operations to a subsequent migration.
[WRN] An operation of type '"SqlOperation"' will be attempted while a rebuild of table '"Preferences"' is pending. The database may not be in an expected state. Review the SQL generated by this migration to help diagnose any failures. Consider moving these operations to a subsequent migration.
[WRN] An operation of type '"SqlOperation"' will be attempted while a rebuild of table '"Users"' is pending. The database may not be in an expected state. Review the SQL generated by this migration to help diagnose any failures. Consider moving these operations to a subsequent migration.
(each message shows twice)
[WRN] No XML encryptor configured. Key {654762f9-d002-4cd0-b5bf-031745238eec} may be persisted to storage in unencrypted form.
...and the 404 for some manifests*) For the record a lil detail:
When purging the old install also the jelly apt-sources and keys should be removed to prevent this error triggered by the install-debuntu.sh:
Code:
E: Conflicting values set for option Signed-By regarding source https://repo.jellyfin.org/debian/ bullseye: /var/lib/extrepo/keys/jellyfin.asc != /etc/apt/keyrings/jellyfin.gpg
E: The list of sources could not be read.
ERROR: Failed to update APT repositories. Something is wrong with your APT sources, GPG keys, or Internet connection. Try again shortly or use https://jellyfin.org/contact to find us for troubleshooting.