2024-06-11, 10:09 PM
Stupid question - but are you able to access jellyfin on the same machine ? If you're not then the problem maybe this
If you are then yeah, it's a port-forwarding issue as you have been discussing with @dreadpirate ... On work around would be to put a reverse-proxy like nginx or caddy infront and have nginx/caddy serve jellyfin on port 80/443 ...
another workaround might be to get jellyfin itself to listen on port 80/443 ... typically port 80/443 don't get blocked by any ISP.
Code:
[2024-06-10 15:01:26.575 -05:00] [INF] [1] Namo.Plugin.InPlayerEpisodePreview.InPlayerEpisodePreviewPlugin: Attempting to inject preview script code in "C:\Program Files\Jellyfin\Server\jellyfin-web\index.html"
[2024-06-10 15:01:26.647 -05:00] [ERR] [1] Namo.Plugin.InPlayerEpisodePreview.InPlayerEpisodePreviewPlugin: Encountered exception while writing to "C:\Program Files\Jellyfin\Server\jellyfin-web\index.html": "System.UnauthorizedAccessException: Access to the path 'C:\Program Files\Jellyfin\Server\jellyfin-web\index.html' is denied.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, Int64 preallocationSize)
at System.IO.StreamWriter.ValidateArgsAndOpenPath(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.File.WriteAllText(String path, String contents)
If you are then yeah, it's a port-forwarding issue as you have been discussing with @dreadpirate ... On work around would be to put a reverse-proxy like nginx or caddy infront and have nginx/caddy serve jellyfin on port 80/443 ...
another workaround might be to get jellyfin itself to listen on port 80/443 ... typically port 80/443 don't get blocked by any ISP.