New Emby Server Release: 4.9.5.0

[elfco 1]

Same isue here, tmdb not fetching any data.

System.Runtime.Serialization.SerializationException: System.Runtime.Serialization.SerializationException: Type definitions should start with a '{', expecting serialized type 'CompleteMovieData', got string starting with: ��}Ko�J��_a�u/������ۖ��eK��.A2(���|H�

at ServiceStack.Text.Common.DeserializeTypeRefJson.StringToType(ReadOnlySpan`1 strType, TypeConfig typeConfig, EmptyCtorDelegate ctorFn, KeyValuePair`2[] typeAccessors) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack.Text/src/ServiceStack.Text/Common/DeserializeTypeRefJson.cs:line 28

at ServiceStack.Text.JsonSerializer.DeserializeFromSpan(Type type, ReadOnlySpan`1 value) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack.Text/src/ServiceStack.Text/JsonSerializer.cs:line 61

at ServiceStack.Text.NetCoreMemory.Deserialize(MemoryStream memoryStream, Boolean fromPool, Type type, DeserializeStringSpanDelegate deserializer) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack.Text/src/ServiceStack.Text/NetCoreMemory.cs:line 184

at ServiceStack.Text.NetCoreMemory.DeserializeAsync(Stream stream, Type type, DeserializeStringSpanDelegate deserializer) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack.Text/src/ServiceStack.Text/NetCoreMemory.cs:line 173

at ServiceStack.Text.JsonSerializer.DeserializeFromStreamAsync[T](Stream stream) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack.Text/src/ServiceStack.Text/JsonSerializer.cs:line 238

at Emby.Common.Implementations.Serialization.JsonSerializer.DeserializeFromStreamAsync[T](Stream stream)

at MovieDb.MovieDbProvider.FetchMainResult(String id, Boolean isTmdbId, String language, CancellationToken cancellationToken)

at MovieDb.MovieDbImageProvider.GetMovieInfo(BaseItem item, String language, IJsonSerializer jsonSerializer, CancellationToken cancellationToken)

at MovieDb.MovieDbImageProvider.GetImages(RemoteImageFetchOptions options, CancellationToken cancellationToken)

at Emby.Providers.Manager.ProviderManager.GetImages(RemoteImageFetchOptions options, CancellationToken cancellationToken, IRemoteImageProvider provider, Int32 providerIndex)

[tenchiowo 7]

Also can confirm after upgrading to Windows Server 4.9.5.0 I cannot Identify any new Movie or TV Show. I tried through IMDB and TMDB with correct paths that should have easily identified the Movie and or Television Show. 

[Vidmo232 8]

Just for fun, I rolled back to 4.9.3.0 and still see the same TMDB issue. I think their API key is no longer valid. If you take the exact GET URL and test it in your browser, you'll get a "Invalid API key" as a response.

https://api.themoviedb.org/3/person/886?api_key=‌f6bd687ffa63cd282b6ff2c6877f2669‌&append_to_response=credits,images,external_ids&language=en-US

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

 

Edited 22 hours ago by Vidmo232

[Vidmo232 8]

Looks like the root cause was/is at TMDB itself.
API returning corrupted data instead of JSON - Talk — The Movie Database (TMDB)

[kandiman 15]

Scanned Movies library everything is fine now definitely the issue was on TMDB side.

[pdufho 0]

18 hours ago, Luke said:

Hi, try shutting the server and then installing the update from the website.

Tried that, I would then get the error that it doesn't have access to the system.old directory, this folder is set read-only. The installation then fails.

Installation works fine after deleting this folder.

Had to do this for the previous version as well.

[AHrubik 2]

After updating my Emby Premier key is not registering and I get a spinning wheel on the admin page trying to save it. I've restarted and reinstalled. Blanked it out, shutdown and resaved it. All results in the spinning wheel and the "get emby premier" button at the top of the page. 

Edit: This seems to be resolved after I cleared the mb3 domain through noscript. This is something I have not had to do before so I'm not sure what's changed in the code. 

Edited 12 hours ago by AHrubik
Resolved.

[Suliamu 45]

4 hours ago, AHrubik said:

Edit: This seems to be resolved after I cleared the mb3 domain through noscript. This is something I have not had to do before so I'm not sure what's changed in the code. 

Same here. 
And i haven't even updated. 
Still on 4.9.1.90.