Closed SileemFarghaly closed 8 months ago
This is a common mistake when something prevents Cosmos from functioning properly (aka. preventing it from editing itself if you use IP / port instead of a domain name):
Ah I see, I was following this guide linked to in the reddit getting started guide (https://guides.engels.zip/). Perhaps it should be removed since that method of install can cause problems.
The guide uses compose from CLI not stack, you used portainer right?
What happened?
With a clean install of cosmos-server, after I install jellyfin, the server goes down and never boots back up. The logs just cycle through the same message every minute or so. It might be getting the wrong container id? see this line in the logs
Error response from daemon: Cannot kill container: 4bee369b66fcea35299c3c6a77489ae828e4f507d292211c54d7212bb899a39d: Container 4bee369b66fcea35299c3c6a77489ae828e4f507d292211c54d7212bb899a39d is not running
What should have happened?
The server should have come back up with Jellyfin active
How to reproduce the bug?
Relevant log output
Other details
The only way I've been able to get everything back up is to delete the cosmos container and remove the jellyfin config from the routes object in
cosmos.config.json
, then recreate the containerSystem details