[Issue]: Files won't play over LAN if a user is already watching over WAN #3587

Closed
opened 2025-12-21 22:26:14 +01:00 by backuprepo · 1 comment
Owner

Originally created by @xkronusx on GitHub (Feb 6, 2022).

Please describe your bug

If a user is watching a video over a WAN connection, users on the LAN side won't be able to start playback of files.

If the LAN user watches via the WAN URL the file will then play.

Jellyfin Version

Other

if other:

No response

Environment

- OS: Docker container 10.8.0 Alpha 5
- Clients: Jellyfin media player
- Browser: Chrome/Opera
- Hardware Acceleration: None
- Reverse Proxy: Traefik

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @xkronusx on GitHub (Feb 6, 2022). ### Please describe your bug If a user is watching a video over a WAN connection, users on the LAN side won't be able to start playback of files. If the LAN user watches via the WAN URL the file will then play. ### Jellyfin Version Other ### if other: _No response_ ### Environment ```markdown - OS: Docker container 10.8.0 Alpha 5 - Clients: Jellyfin media player - Browser: Chrome/Opera - Hardware Acceleration: None - Reverse Proxy: Traefik ``` ### Jellyfin logs _No response_ ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
backuprepo 2025-12-21 22:26:14 +01:00
  • closed this issue
  • added the
    bug
    stale
    labels
Author
Owner

@jellyfin-bot commented on GitHub (Jun 6, 2022):

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.

@jellyfin-bot commented on GitHub (Jun 6, 2022): 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](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#3587
No description provided.