[BUG] Jellyfin gives an error 27 on specific devices

[HammyHavoc]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The current config gives an error 27 on specific devices. The solution is here and means the config file needs updating: https://jellyfin.org/docs/general/networking/nginx/

Expected Behavior

Not get an error 27

Steps To Reproduce

Try connecting to Jellyfin with a webOS device.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[HammyHavoc]

Still a problem.

[j0nnymoe]

If you've found a solution, please at least enlighten us or submit a PR fixing it.

[HammyHavoc]

If you've found a solution, please at least enlighten us or submit a PR fixing it.

I haven't found any solution at present short of not using webOS devices.

[j0nnymoe]

The current config gives an error 27 on specific devices. The solution is here and means the config file needs updating: https://jellyfin.org/docs/general/networking/nginx/

You said the solution is here, have you tried applying any of that first?

[HammyHavoc]

The current config gives an error 27 on specific devices. The solution is here and means the config file needs updating: https://jellyfin.org/docs/general/networking/nginx/

You said the solution is here, have you tried applying any of that first?

No, because I don't have a webOS device to test it with myself.

[j0nnymoe]

I would've assumed that because you reported the issue, that you were able to recreate it.

[HammyHavoc]

I would've assumed that because you reported the issue, that you were able to recreate it.

Relatives with webOS who live a significant distance from me and are very old are likely not to be the most helpful in ongoing testing, but I have seen the problem first-hand.

I figured someone else must have the same issue.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.