Unable to sign into the opensubtitles plugin
pd98 opened this issue · comments
Hi,
I am trying to put in my credentials for the opensubtitles plugin, however the screen just keeps loading.
I think there is some ambiguity on whether to use .com or .org - however .com is not reachable and is producing 500 status code when i check the logs in jellyfin
I cannot reproduce the issue, login works fine for me
There's a chance opensubtitles had an outage, can you check if the issue is still happening and maybe post the error logs?
To log in you need to use .com credentials, also, what is the version of the plugin you are using?
I have similar issue, I accidentally opened the issue in the main repo : jellyfin/jellyfin#10064
I have attached the details and log in there.
I checked wget is working for both www.opensubtitles.org and www.opensubtitles.com from my container/device.
I'm also having the same problem. Here is a stack trace:
[2023-08-13 21:06:18.191 +00:00] [ERR] [15] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request. URL "POST" "/Jellyfin.Plugin.OpenSubtitles/ValidateLoginInfo".
System.InvalidOperationException: The AuthorizationPolicy named: 'DefaultAuthorization' was not found.
at Microsoft.AspNetCore.Authorization.AuthorizationPolicy.CombineAsync(IAuthorizationPolicyProvider policyProvider, IEnumerable`1 authorizeData, IEnumerable`1 policies)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Jellyfin.Api.Middleware.QueryStringDecodingMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.ReDoc.ReDocMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Jellyfin.Api.Middleware.RobotsRedirectionMiddleware.Invoke(HttpContext httpContext)
at Jellyfin.Api.Middleware.LegacyEmbyRouteRewriteMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context)
at Jellyfin.Api.Middleware.ResponseTimeMiddleware.Invoke(HttpContext context, IServerConfigurationManager serverConfigurationManager)
at Jellyfin.Api.Middleware.ExceptionMiddleware.Invoke(HttpContext context)
This is the commit that affected it:
jellyfin/jellyfin@209edd3
This is the line in the plugin that is squawking about it:
I am using version 10.8.z currently and it probably works fine on older versions.
Correction: Apparently I was using an unstable build beyond 10.8.10. There are authorization changes coming in 10.9 that will require updates from the plugin (including the one I listed above)
@MBR-0001 - Please check the details provided by @kikmak42 - I am facing the same issue.
Could you try this? jellyfin/jellyfin#10064 (comment)
The current theory is that opensubtitles may be blocked in India (and some other countries?)
I got this error:
[23:19:14] [ERR] [56] Jellyfin.Plugin.OpenSubtitles.OpenSubtitleDownloader: Invalid response: ServiceUnavailable -
Error 503 Backend fetch failed
Backend fetch failed
Guru Meditation:
XID: 1880097160
Varnish cache server
That's an error caused by an outage at opensubtitles, can't really do much about it
Open subtitles Stopped working for me not sure why. Getting the spinning load if I try to readd my credentials
Open subtitles Stopped working for me not sure why. Getting the spinning load if I try to readd my credentials
Please add server logs.
I got this error: [23:19:14] [ERR] [56] Jellyfin.Plugin.OpenSubtitles.OpenSubtitleDownloader: Invalid response: ServiceUnavailable -
<title>503 Backend fetch failed</title> # Error 503 Backend fetch failed Backend fetch failedGuru Meditation:
XID: 1880097160
Varnish cache server
Getting the same issue here. Does it work for you now?
GURU mediation, error 503 is error on our side, when servers are overloaded. We have hard time to scale this, everything cost money, we are running mostly free service, so our uptime is not 100%
Response on this is: try again later it is server error.