#cant reconnect jellyfin

1 messages · Page 1 of 1 (latest)

fierce yarrow
#

my apikey needed changed so i disconnected and then when i went to redo the connecton i get this error

[22:58:29 ERR] Error getting jellyfin server name
Refit.ApiException: Response status code does not indicate success: 403 (Forbidden).
   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288
--- End of stack trace from previous location ---
   at LanguageExt.TaskExtensions.Map[T,U](Task`1 self, Func`2 map)
   at ErsatzTV.Infrastructure.Jellyfin.JellyfinApiClient.GetServerInformation(String address, String apiKey) in /source/ErsatzTV.Infrastructure/Jellyfin/JellyfinApiClient.cs:line 43```
fierce yarrow
#

still cant get it to connect again

edgy timber
#

Are you sure you have the new API key correct?

fierce yarrow
#

yes i am i just tryed with a second key same error

#
Refit.ApiException: Response status code does not indicate success: 403 (Forbidden).
   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288
--- End of stack trace from previous location ---
   at LanguageExt.TaskExtensions.Map[T,U](Task`1 self, Func`2 map)
   at ErsatzTV.Infrastructure.Jellyfin.JellyfinApiClient.GetServerInformation(String address, String apiKey) in /source/ErsatzTV.Infrastructure/Jellyfin/JellyfinApiClient.cs:line 43
[12:10:21 ERR] Error saving Jellyfin secrets: Response status code does not indicate success: 403 (Forbidden).
#

i am on the unstable build of jellyfin

fierce yarrow
#

i did a clean install of jellyfin now it works something about my api keys wasnt working

edgy timber
#

ok, glad you got it figured out

little shell
#

I'm having the same error after upgrading to the jellyfin 10.9 unstable branch.

@fierce yarrow did you get this to work with unstable or did you switch back to stable?

I just assumed the jf api might have changed and didn't want to bring this up here since it's not a stable release, yet

fierce yarrow
#

i ended up going back to stable