starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

Not starting on SSL port on system boot #844

New Issue
Closed
opened 2026-02-06 20:09:51 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-06 20:09:51 +03:00
Owner
Copy Link

Originally created by @brianjmurrell on GitHub (Aug 17, 2019).

Describe the bug
When my system is restarted, when Jellyfin starts, it binds to the non-SSL port just fine but doesn't bind the to SSL port. If I simply restart the service as soon as I notice this, it binds to the SSL port just fine.

To Reproduce

  1. Install Jellyfin onto Fedora 30 from https://copr.fedorainfracloud.org/coprs/brianjmurrell/jellyfin/
  2. Configure it to run on both non-SSL and SSL ports
  3. Restart the machine
  4. Notice that services on SSL don't work
  5. Use netstat -apn to confirm that it's not listening on the SSL port
  6. Use systemctl to restart jellyfin.service
  7. Retry the SSL service

Expected behavior
Should start on SSL at boot.

Logs
I've already looked in the logs for any errors (or otherwise) about which ports it's listening on and didn't see anything.

System (please complete the following information):

  • OS: Fedora 30
  • Browser: N/A
  • Jellyfin Version: 10.3.7
  • Reverse proxy: no
Originally created by @brianjmurrell on GitHub (Aug 17, 2019). **Describe the bug** When my system is restarted, when Jellyfin starts, it binds to the non-SSL port just fine but doesn't bind the to SSL port. If I simply restart the service as soon as I notice this, it binds to the SSL port just fine. **To Reproduce** <!-- Steps to reproduce the behavior: --> 1. Install Jellyfin onto Fedora 30 from https://copr.fedorainfracloud.org/coprs/brianjmurrell/jellyfin/ 1. Configure it to run on both non-SSL and SSL ports 1. Restart the machine 1. Notice that services on SSL don't work 1. Use `netstat -apn` to confirm that it's not listening on the SSL port 1. Use `systemctl` to restart `jellyfin.service` 1. Retry the SSL service **Expected behavior** Should start on SSL at boot. **Logs** I've already looked in the logs for any errors (or otherwise) about which ports it's listening on and didn't see anything. **System (please complete the following information):** - OS: Fedora 30 - Browser: N/A - Jellyfin Version: 10.3.7 - Reverse proxy: no
OVERLORD added the bugstale labels 2026-02-06 20:09:51 +03:00
OVERLORD commented 2026-02-06 20:09:54 +03:00
Author
Owner
Copy Link

@krazynez commented on GitHub (Aug 17, 2019):

Having the same problem on my Arch install. The default port for 8096 is showing, but my default port 8920 is not showing with netstat.

@krazynez commented on GitHub (Aug 17, 2019): Having the same problem on my Arch install. The default port for 8096 is showing, but my default port 8920 is not showing with netstat.
OVERLORD commented 2026-02-06 20:09:56 +03:00
Author
Owner
Copy Link

@brianjmurrell commented on GitHub (Aug 17, 2019):

To be clear though, it will start on port 8920 (in addition to 8096) if I systemctl restart jellyfin.service once the machine is up and running.

@brianjmurrell commented on GitHub (Aug 17, 2019): To be clear though, it will start on port 8920 (in addition to 8096) if I `systemctl restart jellyfin.service` once the machine is up and running.
OVERLORD commented 2026-02-06 20:09:57 +03:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Nov 15, 2019):

Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

@stale[bot] commented on GitHub (Nov 15, 2019): Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
OVERLORD commented 2026-02-06 20:09:58 +03:00
Author
Owner
Copy Link

@brianjmurrell commented on GitHub (Nov 15, 2019):

This doesn't seem to be a problem on 10.4.1 on EL7 now. I will leave the ticket open for @krazynez to comment or let the stale-bot close as it sees fit.

@brianjmurrell commented on GitHub (Nov 15, 2019): This doesn't seem to be a problem on 10.4.1 on EL7 now. I will leave the ticket open for @krazynez to comment or let the stale-bot close as it sees fit.
OVERLORD commented 2026-02-06 20:09:59 +03:00
Author
Owner
Copy Link

@krazynez commented on GitHub (Nov 15, 2019):

I switched from Arch back to Ubuntu and everything is good for me as well. Good to close.

@krazynez commented on GitHub (Nov 15, 2019): I switched from Arch back to Ubuntu and everything is good for me as well. Good to close.
OVERLORD commented 2026-02-06 20:10:00 +03:00
Author
Owner
Copy Link

@brianjmurrell commented on GitHub (Nov 17, 2019):

This doesn't seem to be a problem on 10.4.1 on EL7 now. I will leave the ticket open for @krazynez to comment or let the stale-bot close as it sees fit.

I have to take this back. Can this please be re-opened? This does still seem to be a problem:

# ss -tpln  | grep jellyfin
LISTEN     0      128       [::]:80                    [::]:*                   users:(("jellyfin",pid=1435,fd=236))

Simply restarting the jellyfin.service enables it:

# ss -tpln  | grep jellyfin
LISTEN     0      128       [::]:443                   [::]:*                   users:(("jellyfin",pid=2630,fd=239))
LISTEN     0      128       [::]:80                    [::]:*                   users:(("jellyfin",pid=2630,fd=238))

So something about starting when the system starts is preventing binding to the SSL port, that works just fine when restarting after the system has started.

Is there some debugging suggestions (i.e. logging setting, etc.) that can be made to get to the bottom of this, given that it's so reproducible?

@brianjmurrell commented on GitHub (Nov 17, 2019): > This doesn't seem to be a problem on 10.4.1 on EL7 now. I will leave the ticket open for @krazynez to comment or let the stale-bot close as it sees fit. I have to take this back. Can this please be re-opened? This does still seem to be a problem: ``` # ss -tpln | grep jellyfin LISTEN 0 128 [::]:80 [::]:* users:(("jellyfin",pid=1435,fd=236)) ``` Simply restarting the `jellyfin.service` enables it: ``` # ss -tpln | grep jellyfin LISTEN 0 128 [::]:443 [::]:* users:(("jellyfin",pid=2630,fd=239)) LISTEN 0 128 [::]:80 [::]:* users:(("jellyfin",pid=2630,fd=238)) ``` So something about starting when the system starts is preventing binding to the SSL port, that works just fine when restarting after the system has started. Is there some debugging suggestions (i.e. logging setting, etc.) that can be made to get to the bottom of this, given that it's so reproducible?
OVERLORD commented 2026-02-06 20:10:01 +03:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 17, 2020):

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 nightlies, 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.

@stale[bot] commented on GitHub (Mar 17, 2020): 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 nightlies, 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](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#844
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?