Jump to content

Emby Server Memory usage / leak in debian 11 / proxmox 7


warrentc3
 Share

Recommended Posts

warrentc3

About twice a week, memory will step into a hole.    It is the embyserver process that is consuming all the memory.  Nothing in syslog other than hourly cron entries.

The service becomes non-responsive.  Killing the process & restarting the service... or rebooting the LXC resolves. 

Anyone seen anything like this?  It didn't happen before moving to Emby 4.6.

image.png.ed292c3cbc37847cb98c62aabad9b643.png

 

image.png.cad665ec94e07efaf55195efa62c501d.png

Link to comment
Share on other sites

Hi, please try removing these plugins:

2021-11-25 16:18:30.211 Info App: Loading MovieThemeSongs, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/moviethemesongs.dll
2021-11-25 16:18:30.211 Info App: Loading DiskSpace, Version=1.0.5.6, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/DiskSpace.dll
2021-11-25 16:18:30.211 Info App: Loading statistics, Version=2.0.20.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Statistics.dll
2021-11-25 16:18:30.211 Info App: Loading MovieThemeVideos, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MovieThemeVideos.dll
2021-11-25 16:18:30.211 Info App: Loading Emby.AutoOrganize, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.AutoOrganize.dll
2021-11-25 16:18:30.211 Info App: Loading ThemeVideos, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/ThemeVideos.dll
2021-11-25 16:18:30.211 Info App: Loading VirtualTV, Version=0.9.9.5, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/VirtualTV.dll
2021-11-25 16:18:30.211 Info App: Loading playback_reporting, Version=1.9.0.5, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/playback_reporting.dll
2021-11-25 16:18:30.211 Info App: Loading Emby.DiagnosticsPlugin, Version=4.7.0.2, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.DiagnosticsPlugin.dll
2021-11-25 16:18:30.211 Info App: Loading CoverArt, Version=4.1.16.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/CoverArt.dll
2021-11-25 16:18:30.211 Info App: Loading ThemeSongs, Version=1.6.6.7, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/themesongs.dll
2021-11-25 16:18:30.211 Info App: Loading MediaBrowser.Plugins.ProwlNotifications, Version=3.1.3.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MediaBrowser.Plugins.ProwlNotifications.dll
2021-11-25 16:18:30.211 Info App: Loading XmlMetadata, Version=3.4.6.0, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/XmlMetadata.dll

Then restarting the server and seeing how that compares. Thanks.

Link to comment
Share on other sites

1 minute ago, warrentc3 said:

I removed a handful of those plugins.... not sure what the cause was.

Are you all set now?

Link to comment
Share on other sites

warrentc3
Just now, Luke said:

Are you all set now?

appear so... will fold some of those plugins back in later this month and see if one of them trips up.

 

Thanks, Luke.

Link to comment
Share on other sites

warrentc3

image.png.ff28c5f5c9793fb1998b202f576868a8.png

 

Syslog

Dec  7 00:00:04 emby2 systemd[1]: Starting Rotate log files...
Dec  7 00:00:04 emby2 systemd[1]: Starting Daily man-db regeneration...
Dec  7 00:00:04 emby2 systemd[1]: logrotate.service: Succeeded. 
Dec  7 00:00:04 emby2 systemd[1]: Finished Rotate log files.
Dec  7 00:00:04 emby2 systemd[1]: man-db.service: Succeeded.
Dec  7 00:00:04 emby2 systemd[1]: Finished Daily man-db regeneration.
Dec  7 00:24:01 emby2 CRON[243561]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 01:24:01 emby2 CRON[244135]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 02:24:01 emby2 CRON[249223]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 03:23:01 emby2 CRON[249562]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Dec  7 03:24:01 emby2 CRON[249570]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 04:24:01 emby2 CRON[250392]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 05:24:01 emby2 CRON[250841]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 06:02:01 emby2 CRON[251111]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Dec  7 06:24:01 emby2 CRON[251275]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 06:41:46 emby2 systemd[1]: Starting Daily apt upgrade and clean activities...
Dec  7 06:41:47 emby2 systemd[1]: apt-daily-upgrade.service: Succeeded.
Dec  7 06:41:47 emby2 systemd[1]: Finished Daily apt upgrade and clean activities.
Dec  7 07:24:01 emby2 CRON[251746]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 07:35:20 emby2 kernel: [853672.954853] Call Trace:
Dec  7 07:35:20 emby2 kernel: [853672.954880]  oom_kill_process.cold+0xb/0x10
Dec  7 07:35:20 emby2 kernel: [853672.954903]  try_charge+0x6f6/0x750
Dec  7 07:35:20 emby2 kernel: [853672.954922]  mem_cgroup_charge+0x36/0xa0
Dec  7 07:35:20 emby2 kernel: [853672.954939]  do_user_addr_fault+0x1bb/0x660
Dec  7 07:35:20 emby2 kernel: [853672.954959]  ? asm_exc_page_fault+0x8/0x30
Dec  7 07:35:20 emby2 kernel: [853672.954972] Code: c8 48 8b c1 48 83 ea 10 c5 fa 6f 0c 47 c5 fa 6f 54 47 10 c5 f1 eb da c4 e2 79 17 d8 0f 94 c1 0f b6 c9 85 c9 74 14 c5 f1 67 d2 <c5> f9 7f 14 06 48 83 c0 10 48 3b c2 76 d0 5d c3 c4 e2 79 17 c8 40
Dec  7 07:35:20 emby2 kernel: [853672.954982] RDX: 0000000000137df3 RSI: 00007f8cbe658ff8 RDI: 00007f8cbe3e93b4
Dec  7 07:35:20 emby2 kernel: [853672.954987] R13: 0065004d0022007b R14: 00007f8cbe3e93b4 R15: 0000000000137e03
Dec  7 07:35:20 emby2 kernel: [853672.955020] kmem: usage 227188kB, limit 9007199254740988kB, failcnt 0
Dec  7 07:35:22 emby2 kernel: [853675.522642] oom_reaper: reaped process 4047501 (EmbyServer), now anon-rss:0kB, file-rss:4kB, shmem-rss:2136kB
Dec  7 07:35:23 emby2 systemd[1]: emby-server.service: Main process exited, code=killed, status=9/KILL
Dec  7 07:35:23 emby2 systemd[1]: emby-server.service: Failed with result 'signal'.
Dec  7 08:20:11 emby2 kernel: [856363.785443] vmbr0: port 4(tap107i0) entered forwarding state
Dec  7 08:24:01 emby2 CRON[251860]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec  7 08:34:10 emby2 kernel: [857203.035693] fwbr106i0: port 2(veth106i0) entered disabled state
Dec  7 08:34:10 emby2 kernel: [857203.036062] fwbr106i0: port 2(veth106i0) entered disabled state
Dec  7 08:34:21 emby2 systemd[1]: Received SIGRTMIN+3.
Dec  7 08:34:21 emby2 systemd[1]: Removed slice system-modprobe.slice.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target Graphical Interface.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target Multi-User System.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target Login Prompts.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target Remote Encrypted Volumes.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target Timers.
Dec  7 08:34:21 emby2 systemd[1]: apt-daily-upgrade.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Daily apt upgrade and clean activities.
Dec  7 08:34:21 emby2 systemd[1]: apt-daily.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Daily apt download activities.
Dec  7 08:34:21 emby2 systemd[1]: e2scrub_all.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Dec  7 08:34:21 emby2 systemd[1]: logrotate.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Daily rotation of log files.
Dec  7 08:34:21 emby2 systemd[1]: man-db.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Daily man-db regeneration.
Dec  7 08:34:21 emby2 systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target System Time Synchronized.
Dec  7 08:34:21 emby2 systemd[1]: Stopped target System Time Set.
Dec  7 08:34:21 emby2 systemd[1]: Stopping Console Getty...
Dec  7 08:34:21 emby2 systemd[1]: Stopping Container Getty on /dev/tty1...
Dec  7 08:34:21 emby2 systemd[1]: Stopping Container Getty on /dev/tty2...
Dec  7 08:34:21 emby2 systemd[1]: Stopping Regular background program processing daemon...
Dec  7 08:34:21 emby2 systemd[1]: Stopping D-Bus System Message Bus...
Dec  7 08:34:21 emby2 systemd[1]: postfix.service: Succeeded.
Dec  7 08:34:21 emby2 systemd[1]: Stopped Postfix Mail Transport Agent.
Dec  7 08:34:21 emby2 systemd[1]: Stopping Postfix Mail Transport Agent (instance -)...
Dec  7 08:40:00 emby2 systemd[1]: Starting Flush Journal to Persistent Storage...
Dec  7 08:40:00 emby2 systemd[1]: Finished nftables.
Dec  7 08:40:00 emby2 systemd[1]: Finished Create Static Device Nodes in /dev.
Dec  7 08:40:00 emby2 systemd[1]: Reached target Local File Systems (Pre).
Dec  7 08:40:00 emby2 systemd[1]: Reached target Local File Systems.
Dec  7 08:40:00 emby2 systemd[1]: Reached target Network (Pre).
Dec  7 08:40:00 emby2 systemd[1]: Starting Raise network interfaces...
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Rule-based Manager for Device Events and Files being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Starting Network Service...
Dec  7 08:40:00 emby2 systemd[1]: Finished Flush Journal to Persistent Storage.
Dec  7 08:40:00 emby2 systemd[1]: Starting Create Volatile Files and Directories...
Dec  7 08:40:00 emby2 systemd-networkd[68]: Enumeration completed
Dec  7 08:40:00 emby2 systemd[1]: Started Network Service.
Dec  7 08:40:00 emby2 systemd-networkd[68]: eth0: Lost carrier
Dec  7 08:40:00 emby2 systemd-networkd[68]: eth0: Gained carrier
Dec  7 08:40:00 emby2 systemd[1]: Starting Wait for Network to be Configured...
Dec  7 08:40:00 emby2 systemd[1]: Finished Create Volatile Files and Directories.
Dec  7 08:40:00 emby2 systemd[1]: Starting Network Name Resolution...
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Reached target System Time Set.
Dec  7 08:40:00 emby2 systemd[1]: Reached target System Time Synchronized.
Dec  7 08:40:00 emby2 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Dec  7 08:40:00 emby2 systemd[1]: Finished Wait for Network to be Configured.
Dec  7 08:40:00 emby2 systemd[1]: Finished Update UTMP about System Boot/Shutdown.
Dec  7 08:40:00 emby2 systemd[1]: Reached target System Initialization.
Dec  7 08:40:00 emby2 systemd[1]: Started Daily apt download activities.
Dec  7 08:40:00 emby2 systemd[1]: Started Daily apt upgrade and clean activities.
Dec  7 08:40:00 emby2 systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Discard unused blocks once a week being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Started Daily rotation of log files.
Dec  7 08:40:00 emby2 systemd[1]: Started Daily man-db regeneration.
Dec  7 08:40:00 emby2 systemd[1]: Started Daily Cleanup of Temporary Directories.
Dec  7 08:40:00 emby2 systemd[1]: Reached target Timers.
Dec  7 08:40:00 emby2 systemd[1]: Listening on D-Bus System Message Bus Socket.
Dec  7 08:40:00 emby2 systemd[1]: Listening on OpenBSD Secure Shell server socket.
Dec  7 08:40:00 emby2 systemd[1]: Reached target Sockets.
Dec  7 08:40:00 emby2 systemd[1]: Reached target Basic System.
Dec  7 08:40:00 emby2 systemd[1]: Started Regular background program processing daemon.
Dec  7 08:40:00 emby2 systemd[1]: Started D-Bus System Message Bus.
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in Remove Stale Online ext4 Metadata Check Snapshots being skipped.
Dec  7 08:40:00 emby2 systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Dec  7 08:40:00 emby2 cron[172]: (CRON) INFO (pidfile fd = 3)
Dec  7 08:40:00 emby2 systemd[1]: Starting System Logging Service...
Dec  7 08:40:00 emby2 systemd[1]: Starting User Login Management...
Dec  7 08:40:00 emby2 cron[172]: (CRON) INFO (Running @reboot jobs)
Dec  7 08:40:00 emby2 systemd[1]: Finished Raise network interfaces.
Dec  7 08:40:00 emby2 rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.2102.0]
Dec  7 08:40:00 emby2 rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="175" x-info="https://www.rsyslog.com"] start
Dec  7 08:40:00 emby2 systemd[1]: Started System Logging Service.
Dec  7 08:40:01 emby2 systemd[1]: Started User Login Management.

embyserver-63774463201.zip

Link to comment
Share on other sites

Hi, please try removing these plugins:

	CoverArt 4.1.16.0
	Playback Reporting 1.9.0.5
	Prowl Notifications 3.1.3.0
	Theme Songs 1.6.6.7
	VirtualTV Plugin 0.1.1.0

Then restart the server and see how that compares. Thanks.

Link to comment
Share on other sites

Q-Droid

What kind of filesystem is /opt/transcode/transcoding-temp?

You seem to have an Apple device (Emby-Client=tvOS&X-Emby-Device-Name=Apple TV) constantly streaming a Live TV channel, for the entire duration of your Emby server log.

Link to comment
Share on other sites

warrentc3
50 minutes ago, Q-Droid said:

What kind of filesystem is /opt/transcode/transcoding-temp?

You seem to have an Apple device (Emby-Client=tvOS&X-Emby-Device-Name=Apple TV) constantly streaming a Live TV channel, for the entire duration of your Emby server log.

image.png.a7c9b1c6271314bff68a4d413b719b1f.png

Link to comment
Share on other sites

warrentc3
3 hours ago, Luke said:

Hi, please try removing these plugins:

	CoverArt 4.1.16.0
	Playback Reporting 1.9.0.5
	Prowl Notifications 3.1.3.0
	Theme Songs 1.6.6.7
	VirtualTV Plugin 0.1.1.0

Then restart the server and see how that compares. Thanks.

I don't believe this will help.  I've had all these plugins for some time.

Link to comment
Share on other sites

2 minutes ago, warrentc3 said:

I don't believe this will help.  I've had all these plugins for some time.

Can you try it?

Link to comment
Share on other sites

warrentc3

Well I typed up a dissertation of the log file attached here... but then i hit submit and it all went disappeared.embyserver.zip

I think @Q-Droid is on to something w/ Apple clients.

Pretty much....  it appears the issue occurs as part of a playback activity.

20:25 - System.Net.WebSockets.WebSocketException: System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.

then followed by about 20,000 lines of System.NullReferenceException: System.NullReferenceException: Object reference not set to an instance of an object.

 

21:15ish - my parents started playing a movie on their appletv

21:45ish - their activity of playing a movie magically appears in the server dashboard, but not anywhere on the activity log.

 

There also appears to be a peculiar amount of HTTP 500 errors.

 

It also looks like special chars are not URL encoded for device names.  Probably unrelated.  Unsure if by design and/or benign. 

 

Have also removed the following since those are plugins that center around playback activity.
   Playback Reporting 1.9.0.5
   Prowl Notifications 3.1.3.0

Edited by warrentc3
Link to comment
Share on other sites

Q-Droid
10 hours ago, warrentc3 said:

image.png.a7c9b1c6271314bff68a4d413b719b1f.png

Ok. I asked about the transcode path because some people like to get cute and use ramfs/tmpfs for things like transcoding or DB then wonder what happened when they run out and it crashes.

From your syslog it looks like a legit OOM kill of the Emby server. That's a serious jump in RAM usage but I couldn't spot anything else in the log.

 

Link to comment
Share on other sites

I've been noticing something similar for a while but haven't bothered to troubleshoot it since it's nowhere near this frequency.

I'd say every 4-6 weeks or so I'll wake up one morning and can't connect to my emby instance from my android-tv app. I'll hop on proxmox and the LXC container has the ram pegged and the swap pegged. Reboot the container and all is good for another 4-6 weeks. I haven't dug into it since I've got every single one of my media related services running in that 1 LXC so it's a lot of work to troubleshoot for something that's a very minor inconvenience with the frequency it's happening.

Link to comment
Share on other sites

I realize that this isn't going to be helpful since I don't have complete diagnostics, but I too have been experiencing this issue. I will attempt to gather as much data as possible after the holidays.

Sometime after the 4.6.1+ release I noticed very poor performance and frequent unresponsiveness of the emby server.  This issue seems to only happen when recording live tv but that might be coincidental. Symptoms include:

1) If streaming, the client will suffer from buffering issues and/or the stream will stop entirely.

2) If I close and attempt to re-open the app on the client the app will fail to find the server.

3) The server dashboard will be almost entirely unresponsive, taking several minutes to load if at all.

3) The now recording section of the dashboard or homepage will only show 1 active recording even if multiple recordings are taking place.  My HDHomeRun will show multiple tuners in use and the recordings eventually show up in the recording folder, often corrupted.

I've been kind of all over the place trying to figure this out, all of my variables have changed making this cumbersome. For example, my roku finally died and I replace it with an Nvidia Shield, my router crapped out and I had to replace that, and then I replaced my hdhomerun quatro for the new 4k flex.  I had been investigating this as a possible hard drive failure when I casually checked htop and found that my 2gig swap was entirely eaten up and very high ram usage by emby.  Normally emby would have a handful of threads in htop but at that time emby had dozens of long running processes.  Restarting the emby service instantly freed up all swap and ram.

I was running 4.6.7.0 and upgraded to 4.7.0.18, issue persisted.  Upgraded to 4.7.0.19 issue persists, but also introduced bugs with the continue watching section showing items that have already been watched and other things.  Finally rolled back to 4.6.0.50 and things seem to be normal again.  That problem on the 4.6.1+ code was very frequent for me, happening numerous times per day every day.

My system is running Debian 11 headless, base system+emby+pihole and that's it. 

/edit/ Just noticed that I went months on 4.6.4.0 and then moved to 4.6.6.0.  so this should narrow things down to changes implemented in 4.6.6 or 4.6.7.

-rw-r--r-- 1 root root 135M Jul  1 11:58 emby-server-deb_4.6.4.0_amd64.deb
-rw-r--r-- 1 root root 135M Nov 17 14:29 emby-server-deb_4.6.6.0_amd64.deb

 

Edited by sagean
add additional details.
Link to comment
Share on other sites

warrentc3
On 12/16/2021 at 1:35 PM, sagean said:

I realize that this isn't going to be helpful since I don't have complete diagnostics, but I too have been experiencing this issue. I will attempt to gather as much data as possible after the holidays.

Sometime after the 4.6.1+ release I noticed very poor performance and frequent unresponsiveness of the emby server.  This issue seems to only happen when recording live tv but that might be coincidental. Symptoms include:

1) If streaming, the client will suffer from buffering issues and/or the stream will stop entirely.

2) If I close and attempt to re-open the app on the client the app will fail to find the server.

3) The server dashboard will be almost entirely unresponsive, taking several minutes to load if at all.

3) The now recording section of the dashboard or homepage will only show 1 active recording even if multiple recordings are taking place.  My HDHomeRun will show multiple tuners in use and the recordings eventually show up in the recording folder, often corrupted.

I've been kind of all over the place trying to figure this out, all of my variables have changed making this cumbersome. For example, my roku finally died and I replace it with an Nvidia Shield, my router crapped out and I had to replace that, and then I replaced my hdhomerun quatro for the new 4k flex.  I had been investigating this as a possible hard drive failure when I casually checked htop and found that my 2gig swap was entirely eaten up and very high ram usage by emby.  Normally emby would have a handful of threads in htop but at that time emby had dozens of long running processes.  Restarting the emby service instantly freed up all swap and ram.

I was running 4.6.7.0 and upgraded to 4.7.0.18, issue persisted.  Upgraded to 4.7.0.19 issue persists, but also introduced bugs with the continue watching section showing items that have already been watched and other things.  Finally rolled back to 4.6.0.50 and things seem to be normal again.  That problem on the 4.6.1+ code was very frequent for me, happening numerous times per day every day.

My system is running Debian 11 headless, base system+emby+pihole and that's it. 

/edit/ Just noticed that I went months on 4.6.4.0 and then moved to 4.6.6.0.  so this should narrow things down to changes implemented in 4.6.6 or 4.6.7.

-rw-r--r-- 1 root root 135M Jul  1 11:58 emby-server-deb_4.6.4.0_amd64.deb
-rw-r--r-- 1 root root 135M Nov 17 14:29 emby-server-deb_4.6.6.0_amd64.deb

 

 

I'm in a similar boat...  there appears to be correlation between this symptom and 4.6.x + LiveTV

Link to comment
Share on other sites

  • 2 weeks later...

Good evening and congratulations to all of you, if any of you are using Nginx as a reverse proxy, the same thing happened to me that the Emby service stopped or gave an error, I started to check carefully and eliminate the Nginx server and buff the server It is running without any problem, now it is much faster, and it has been a week without problems, this could be the solution to those who are experiencing the same thing as me.
Currently I have 651 users and simultaneously I have about 107 users online and the server has not presented any more problems since I did the ones I raised.

Edited by Mstinga
  • Thanks 1
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
 Share

×
×
  • Create New...