Emby starts, but just stops after a second.

[Crevv 1]

Following the steps of a tutorial I watched online, but as soon as I reached the step where I validated the status of Emby, this pops up:

 

sudo systemctl status emby-server
○ emby-server.service - Emby Server is a personal media server with apps on just about every device
     Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Wed 2024-01-24 09:51:31 UTC; 3s ago
    Process: 30966 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS)
   Main PID: 30966 (code=exited, status=0/SUCCESS)
        CPU: 1.324s

Jan 24 09:51:31 homecrev emby-server[30966]:         TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(Sys>
Jan 24 09:51:31 homecrev emby-server[30966]:            at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThr>
Jan 24 09:51:31 homecrev emby-server[30966]:            at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, >
Jan 24 09:51:31 homecrev emby-server[30966]:            at System.Net.Sockets.Socket.Bind(EndPoint localEP)
Jan 24 09:51:31 homecrev emby-server[30966]:            at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelLi>
Jan 24 09:51:31 homecrev emby-server[30966]:            at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Socket>
Jan 24 09:51:31 homecrev emby-server[30966]:
Jan 24 09:51:31 homecrev emby-server[30966]: Info Main: Shutdown complete
Jan 24 09:51:31 homecrev systemd[1]: emby-server.service: Deactivated successfully.
Jan 24 09:51:31 homecrev systemd[1]: emby-server.service: Consumed 1.324s CPU time.

As usual, I see it inactive, so I start it up with "sudo systemctl start emby-server". It starts up fine but becomes inactive after a second or so. If anyone needs logs or anything, please tell me how to pull said logs as I'm new to Linux and all these CLI stuff. Thank you and have a great day ahead!

[Crevv 1]

Okay, I may have forgotten a move I did earlier before this install. My bad. But for anyone who encounters this, try "sudo ufw status", if it's enabled and 8096 isn't listed, disable the firewall and allow port 8096. I also realized that Jellyfin is also using port 8096 and was still running before this install, that's why Emby won't start, so disable Jellyfin too if you have that. I'm sorry that I haven't thought of this enough, but Emby works fine as expected. Thank you!

[Luke 37249]

HI, thanks for following up.