Jump to content

Problem with WAN HTTPS


pacoyoh

Recommended Posts

jscoys

Hum interesting thing. I had the same issue and we tried to debug without success with @@dcrdev 2-3 months ago.

 

Hum first question: is it working with Plex? Did you wait up to 8 hours with Plex to see if it became unresponsive?

 

Other thing, what is your router? Do you have the original firmware on it?

 

Following my issue 2-3 months ago, desperate, I replaced my firmware on my dlink-880l with dd wrt and it works like a charm now. I don’t know if it handle better some connections not closed on Emby side or other issues there, but it solved my issue.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

ElDitcho

here is the log

2018-04-19 09:20:07.043 Info Main: Application path: /opt/emby-server/system/EmbyServer.dll
2018-04-19 09:20:07.052 Info Main: Emby
    Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
    Operating system: Unix 4.4.0.119
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Processor count: 4
    Program data path: /var/lib/emby
    Application directory: /opt/emby-server/system
2018-04-19 09:20:07.230 Info App: Application version: 3.3.1.19
2018-04-19 09:20:07.231 Info App: Loading assemblies
2018-04-19 09:20:07.250 Info App: File /var/lib/emby/plugins/Emby.Server.CinemaMode.dll has version 1.0.0.0
2018-04-19 09:20:07.250 Info App: File /opt/emby-server/system/plugins/Emby.Server.CinemaMode.dll has version 1.0.0.0
2018-04-19 09:20:07.257 Info App: Loading MBBackup, Version=1.2.2.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MBBackup.dll
2018-04-19 09:20:07.257 Info App: Loading Emby.Server.CinemaMode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll
2018-04-19 09:20:07.257 Info App: Loading statistics, Version=2.0.4.2, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Statistics.dll
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Plugins.Anime, Version=1.2.6.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MediaBrowser.Plugins.Anime.dll
2018-04-19 09:20:07.257 Info App: Loading Emby.Kodi.SyncQueue, Version=2.0.2.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Kodi.SyncQueue.dll
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Api, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.WebDashboard, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Model, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Controller, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Photos, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Server.Implementations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Server.MediaEncoding, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Dlna, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.LocalMetadata, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading MediaBrowser.XbmcMetadata, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Server.Connect, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.257 Info App: Loading Emby.Server.Sync, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
2018-04-19 09:20:07.387 Info SqliteUserRepository: Sqlite version: 3.23.1
2018-04-19 09:20:07.387 Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1
2018-04-19 09:20:07.414 Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal
2018-04-19 09:20:07.417 Info SqliteUserRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.428 Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal
2018-04-19 09:20:07.428 Info AuthenticationRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.514 Info DeviceManager: Default journal_mode for /var/lib/emby/data/devices.db is wal
2018-04-19 09:20:07.514 Info DeviceManager: PRAGMA synchronous=1
2018-04-19 09:20:07.536 Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is wal
2018-04-19 09:20:07.537 Info ActivityRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.539 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is wal
2018-04-19 09:20:07.539 Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.542 Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is wal
2018-04-19 09:20:07.542 Info SqliteItemRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.553 Info SqliteNotificationsRepository: Default journal_mode for /var/lib/emby/data/notifications.db is wal
2018-04-19 09:20:07.553 Info SqliteNotificationsRepository: PRAGMA synchronous=1
2018-04-19 09:20:07.783 Info App: Emby.Kodi.SyncQueue IS NOW STARTING!!!
2018-04-19 09:20:07.784 Info App: Emby.Kodi.SyncQueue: Creating DB Repository...
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  SyncAPI Created and Listening at "/Emby.Kodi.SyncQueue/{UserID}/{LastUpdateDT}/GetItems?format=json" - {LastUpdateDT} must be a UTC DateTime formatted as yyyy-MM-ddTHH:mm:ssZ
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  SyncAPI Created and Listening at "/Emby.Kodi.SyncQueue/{UserID}/GetItems?LastUpdateDT={LastUpdateDT}&format=json" - {LastUpdateDT} must be a UTC DateTime formatted as yyyy-MM-ddTHH:mm:ssZ
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  The following parameters also exist to filter the results:
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  filter=movies,tvshows,music,musicvideos,boxsets
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  Results will be included by default and only filtered if added to the filter query...
2018-04-19 09:20:07.852 Info App: Emby.Kodi.SyncQueue:  the filter query must be lowercase in both the name and the items...
2018-04-19 09:20:07.926 Info HttpServer: Calling ServiceStack AppHost.Init
2018-04-19 09:20:08.664 Info ServerManager: Loading Http Server
2018-04-19 09:20:08.669 Info HttpServer: Adding HttpListener prefix http://+:8096/
2018-04-19 09:20:08.669 Info HttpServer: Adding HttpListener prefix https://+:8920/
2018-04-19 09:20:08.895 Info Skia: SkiaSharp version: 1.58.0.0
2018-04-19 09:20:08.901 Info App: Emby.Kodi.SyncQueue.Task: Retention Task Scheduled!
2018-04-19 09:20:08.930 Info TaskManager: Daily trigger for Configuration Backup set to fire at 20/04/2018 00:10:00, which is 889.85116294 minutes from now.
2018-04-19 09:20:08.931 Info TaskManager: Daily trigger for Calculate statistics for all users set to fire at 20/04/2018 00:00:00, which is 879.851142081667 minutes from now.
2018-04-19 09:20:08.932 Info TaskManager: Daily trigger for Remove Old Sync Data set to fire at 20/04/2018 00:01:00, which is 880.851132006667 minutes from now.
2018-04-19 09:20:08.935 Info TaskManager: Daily trigger for Chapter image extraction set to fire at 20/04/2018 02:00:00, which is 999.851079656667 minutes from now.
2018-04-19 09:20:08.953 Info TaskManager: Daily trigger for Rotate log file set to fire at 20/04/2018 00:00:00, which is 879.850775838333 minutes from now.
2018-04-19 09:20:08.958 Info MediaEncoder: FFMpeg: /opt/emby-server/bin/ffmpeg
2018-04-19 09:20:08.959 Info MediaEncoder: FFProbe: /opt/emby-server/bin/ffprobe
2018-04-19 09:20:08.959 Info MediaEncoder: Validating media encoder at /opt/emby-server/bin/ffmpeg
2018-04-19 09:20:08.961 Info MediaEncoder: Running /opt/emby-server/bin/ffmpeg -decoders
2018-04-19 09:20:08.998 Info MediaEncoder: Decoder available: mpeg2video
2018-04-19 09:20:09.003 Info MediaEncoder: Decoder available: h264_cuvid
2018-04-19 09:20:09.003 Info MediaEncoder: Decoder available: hevc_cuvid
2018-04-19 09:20:09.004 Info MediaEncoder: Decoder available: mpeg2_cuvid
2018-04-19 09:20:09.004 Info MediaEncoder: Decoder available: mpeg4_cuvid
2018-04-19 09:20:09.004 Info MediaEncoder: Decoder available: vc1_cuvid
2018-04-19 09:20:09.005 Info MediaEncoder: Decoder available: vp8_cuvid
2018-04-19 09:20:09.006 Info MediaEncoder: Decoder available: vp9_cuvid
2018-04-19 09:20:09.014 Info MediaEncoder: Decoder available: ac3
2018-04-19 09:20:09.014 Info MediaEncoder: Decoder available: aac
2018-04-19 09:20:09.015 Info MediaEncoder: Decoder available: mp3
2018-04-19 09:20:09.015 Info MediaEncoder: Decoder available: h264
2018-04-19 09:20:09.016 Info MediaEncoder: Decoder available: hevc
2018-04-19 09:20:09.025 Info MediaEncoder: Running /opt/emby-server/bin/ffmpeg -encoders
2018-04-19 09:20:09.057 Info MediaEncoder: Encoder available: libx264
2018-04-19 09:20:09.058 Info MediaEncoder: Encoder available: mpeg4
2018-04-19 09:20:09.058 Info MediaEncoder: Encoder available: msmpeg4
2018-04-19 09:20:09.059 Info MediaEncoder: Encoder available: aac
2018-04-19 09:20:09.059 Info MediaEncoder: Encoder available: libmp3lame
2018-04-19 09:20:09.060 Info MediaEncoder: Encoder available: libopus
2018-04-19 09:20:09.060 Info MediaEncoder: Encoder available: libvorbis
2018-04-19 09:20:09.061 Info MediaEncoder: Encoder available: srt
2018-04-19 09:20:09.061 Info MediaEncoder: Encoder available: h264_nvenc
2018-04-19 09:20:09.061 Info MediaEncoder: Encoder available: hevc_nvenc
2018-04-19 09:20:09.064 Info MediaEncoder: Encoder available: h264_vaapi
2018-04-19 09:20:09.064 Info MediaEncoder: Encoder available: hevc_vaapi
2018-04-19 09:20:09.065 Info MediaEncoder: Encoder available: h264_v4l2m2m
2018-04-19 09:20:09.065 Info MediaEncoder: Encoder available: libwebp
2018-04-19 09:20:09.065 Info MediaEncoder: Encoder available: ac3
2018-04-19 09:20:09.066 Info MediaEncoder: Encoder validation complete
2018-04-19 09:20:09.067 Info App: ServerId: b693d914c2614efeb63b3dabdc2b2793
2018-04-19 09:20:09.116 Info App: Starting entry point MediaBrowser.WebDashboard.ServerEntryPoint
2018-04-19 09:20:09.117 Info App: Entry point completed: MediaBrowser.WebDashboard.ServerEntryPoint. Duration: 0.0008154 seconds
2018-04-19 09:20:09.117 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint
2018-04-19 09:20:09.276 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.158647 seconds
2018-04-19 09:20:09.276 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint
2018-04-19 09:20:09.277 Info App: Loading data from /var/lib/emby/data/connect.txt
2018-04-19 09:20:09.282 Info App: Loading data from /var/lib/emby/data/wan.dat
2018-04-19 09:20:09.288 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0125413 seconds
2018-04-19 09:20:09.288 Info App: Core startup complete
2018-04-19 09:20:09.288 Info App: Post-init migrations complete
2018-04-19 09:20:09.288 Info App: Starting entry point Emby.Security.PluginSecurityManager
2018-04-19 09:20:09.288 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 4.04E-05 seconds
2018-04-19 09:20:09.288 Info App: Starting entry point MBBackup.ServerEntryPoint
2018-04-19 09:20:09.288 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 3.04E-05 seconds
2018-04-19 09:20:09.288 Info App: Starting entry point Emby.Security.PluginSecurityManager
2018-04-19 09:20:09.288 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 2.66E-05 seconds
2018-04-19 09:20:09.288 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint
2018-04-19 09:20:09.289 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.000334 seconds
2018-04-19 09:20:09.289 Info App: Starting entry point Emby.Kodi.SyncQueue.EntryPoints.LibrarySyncNotification
2018-04-19 09:20:09.291 Info App: Emby.Kodi.SyncQueue:  LibrarySyncNotification Startup...
2018-04-19 09:20:09.291 Info App: Entry point completed: Emby.Kodi.SyncQueue.EntryPoints.LibrarySyncNotification. Duration: 0.001814 seconds
2018-04-19 09:20:09.291 Info App: Starting entry point Emby.Kodi.SyncQueue.EntryPoints.UserSyncNotification
2018-04-19 09:20:09.291 Info App: Emby.Kodi.SyncQueue:  UserSyncNotification Startup...
2018-04-19 09:20:09.292 Info App: Entry point completed: Emby.Kodi.SyncQueue.EntryPoints.UserSyncNotification. Duration: 0.0009157 seconds
2018-04-19 09:20:09.292 Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint
2018-04-19 09:20:09.292 Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 5.57E-05 seconds
2018-04-19 09:20:09.292 Info App: Starting entry point Emby.Server.Implementations.Notifications.Notifications
2018-04-19 09:20:09.295 Info App: Entry point completed: Emby.Server.Implementations.Notifications.Notifications. Duration: 0.003462 seconds
2018-04-19 09:20:09.295 Info App: Starting entry point Emby.Server.Implementations.Notifications.WebSocketNotifier
2018-04-19 09:20:09.296 Info App: Entry point completed: Emby.Server.Implementations.Notifications.WebSocketNotifier. Duration: 0.0004791 seconds
2018-04-19 09:20:09.296 Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint
2018-04-19 09:20:09.296 Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0001975 seconds
2018-04-19 09:20:09.296 Info App: Starting entry point Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint
2018-04-19 09:20:09.298 Info App: Loading live tv data from /var/lib/emby/data/livetv/timers
2018-04-19 09:20:09.402 Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1 on 192.168.1.51
2018-04-19 09:20:09.461 Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1 on fe80::20c:29ff:fee8:886a%2
2018-04-19 09:20:09.540 Info App: Entry point completed: Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint. Duration: 0.2439831 seconds
2018-04-19 09:20:09.540 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
2018-04-19 09:20:09.566 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0265326 seconds
2018-04-19 09:20:09.567 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
2018-04-19 09:20:09.567 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0002866 seconds
2018-04-19 09:20:09.567 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ExternalPortForwarding
2018-04-19 09:20:09.579 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ExternalPortForwarding. Duration: 0.0125617 seconds
2018-04-19 09:20:09.579 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
2018-04-19 09:20:09.580 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0002005 seconds
2018-04-19 09:20:09.580 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
2018-04-19 09:20:09.581 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0009701 seconds
2018-04-19 09:20:09.581 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.RecordingNotifier
2018-04-19 09:20:09.582 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.RecordingNotifier. Duration: 0.0010707 seconds
2018-04-19 09:20:09.582 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
2018-04-19 09:20:09.583 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0016058 seconds
2018-04-19 09:20:09.583 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
2018-04-19 09:20:09.584 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0006257 seconds
2018-04-19 09:20:09.584 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
2018-04-19 09:20:09.584 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0002331 seconds
2018-04-19 09:20:09.584 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint
2018-04-19 09:20:09.588 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint. Duration: 0.0040935 seconds
2018-04-19 09:20:09.589 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UsageEntryPoint
2018-04-19 09:20:09.589 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UsageEntryPoint. Duration: 0.0005921 seconds
2018-04-19 09:20:09.589 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
2018-04-19 09:20:09.589 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0001155 seconds
2018-04-19 09:20:09.589 Info App: Starting entry point Emby.Server.Implementations.Devices.DeviceManagerEntryPoint
2018-04-19 09:20:09.590 Info App: Entry point completed: Emby.Server.Implementations.Devices.DeviceManagerEntryPoint. Duration: 0.0009074 seconds
2018-04-19 09:20:09.590 Info App: Starting entry point Emby.Server.Implementations.Collections.CollectionManagerEntryPoint
2018-04-19 09:20:09.592 Info App: Entry point completed: Emby.Server.Implementations.Collections.CollectionManagerEntryPoint. Duration: 0.0022274 seconds
2018-04-19 09:20:09.592 Info App: Starting entry point Emby.Server.Implementations.Activity.ActivityLogEntryPoint
2018-04-19 09:20:09.594 Info App: Entry point completed: Emby.Server.Implementations.Activity.ActivityLogEntryPoint. Duration: 0.001149 seconds
2018-04-19 09:20:09.594 Info App: Starting entry point Emby.Server.MediaEncoding.Api.ApiEntryPoint
2018-04-19 09:20:09.594 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.ApiEntryPoint. Duration: 0.0006185 seconds
2018-04-19 09:20:09.594 Info App: Starting entry point MediaBrowser.XbmcMetadata.EntryPoint
2018-04-19 09:20:09.594 Info App: Entry point completed: MediaBrowser.XbmcMetadata.EntryPoint. Duration: 0.000121 seconds
2018-04-19 09:20:09.594 Info App: Starting entry point Emby.Security.PluginSecurityManager
2018-04-19 09:20:09.595 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 4.38E-05 seconds
2018-04-19 09:20:09.595 Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
2018-04-19 09:20:09.604 Info App: Sqlite version: 3.23.1
2018-04-19 09:20:09.604 Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1
2018-04-19 09:20:09.604 Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
2018-04-19 09:20:09.605 Info App: PRAGMA synchronous=1
2018-04-19 09:20:09.607 Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.012815 seconds
2018-04-19 09:20:09.607 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
2018-04-19 09:20:09.608 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0003555 seconds
2018-04-19 09:20:09.608 Info App: All entry points have started
2018-04-19 09:20:09.923 Info LibraryMonitor: Watching directory /jarvis/video/AnimeMovies
2018-04-19 09:20:09.929 Info HttpClient: GET https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog
2018-04-19 09:20:10.129 Info LibraryMonitor: Watching directory /jarvis/video/TV Shows
2018-04-19 09:20:10.427 Info LibraryMonitor: Watching directory /jarvis/video/AnimeTv
2018-04-19 09:20:11.942 Info TaskManager: StartupTrigger fired for task: Check for plugin updates
2018-04-19 09:20:11.944 Info TaskManager: Queueing task PluginUpdateTask
2018-04-19 09:20:11.948 Info TaskManager: Executing Check for plugin updates
2018-04-19 09:20:11.952 Info TaskManager: StartupTrigger fired for task: Check for application updates
2018-04-19 09:20:11.952 Info TaskManager: Queueing task SystemUpdateTask
2018-04-19 09:20:11.952 Info TaskManager: Executing Check for application updates
2018-04-19 09:20:11.967 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json
2018-04-19 09:20:11.969 Info HttpClient: GET https://api.github.com/repos/MediaBrowser/Emby.Releases/releases
2018-04-19 09:20:12.325 Info LibraryMonitor: Watching directory /jarvis/video/Movies
2018-04-19 09:20:13.155 Info TaskManager: Check for application updates Completed after 0 minute(s) and 1 seconds
2018-04-19 09:20:13.171 Info TaskManager: ExecuteQueuedTasks
2018-04-19 09:20:13.210 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 1 seconds
2018-04-19 09:20:13.210 Info TaskManager: ExecuteQueuedTasks
2018-04-19 09:20:37.702 Info HttpServer: HTTP GET https://dummyurl:8920/. UserAgent: curl/7.47.0
2018-04-19 09:20:37.704 Info HttpServer: HTTP Response 302 to 127.0.0.1. Time: 3ms. https://dummyurl:8920/
2018-04-19 09:25:19.718 Error HttpServer: Error in ProcessAccept
    *** Error Report ***
    Version: 3.3.1.19
    Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
    Operating system: Unix 4.4.0.119
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Processor count: 4
    Program data path: /var/lib/emby
    Application directory: /opt/emby-server/system
    System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> Interop+OpenSsl+SslException: SSL Handshake failed with OpenSSL error - SSL_ERROR_SSL. ---> Interop+Crypto+OpenSslCryptographicException: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
       --- End of inner exception stack trace ---
       at Interop.OpenSsl.DoSslHandshake(SafeSslHandle context, Byte[] recvBuf, Int32 recvOffset, Int32 recvCount, Byte[]& sendBuf, Int32& sendCount)
       at System.Net.Security.SslStreamPal.HandshakeInternal(SafeFreeCredentials credential, SafeDeleteContext& context, SecurityBuffer inputBuffer, SecurityBuffer outputBuffer, Boolean isServer, Boolean remoteCertRequired)
       --- End of inner exception stack trace ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
       at System.Net.Security.SslStream.EndAuthenticateAsServer(IAsyncResult asyncResult)
       at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpConnection.<Init>d__30.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpEndPointListener.<ProcessAccept>d__29.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpEndPointListener.<ProcessAccept>d__27.MoveNext()
    System.Security.Authentication.AuthenticationException
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
       at System.Net.Security.SslStream.EndAuthenticateAsServer(IAsyncResult asyncResult)
       at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpConnection.<Init>d__30.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpEndPointListener.<ProcessAccept>d__29.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at SocketHttpListener.Net.HttpEndPointListener.<ProcessAccept>d__27.MoveNext()
    InnerException: Interop+OpenSsl+SslException
    Interop+OpenSsl+SslException: SSL Handshake failed with OpenSSL error - SSL_ERROR_SSL. ---> Interop+Crypto+OpenSslCryptographicException: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
       --- End of inner exception stack trace ---
       at Interop.OpenSsl.DoSslHandshake(SafeSslHandle context, Byte[] recvBuf, Int32 recvOffset, Int32 recvCount, Byte[]& sendBuf, Int32& sendCount)
       at System.Net.Security.SslStreamPal.HandshakeInternal(SafeFreeCredentials credential, SafeDeleteContext& context, SecurityBuffer inputBuffer, SecurityBuffer outputBuffer, Boolean isServer, Boolean remoteCertRequired)
       at Interop.OpenSsl.DoSslHandshake(SafeSslHandle context, Byte[] recvBuf, Int32 recvOffset, Int32 recvCount, Byte[]& sendBuf, Int32& sendCount)
       at System.Net.Security.SslStreamPal.HandshakeInternal(SafeFreeCredentials credential, SafeDeleteContext& context, SecurityBuffer inputBuffer, SecurityBuffer outputBuffer, Boolean isServer, Boolean remoteCertRequired)
    InnerException: Interop+Crypto+OpenSslCryptographicException
    Interop+Crypto+OpenSslCryptographicException: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
    

Hum interesting thing. I had the same issue and we tried to debug without success with @@dcrdev 2-3 months ago.

Hum first question: is it working with Plex? Did you wait up to 8 hours with Plex to see if it became unresponsive?

Other thing, what is your router? Do you have the original firmware on it?

Following my issue 2-3 months ago, desperate, I replaced my firmware on my dlink-880l with dd wrt and it works like a charm now. I don’t know if it handle better some connections not closed on Emby side or other issues there, but it solved my issue.


Sent from my iPhone using Tapatalk

 

For my part, there is no plex and using the router of my provider.

Link to comment
Share on other sites

jscoys

Ok forget my message, I’m having the same issue with 3.3.1.19... let’s @@Luke checking.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

jscoys

Can we have a status on it? Every time I wanna watch something I have to restart my Emby-Server service...

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Can we have a status on it? Every time I wanna watch something I have to restart my Emby-Server service...

 

 

Sent from my iPhone using Tapatalk

 

Have you provided the information requested in how to report a problem? Thanks.

Link to comment
Share on other sites

jscoys

Little word to say I don’t have the issue with the .20 so I guess it’s fixed.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Just passed on the .21 and it's worse  ^^ i have some "Error processing request" but does not seems related.

 

https://pastebin.com/7fHqELUj

 

Hi, please keep beta discussion in the Testing Area section of the community. However, just to address this - there are no problems in this log.

Link to comment
Share on other sites

ElDitcho

Hi, please keep beta discussion in the Testing Area section of the community. However, just to address this - there are no problems in this log.

 

ok thx

Link to comment
Share on other sites

jscoys

Do you have the link for the entry in Beta section? Personally I still have the issue

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

  • 2 weeks later...
jscoys

Sooooo on Yesterday it wasn’t working well, today it is. Accessed from https through browsers is working well with .28 today, so we can close the point. Something I notice is that through https I have sometimes issues but not through native apps on devices like iOS app or android app... I guess you use different technology to connect from them?

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

jscoys

I don’t know why but I’m so desperate of the web access to my Emby server... it’s not loading correctly from safari on iOS, I have to refresh the page several times... but on the native iOS app it’s working nicely...

 

Luke how do you handle differently the access from web browsers compared to native apps?

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Well the web app has to download both the web app files as well as your emby data. I've seen this with older versions of ios, for instance i have a tablet still on ios9 which i use for old device testing. Sometimes on initial load of the web app i have to refresh the page a couple times. I do not see this with ios 10 and above.

Link to comment
Share on other sites

neik

I think I am having the same problem as described in post #1 with 3.4.0.0.

 

After a random amount of time I can't access Emby anymore using https. It does not matter how I try to access it (WebUI, Emby for Kodi, Emby for Android) always the same result.

 

Interesting enough Emby doesn't even write anything into the logfile it looks like it is freezed and doesn't respond to queries.

 

Gonna update to latest stable but anyways I would appreciate any hint.

Link to comment
Share on other sites

I think I am having the same problem as described in post #1 with 3.4.0.0.

 

After a random amount of time I can't access Emby anymore using https. It does not matter how I try to access it (WebUI, Emby for Kodi, Emby for Android) always the same result.

 

Interesting enough Emby doesn't even write anything into the logfile it looks like it is freezed and doesn't respond to queries.

 

Gonna update to latest stable but anyways I would appreciate any hint.

 

We already have a topic where we are trying to help you. Right now you are posting the same thing in multiple places and that's actually going to make it harder for us to help you.

Link to comment
Share on other sites

torinn

I'm still seeing this behavior on 3.4.1.0 stable. Many tcp connections in the CLOSE_WAIT state with an internal host chatting over HTTPS (specifically a Samsung TV running the Emby app). Bouncing the service sorts the issue out for a spell, and then we're right back to it. Here's the "How to report a problem" bits as best I can provide them:

 

- First version where this issue was observed: Emby Server 3.3.1.0

- Tried on various beta builds from 3.3.1.*, as well at 3.4.0.0

- Current version: Emby Server 3.4.1.0

- OS: Debian 9.4

- Clients and network location, in order of frequency: Internal web browser, internal Samsung app, external android app, external Chrome browser

- Applications accessing the server over the API: Ombi (request portal)

- HTTPS Certificate provider: Letsencrypt

- HTTPS port: 8920 (default)

- Last restart: 01:22 AM UTC 2018-05-12

- Description of behavior: "At some time after starting the emby-server service internal and external HTTPS traffic hangs. After this time HTTP access remains operational (though practically this downs the application as I only use HTTP for diagnostic testing for security reasons). I observe many CLOSE_WAIT connections in the output of netstat when this behavior presents itself. Restarting the emby-server service temporarily resolves this behavior."

 

Server Logs in full are somewhat burdensome to share (220k lines when HTTPS goes down on 2018-05-12 and another 198k lines from today, 68M of data across the two files). Trimming around the last few instances of <DNS-record>:<HTTPS port> occurs:

#First (and only) cluster of errors in the logs before HTTPS fails

2018-05-12 00:00:05.393 Error FileSystem: Error determining LastAccessTimeUtc for /mnt/nas/media/TV/House/Season 1/House 01x18 - Babies & Bathwater.avi
	*** Error Report ***
	Version: 3.4.1.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Unix 4.9.0.3
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 8
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	System.ArgumentOutOfRangeException: Valid values are between -62135596800 and 253402300799, inclusive.
	Parameter name: seconds
	   at System.DateTimeOffset.FromUnixTimeSeconds(Int64 seconds)
	   at System.IO.FileSystemInfo.System.IO.IFileSystemObject.get_LastWriteTime()
	   at System.IO.FileSystemInfo.get_LastWriteTimeUtc()
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetLastWriteTimeUtc(FileSystemInfo info)
	System.ArgumentOutOfRangeException
	   at System.DateTimeOffset.FromUnixTimeSeconds(Int64 seconds)
	   at System.IO.FileSystemInfo.System.IO.IFileSystemObject.get_LastWriteTime()
	   at System.IO.FileSystemInfo.get_LastWriteTimeUtc()
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetLastWriteTimeUtc(FileSystemInfo info)

#Last hit for "https://emby.torinn.xyz:8920" in logs

2018-05-12 06:57:50.125 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:00.125 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:00.126 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:10.126 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:10.127 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:20.125 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:20.126 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:30.125 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:30.126 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:40.126 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:40.126 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:58:50.125 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:58:50.126 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:59:00.126 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:59:00.127 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:59:10.126 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:59:10.127 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 06:59:20.128 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:59:20.129 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
2018-05-12 07:05:01.736 Info HttpServer: HTTP GET http://emby.torinn.xyz:8096/emby/users/89719bdb5d1245e0b30c1da111c03322/items?Recursive=True&IncludeItemTypes=Movie. UserAgent: Ombi
2018-05-12 07:05:01.760 Info HttpServer: HTTP Response 200 to 10.0.0.20. Time: 25ms. http://emby.torinn.xyz:8096/emby/users/89719bdb5d1245e0b30c1da111c03322/items?Recursive=True&IncludeItemTypes=Movie 
2018-05-12 07:05:01.764 Info HttpServer: HTTP GET http://emby.torinn.xyz:8096/emby/users/89719bdb5d1245e0b30c1da111c03322/items/01422d2977b063a1d4d75ed7853d8ee5. UserAgent: Ombi


#First errors after HTTPS traffic stops
2018-05-12 09:25:00.423 Error FileSystem: Error determining LastAccessTimeUtc for /mnt/nas/media/TV/House/Season 2/House - 02x02 - Autopsy.avi
	*** Error Report ***
	Version: 3.4.1.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Unix 4.9.0.3
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 8
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	System.ArgumentOutOfRangeException: Valid values are between -62135596800 and 253402300799, inclusive.
	Parameter name: seconds
	   at System.DateTimeOffset.FromUnixTimeSeconds(Int64 seconds)
	   at System.IO.FileSystemInfo.System.IO.IFileSystemObject.get_LastWriteTime()
	   at System.IO.FileSystemInfo.get_LastWriteTimeUtc()
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetLastWriteTimeUtc(FileSystemInfo info)
	System.ArgumentOutOfRangeException
	   at System.DateTimeOffset.FromUnixTimeSeconds(Int64 seconds)
	   at System.IO.FileSystemInfo.System.IO.IFileSystemObject.get_LastWriteTime()
	   at System.IO.FileSystemInfo.get_LastWriteTimeUtc()
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetLastWriteTimeUtc(FileSystemInfo info)

#No other errors throughout the logs that don't match "Error determining LastAccessTimeUtc"

As the errors mention System.IO and Filesystem I figure it's also worth mentioning these files are shared via a CIFS mount configured in /etc/fstab.

 

Log times are in EST, so the gap roughly maps to 12:00:00 UTC (10h 38m after service restart).

Edited by torinn
  • Like 1
Link to comment
Share on other sites

Hi there, can you please attach the complete emby server log? Thanks !

Link to comment
Share on other sites

I don't see any incoming https traffic in this log. Have you even configured https connectivity in Emby?

Link to comment
Share on other sites

torinn

An example HTTP POST transaction to emby.torinn.xyz:8920 over the HTTPS protocol:

2018-05-12 06:59:20.128 Info HttpServer: HTTP POST https://emby.torinn.xyz:8920/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-12 06:59:20.129 Info HttpServer: HTTP Response 204 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/Sessions/Playing/Progress 
 

The response sent to the client (10.0.0.50) was a 204. I just generated these transactions (I've restarted the service as I wanted to watch something):

2018-05-13 19:08:50.951 Info HttpServer: HTTP GET https://emby.torinn.xyz:8920/web/strings/en-US.json?v=1526252921483. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-13 19:08:50.953 Info HttpServer: HTTP Response 200 to 10.0.0.50. Time: 2ms. https://emby.torinn.xyz:8920/web/strings/en-US.json?v=1526252921483 
2018-05-13 19:08:50.954 Info HttpServer: HTTP GET https://emby.torinn.xyz:8920/web/bower_components/emby-webcomponents/strings/en-us.json?v=1526252921483. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-13 19:08:50.955 Info HttpServer: HTTP Response 200 to 10.0.0.50. Time: 1ms. https://emby.torinn.xyz:8920/web/bower_components/emby-webcomponents/strings/en-us.json?v=1526252921483 
2018-05-13 19:08:51.285 Info HttpServer: HTTP GET https://emby.torinn.xyz:8920/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
2018-05-13 19:08:51.285 Info HttpServer: HTTP Response 200 to 10.0.0.50. Time: 0ms. https://emby.torinn.xyz:8920/emby/system/info/public 

Looks like HTTPS to me

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...