jellyfin

As part of the deblobbing/removing calling home work on Jellyfin, there are a couple errors that are commonly generated and are not impacting. If you see these errors, you may safely ignore them. They will be cleaned up fully in a future release that removes the callhome entirely.

Error HttpClient: Error NameResolutionFailure

Errors like this are due to us changing the Emby callhome domain in the code, thus causing package downloads to fail.

2018-12-22 00:38:58.373 Info HttpClient: HttpClientManager GET: https://www.mb3admin.local/admin/service/EmbyPackages.json
2018-12-22 00:38:58.589 Error HttpClient: Error NameResolutionFailure getting response from https://www.mb3admin.local/admin/service/EmbyPackages.json
        *** Error Report ***
        Version: 3.5.2.0
        Command line: /usr/lib/jellyfin/bin/jellyfin.dll -programdata /var/lib/jellyfin -restartpath /usr/lib/jellyfin/restart.sh
        Operating system: Unix 4.9.0.8
        64-Bit OS: True
        64-Bit Process: True
        User Interactive: True
        Processor count: 6
        Program data path: /var/lib/jellyfin
        Application directory: /usr/lib/jellyfin/bin
        System.Net.WebException: No such device or address No such device or address ---> System.Net.Http.HttpRequestException: No such device or address ---> System.Net.Sockets.SocketException: No such device or address
           at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
           --- End of inner exception stack trace ---