SOLVED: Jellyfin don't want to start

[Bcause42]

Journalctl -xeu jellyfin :

Code:

Oct 28 20:15:29 movies jellyfin[2132]:    at System.Xml.XmlReader.MoveToContent()
Oct 28 20:15:29 movies jellyfin[2132]:    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationRead>
Oct 28 20:15:29 movies jellyfin[2132]:    at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** argu>
Oct 28 20:15:29 movies jellyfin[2132]:    at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, B>
Oct 28 20:15:29 movies jellyfin[2132]:    --- End of inner exception stack trace ---
Oct 28 20:15:29 movies jellyfin[2132]:    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlRe>
Oct 28 20:15:29 movies jellyfin[2132]:    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlRe>
Oct 28 20:15:29 movies jellyfin[2132]:    at Emby.Server.Implementations.Serialization.MyXmlSerializer.Deserial>
Oct 28 20:15:29 movies jellyfin[2132]:    at Emby.Server.Implementations.Serialization.MyXmlSerializer.Deserial>
Oct 28 20:15:29 movies jellyfin[2132]:    at Jellyfin.Server.Migrations.MigrationRunner.RunPreStartup(ServerApp>
Oct 28 20:15:29 movies jellyfin[2132]:    at Jellyfin.Server.Program.StartApp(StartupOptions options)
Oct 28 20:15:29 movies jellyfin[2132]:    at Jellyfin.Server.Program.<Main>(String[] args)
Oct 28 20:15:29 movies systemd[1]: jellyfin.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit jellyfin.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 6.
Oct 28 20:15:29 movies systemd[1]: jellyfin.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit jellyfin.service has entered the 'failed' state with result 'signal'.
Oct 28 20:15:29 movies systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit jellyfin.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Oct 28 20:15:29 movies systemd[1]: Stopped jellyfin.service - Jellyfin Media Server.
░░ Subject: A stop job for unit jellyfin.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit jellyfin.service has finished.
░░
░░ The job identifier is 2945 and the job result is done.
Oct 28 20:15:29 movies systemd[1]: jellyfin.service: Start request repeated too quickly.
Oct 28 20:15:29 movies systemd[1]: jellyfin.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit jellyfin.service has entered the 'failed' state with result 'signal'.
Oct 28 20:15:29 movies systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.
░░ Subject: A start job for unit jellyfin.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit jellyfin.service has finished with a failure.
░░
░░ The job identifier is 2945 and the job result is failed.

---

The logs are not reachable :

Code:

sudo cd /var/log/jellyfin/
sudo: cd: command not found
sudo: "cd" is a shell built-in command, it cannot be run directly.
sudo: the -s option may be used to run a privileged shell.
sudo: the -D option may be used to run a command in a specific directory.

and "ls -l /var/log/jellyfin give me results (see in attachment)