Open gbakeman opened 3 years ago
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
I'm assuming this is still an issue?
Describe the bug When I enabled HTTPS and added the certificate, I clicked save but was unable to access Jellyfin on the HTTPS port. I also confirmed that it was not listening on that port on the host. When I checked the logs, I saw a couple of lines:
The context they were in didn't tell me why I needed to reboot, but I restarted the docker container anyways and sure enough, the HTTPS port was listening.
System (please complete the following information):
To Reproduce
Expected behavior Any one of the following:
Server Logs