Jump to content

Search the Community

Showing results for tags 'Docker'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. I am changing my home Emby server from an Ubuntu based .deb package installation to a Docker setup. I did not realise that you could keep all the metadata, images and subtitles in each Movie or TV Show folder. Is it possible to wave a magic wand and copy all the current metadata, images and subtitles (gathered over the years!) to each of the Movie or TV Show folders when I install Emby using Docker? I guess this is Docker independant and it would be best to do this operation before the change to Docker? /var/lib/emby/metadata/ --> /srv/storage/Emby/Movies/Movie Name (YEAR)/Movie Name (YEAR).nfo etc I await your magic wand. Paully
  2. bendini20

    Transcoding Cache Flush Issue

    Hello all! I am using the docker for Emby media Server on unraid. The functionality of the docker is no different than a socker on any other linux distro. The docker I use: https://registry.hub.docker.com/r/emby/embyserver/ I have my Emby and Plex dockers use ram as a transcoding working directory to save SSD life. I have /tmp mapped to the docker and both Plex and Emby are able to utilize the ram. However, Emby does not purge this cache once playback (the transcoding job) is finished. Plex on the other hand does this perfectly. I frequently check on my server, and ram usage will be somewhat high. After inspecting the directories, Emby transcoding is always the culprit, and no playbacks are occurring on the Emby Server. The transcoding directory is full of: Once I delete all of this, ram usage goes back to normal. I have had to do this many times. I am not sure if it is a bug with Emby or a config issue. Any further assistance would be appreciated. Thanks.
  3. Hi, I have recently upgrade my HTPC with Emby Server to better allow transcoding. I had an older ubuntu server that both hosted both the media and emby server. Now I have an intel based windows PC with an SSD. I initially set this up directly on the PC and connected to the old ubuntu server and use it for all storage (including cache to avoid too many read/write actions and shortening the lifespan). Once I had setup SAMBA on the ubuntu server and signed in I had no issue. However, I decided to install Emby Docker container and run it through a VPN given that I use Emby away from home (with appropriate port forwarding). However, since doing this, any write requirements to the ubuntu server fails (both transcoding and cache) fail. I have tried to redo all the users:groups to make sure that they are all correct and it would seem to be the case. However, everytime I try to stream something that needs a buffer or transcoding the logs show that this fails with 'permission denied'. I have tried a number of things (see the unanswered post on https://stackoverflow.com/questions/71417345/configuring-user-permissions-in-docker-compose for a more extensive summary). Any thoughts? (I can post logs if helpful but there would seem only to be a 'permission denied' error when I see the action failed).
  4. Hi, I run the following command to start Emby docker container: docker run -d --name emby --volume /Emby/data/config:/config --volume /Emby/data/movie:/mnt/share1 --volume /Emby/data/show:/mnt/share2 --net=host --publish 8096:8096 --publish 8920:8920 --env UID=1000 --env GID=100 --env GIDLIST=100 emby/embyserver:4.6.4.0 When I use browser to access it prompts a panel to login with a default user of emby. I created local account named emby with UID 1000, but I still can't login with the password I set locally. Could you help how to login Emby? Thanks, Song
  5. jhowetan

    Emby not running through Portainer

    Hello, I'm trying to run Emby through Portainer but I am having issues. I've attached the container log and the content of the stack. Thanks in advance! emby_stack.txt _emby_logs.txt
  6. Emby client started a conversion process and I noticed it and stopped the process on the server-side. Now, the client's device tries polling the server on the conversion/sync progress and it appears to make Emby refuse all connections from that source (from my nginx proxy, so basically any connections through my duckdns.org domain) and results in a 502 error. My setup is: Router port forward ports 80, 443 --> nginx-proxy-manager hosted on docker on my Ubuntu (192.168.1.13), which routes to my Emby Server on Docker Nginx logs attached, Emby Server logs attached as well. # EMBY SERVER LOGS 2022-02-08 02:27:26.449 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/6/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.450 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/3/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.451 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/4/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.453 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/5/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.455 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/7/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.462 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/8/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/9/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/10/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/14/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/12/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/13/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/15/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 2022-02-08 02:27:26.466 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/16/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0 # EMBY SERVER LOGS 2022-02-08 02:32:31.007 Info Server: http/1.1 Response 204 to 192.168.1.3. Time: 13ms. http://192.168.1.13:8096/emby/Sessions/Playing/Progress 2022-02-08 02:32:39.741 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313277ms. http://emby.mydomain.duckdns.org/Sync/JobItems/9/File 2022-02-08 02:32:39.955 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313501ms. http://emby.mydomain.duckdns.org/Sync/JobItems/5/File 2022-02-08 02:32:40.006 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313193ms. http://emby.mydomain.duckdns.org/Sync/JobItems/25/File 2022-02-08 02:32:40.130 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313313ms. http://emby.mydomain.duckdns.org/Sync/JobItems/24/File 2022-02-08 02:32:40.276 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313809ms. http://emby.mydomain.duckdns.org/Sync/JobItems/16/File 2022-02-08 02:32:40.675 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313840ms. http://emby.mydomain.duckdns.org/Sync/JobItems/38/File 2022-02-08 02:32:40.812 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312229ms. http://emby.mydomain.duckdns.org/Sync/JobItems/57/File 2022-02-08 02:32:40.897 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312303ms. http://emby.mydomain.duckdns.org/Sync/JobItems/59/File 2022-02-08 02:32:40.974 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312381ms. http://emby.mydomain.duckdns.org/Sync/JobItems/67/File # NGINX ERROR LOGS 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443" 2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET embyserver_redacted.txt embyserver-63779937295_redacted.txt nginx_error_redacted.txt
  7. Hi, Put this together for my own use - its a bit rough around the edges but figured i'd throw it out here should anyone want to give it a whirl! Docker Hub: https://hub.docker.com/r/matty87a/telemby GitHub: https://github.com/matty87a/telemby
  8. I have an Ubuntu server running the emby server docker container. Just spun it up yesterday. My password worked no problem. Today, I tried to log in through firefox on another linux machine, and my password doesn't seem to be working. So I decided to try resetting my admin/user account password by clicking the "Forgot Password" button. When I clicked the button, it prompts me for a username. When I type the username and then hit "Submit", nothing at all seems to happen. What can I do to troubleshoot this further so I can get access to my media server again?
  9. Hello, For a while now whenever I go to watch something through emby after about 20-25 minutes the session either crashes or is forcefully closed somehow and I am not seeing the reasoning in the logs. I attached a log file to show the behavior I am seeing. Essentially no matter what file I am watching (in this case a TV episode) it will crash or close out after that rough time period. Once I re-open the video or movie and start playback again I won't have any issues at all with the movie or tv show, no matter how long I watch after. I am not sure if this is a plug in issue, but I have removed a ton of plugins to see if that was the cause but so far the issue still persists. I usually am casting through my android phone through the app (Pixel 4A with Android 12 Beta). I have emby running in a docker container (5:20.10.8~3-0~debian-buster) on OpenMediaVault (5.6.14-1) (Kernel: Linux 5.10.0-0.bpo.8-amd64). I have not been able to pinpoint exactly what causes the issue to re-occur as sometimes its overnight, sometimes its a week later. I attached the log from emby, but cannot find any log that might be stored on my phone as well to upload that. Also, I should mention that I saw others having bitrate issues and that was the root cause. I am not 100% sure how to do this in the android emby app, but I have gigabit wired ethernet running to both the chromecast as well as the server running emby, so while it may still be an issue of speed, I would highly doubt that. Log line issue occurred on: [2021-09-06 16:17:26.698 Info SessionManager: Playback stopped reported by app Emby for Chromecast 2.1.0 playing Forgetting Sarick Mortshall. Stopped at 1336684 ms] I know there are some errors in there for the coverart plugin but I know those are centered around HVEC codec and is a known issue that hasn't affected anyones playback that I can find. I also have lifetime emby premier but am seeing a warning in regards to a license, not sure what that's about either. 2021-09-06 15:52:27.982 Error Server: Access token is invalid or expired. Thank you for your time and any help you might have for me! embyserver.txt
  10. MrLinford

    [DOCKER] HTTPS is not working

    Been a while since I have had to post so just a quick thank you. I am running EmbyServer in a docker on my unRAID server (emby/embyserver:latest) and I'm trying to get HTTPS to work through my Nginx Proxy. HTTP works no problem. Client: Docker Engine - Community Version: 20.10.5 API version: 1.41 Go version: go1.13.15 Git commit: 55c4c88 Built: Tue Mar 2 20:14:11 2021 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.5 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: 363e9a8 Built: Tue Mar 2 20:18:31 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc93 GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec docker-init: Version: 0.19.0 GitCommit: de40ad0 Client: Context: default Debug Mode: false Server: Containers: 12 Running: 10 Paused: 0 Stopped: 2 Images: 12 Server Version: 20.10.5 Storage Driver: btrfs Build Version: Btrfs v4.20.1 Library Version: 102 Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 5.10.28-Unraid Operating System: Slackware 14.2 x86_64 (post 14.2 -current) OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 15.34GiB Name: NEO ID: Y3GH:2DQQ:RWFG:TAIJ:3NPK:QLXK:M5QV:F22B:HCUV:QH5I:VBER:5M6B Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine docker run -d --name='Emby' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'UID'='2' -e 'GID'='2' -e 'GIDLIST'='2,18' -p '8096:8096/tcp' -p '8920:8920/tcp' -v '/mnt/user/nas/':'/mnt':'rw' -v '/mnt/cache/appdata/EmbyServer/':'/config':'rw' --device=/dev/dri 'emby/embyserver:latest' When going to my https address I get 502. Looking in the container logs I noticed I only see `Info App: Adding HttpListener prefix http://+:8096/` I can not see HttpListener for 8920. Any thoughts why the container isn't starting HttpListener for 8920. Thank you, MrLinford
  11. Hello everyone Last Friday I restarted my Docker Emby container on Unraid. I lost all my libraries. I had the "Server Configuration Backup" extension, but no restore worked. I was using this Emby package, so I thought that this one had a problem. So I installed a new package at the end of the day. Everything was working until today when I had no cover image on my libraries. I restarted my container, and I lost all my containers. I also tried a restore but nothing worked. Also, it deleted my old Emby log files... However, I found an error in the little log file : When I look in my system, all the metadatas are deleted... ! Do you know can i fix it and restore my metadas ? Thanks a lot embyserver-63765654731.txt
  12. Hi Everyone, sorry for the long-winded post: I have approximately, 5 remote users that may be transcoding at any given time, plus 3 possible direct streams in my house, then mobile phone/tablet usage, maybe a couple at a time max (but rare, at least for now) I know there are a lot of posts where people are asking what kind of server to use, and if their server is good enough, my question(s) are different. First I will give an idea of my previous servers so you can see where I have been, so we can understand better, where I would like to go: 1.) I started with a Drobo FS (for Media) with single drive redundancy, and a Dell Poweredge R610 running a Plex server (this worked well for a few years), but I did need to rebuild Plex now and again, and setup all my coverart/other metadata a few times. (not fun). 2.) I moved to a Drobo 5N (with a cache drive) I initially tried the Plex server built into the Drobo 5N, but the server was too slow, so I went back to the Dell and used the Drobo just for the Media 3.) I lost all the Drobo files because a second drive failed during a rebuild. rip. So I moved to a Synology DS1815+ (maxed the RAM on it, 2 drive redundancy) I upgraded my Plex server to an HP DL360 G6 with 128 GB RAM and 2x Xeon 5650 (got it for cheap through my work) Eventually I lost all my metadata (not media) on Plex because a SAS drive failed. 4.) I created an iSCSI LUN on my Synology and put Plex on that (so I don't have to worry about losing the VMs/MetaData), tried that for a while, but it was too slow. (At this point I decided to switch from Plex to Emby for features as well) 5.) So FINALLY (sorry for the long post again) I ended up with my DL360 running ESXi, with an Emby VM, and a seperate torrent VM (always behind VPN). Basiclly, The DL360 isn't working anymore, it is currently in my garage, and during the summer, it sounds like a jet taking off, and the fans die often. The only place I can move it is the basement, and that doesn't fit there (it's GIANT), so I need to build a PC, and I figured I would futureproof a bit, and move away from enterprise to avoid the expensive replacement equipment. (Fans, and SAS drives). I am not sure if I should continue on the ESXi route (compatibility with non-enterprise parts seems to be annoying, and the VMWare matrix is a nightmare, at least to me), or maybe run something like FreeNAS or UnRAID (Emby Container). I don't want to go the UnRAID/FreeNAS route, only to find out that I have taken a step-back in performance (like the Drobo and the Synology server application was). However, I do like the idea of getting four M.2 500GB NVMe drives running the OS, so I never have to worry again about losing my VMs(or containers)/metadata. OR just install a linux server OS, then run all my servers as containers on that. I see that I can set a GPU to passthrough to an Emby container in UnRAID, and get GPU transcoding. So that seems like a perk. So, I am curious what everyone thinks about potential hardware setup, and what my best option may be for the OS to take advantage of said hardware. I am putting this post in hardware, because the hardware I am buying is going to change depending on what OS(s) can take advantage of it (give best performance). When it's all said and done, I'll want a full replacement for the Emby Server (currently ESXi VM) and my torrent server (ESXi VM) and a couple other servers (Home assistant, Minecraft, whatever else I am playing with). With the best possible performance. How much RAM do you think? (like 32 or 64 DDR4 will be way faster than the 128GB that I hardly use currently) Intel CPU (probably, right?), Nvdia Video card seems to be a good choice (around 2070 looks fine)...? RAID on SSD or NVMe, at the OS level? Is this just going ridiculously overkill? Can anyone help with some ideas please? I would really appreciate any insight to help me make some decisions before it starts getting too hot in the garage. Thank you!
  13. Hi, And thanks for this software. Right now I'm running emby server (premiere) on synology app (NAS is a 918+) ; client is installed on a first generation nvidia shield . All is connected via ethernet. Sometimes (rarely to be frank, very rarely) I got stuttering, mainly x or h265 files. I get two months ago a second hand elitedesk G4 mini (UHD Graphics 630) and installed linux (ubuntu 20.04 server) to run some valheim, minecraft and conan exiles servers via docker. And I wonder if using an emby container on this linux computer would improve performances. CPU is way better in the G4 than in the NAS. RAM is the same, 32Go. I have several questions, having close to none tech skill. 1- In my current setup (syno server to shield), which is "decoding" the stream ? NAS is decoding, and shield just have to display ? Shield is decoding, NAS being just providing the files for the shield to decode ? 2- In my current setup, is there some tips I should use to improve streaming ? 3- In my current setup, should I check somewhere if some sort of hardware acceleration is activated ? On the NAS ? The Shield ? 4- Would using linux server as a host for an emby container, NAS only for storage and the shield as a client improve the experience ? Once again thanks for the program, and the forum. I have a lot of informations available should I install emby docker on linux... Regards, F.
  14. I am using docker, i have the exact same set up with jellyfin, i just wanted to try emby as they have apps for my lg tv. If i go into my docker containers cli i can see all the films and tv shows, they just don't appear in my movie or tv show library on the emby gui when i have scanned them, the path is exactly the same as my existing jellyfin docker which works without issue. Logs are here: Info App: Loading Emby.Notifications, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info App: Loading Emby.Codecs.Dxva, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info App: Loading Emby.Codecs, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info App: Loading Emby.Server.Connect, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info App: Loading Emby.Server.Sync, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info App: Loading EmbyServer, Version=4.6.4.0, Culture=neutral, PublicKeyToken=null, Info SqliteUserRepository: Sqlite version: 3.35.5, Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-8.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_JSON1,ENABLE_MATH_FUNCTIONS,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, Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal, Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal, Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal, Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal, Info App: Adding HttpListener prefix http://+:8096/, Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal, Info SqliteItemRepository: cache_size is -98304, Info SqliteItemRepository: page_size is 4096, Info FfmpegManager: FFMpeg: /bin/ffmpeg, Info FfmpegManager: FFProbe: /bin/ffprobe, Info FfmpegManager: FFDetect: /bin/ffdetect, Info Skia: SkiaSharp version: 2.80.0.0, Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 08/10/2021 02:00:00, which is 147.766498335 minutes from now., Info TaskManager: Daily trigger for Rotate log file set to fire at 08/10/2021 00:00:00, which is 27.765629838333332 minutes from now., Info App: ServerId: 160d125f79c749ceaeb31cd227f2eb47, Info Server: http/1.1 GET http://192.168.0.7:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Linux; Android 10; ONEPLUS A6013 Build/QKQ1.190716.003; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/92.0.4515.131 Mobile Safari/537.36, Info Server: http/1.1 Response 503 to 192.168.0.5. Time: 156ms. http://192.168.0.7:8096/emby/system/info/public, Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint, Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1, Info NetworkManager: Detected local ip addresses: 192.168.0.7, 127.0.0.1, Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.3627385 seconds, Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint, Info App: Loading data from /config/data/connect.txt, Info App: Loading data from /config/data/wan.dat, Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0222597 seconds, Info App: Core startup complete, Info App: Post-init migrations complete, Info App: Starting entry point Emby.Security.PluginSecurityManager, Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 0.0003403 seconds, Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint, Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0006473 seconds, Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint, Info App: Entry point completed: Emby.Webhooks.WebhooksEntryPoint. Duration: 0.0091679 seconds, Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding, Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0022248 seconds, Info App: Starting entry point NfoMetadata.EntryPoint, Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0009112 seconds, Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint, Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 0.0003795 seconds, Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint, Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0048624 seconds, Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint, Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0006593 seconds, Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint, Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0022856 seconds, Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup, Info App: Init BeginReceive on 0.0.0.0, Info App: Init BeginReceive on 0.0.0.0, Info App: Init BeginReceive on 192.168.0.7, Info App: Init BeginReceive on 127.0.0.1, Info HttpClient: GET https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog, Info LibraryMonitor: Skipping realtime monitor for /data/movies because the path does not exist, Info LibraryMonitor: Skipping realtime monitor for /data/tvshows because the path does not exist, Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.7805528 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0010587 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0006837 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0084622 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0087661 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.001243 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0017413 seconds, Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier, Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.000559 seconds, Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint, Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0073198 seconds, Info App: Starting entry point Emby.LiveTV.EntryPoint, Info LiveTV: Loading live tv data from /config/data/livetv/timers, Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0511545 seconds, Info App: Starting entry point Emby.LiveTV.UpgradeChannelOptionsEntryPoint, Info App: Entry point completed: Emby.LiveTV.UpgradeChannelOptionsEntryPoint. Duration: 0.0037867 seconds, Info App: Starting entry point Emby.LiveTV.RecordingNotifier, Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0070804 seconds, Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint, Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.009562 seconds, Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint, Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0040112 seconds, Info App: Starting entry point Emby.Notifications.Notifications, Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0011337 seconds, Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint, Info App: SyncRepository Initialize taking write lock, Info App: SyncRepository Initialize write lock taken, Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0143517 seconds, Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint, Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0058497 seconds, Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint, Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0004983 seconds, Info App: All entry points have started
  15. Hello, Still quite new to using Emby with Docker. Below is the line from my container run for the configuration folder. The container creates the folder. I also tested prior by having the folders already created locally. However the container is still creating the folder within itself as far as I know. I also have a Sonarr setup where I'm using a similar line of code to have it put its configuration files in the below successfully. I just wanted to have all of my containers configuration files uniformly accessible in the same location incase I want to check logs outside of the respective services, and create backups without having to backup the entire container. Regards, Vivid
  16. After Recreating my (32bit) Pi4B / OMV / Docker / Portainer image to upgrade to Emby 4.6, the /app/emby/EmbyServer process was constantly restarting, with no access to the Emby Web interface. After a lot of web searching and several blind alleys the solution is here: https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal Manually installing libseccomp2_2.4.4-1~bpo10+1_armhf.deb (Option 2) worked for me, although I've subsequently added the Buster backports repo (Option 3) Hope this saves time and anxiety for someone....
  17. Hello Community, I was hoping someone else is having a similar problem and perhaps know the reason why after the second to last update of Emby, my collections vanished (both user created, and those generated by the box set plugin). At first I thought it had to be ownership/permissions had become muddled, but all other writes are allowed (updates to metadata, metadata refreshes on intervals, favourites) Here is a breakdown of my formerly working setup: Emby running on Docker - app folder in home directory to utilize the SSD benefit. OS: Fedora 33 - kept up to date daily Docker image is from Linuxserver.io (I chose that image to keep things in line with my other services, and ease of setup Permissions are defined in the docker-compose file for PGID:1000 (logged user) and GUID:973 (docker) however i've also tried chowning the permissions to 1000:1000 in both the .yaml file and filesystem in keeping with linuxserver.io's standard setups.. No joy as of yet.. I'm copying a backup of the emby appdata folder to backup in an attempt to start fresh, if that doesn't work i'll restore and hope that either emby, or the image provider figures it out. One thing worth noting, while I can't make a collection, the Boxset plugin CAN, and I can add and remove from them, if I try to create my own it circles out. I'd really prefer to keep my watched status. not so much for me, but my elderly parents (also my main reason for fighting with collections, so I can narrow down content for them) so I was wondering if the community can : 1) Diagnose what might have happened to either the config or the docker image (last two versions, first time lost all collections, I tried backing up the collections folder and starting new, no joy. or 2) If I create a new instance, which folders to keep so my 2 users keep their watched status. I don't mind rescanning metadata and tailoring the layout again. Any help would be appreciated, I hope I gave the community enough information, so as to not waste your time. Thank You, Ray.
  18. cappapp

    TV Shows by date added wrong order?

    My emby docker no longer displays tv shows by date added properly any more. Everything else seems fine. But I get a mix of old and new shows when sorting by date added. Any ideas what might cause this? @Happy2Play please move my posting to a new topic. Thanks.
  19. I have a Samsung TV (UN65H6350) and I use docker and docker-compose to use embyserver. However, in DLAN mode of Samsung TV, embyserver can only be found up to version 3.2.70.0. From v3.2.70 to the latest version, it cannot be detected in DLAN mode. I kept using emby/embyserver:3.2.70.0 due to dlan issue, but it is no longer compatible with android apps, so i have no choice but to update embyserver. I wish UN65H6350 DLAN could work on the latest version of Embyserver.
  20. ivolanski

    Emby Docker exit after few seconds

    Hello, First of all, thanks in advance for any help you can give me and feel free to ask anything else if you need more information. Emby docker just stop after few seconds, here are some information: It's a N1 box running Openwrt and it contains docker.
  21. ShadowKindjal

    Nvidia Runtime Docker Compose

    Would anyone be able to help me? I have a docker install for Emby currently working but I would like to use Docker Compose to further simplify the process. I noticed that the Nvidia runtime is not supported within the docker-compose.yml file but does anyone know a way to maybe incorporate the runtime with a Dockerfile? Any help would be appreciated.
  22. mengoshmink

    (Ubuntu + Docker +) Emby + Tvheadend

    Hi, I have created this in the hope it helps others. It isn't very detailed but hopefully enough information to be helpful. Thank you. My setup: Ubuntu 20.04.1 LTS (I would prefer if this said CEntOS but that's another story) TurboSight TBS 6280 DVB-T/T2/C (SAA716x dvb adapter) Docker (I don't think this effects my guide much below but worth mentioning) Emby (emby/embyserver:latest version on as of 9th January 2021) Tvheadend (linuxserver/tvheadend:latest version on as of 9th January 2021) docker-compose.yml Install required software (Ubuntu, TBS drivers, docker, docker-compose) Check DVB adapter exists $ ls /dev/dvb/ Install required Docker images/containers (see attached docker-compose.yml) $ docker-compose up -d http://tvheadend:9981 (setup Tvheadend) Configuration > Start wizard > Language (save and next) > Access control details (either on this screen or after the wizard create a user with the username * and no password (see attached User login.png) Tuners and network (configure as required) Assign Predefined Muxes to Networks (configure as required) > Scanning (save and next) > Map services to channels (configure as required) > Finish http://emby:8096 (setup Emby) Settings > Live TV > Live TV > TV Sources > M3U Tuner (http://tvheadend:9981/playlist/channels.m3u) Settings > Live TV > Live TV > TV Guide Data Providers > Guide Data Setup (configure country as required) and Guide source: XmlTV > File or URL (http://tvheadend:9981/xmltv/channels) Settings > Users > Access > Recordings Notes: Recordings made through the Tvheadend interface are separate to recordings made through the Emby interface. If I haven't mentioned a setting, chances are I haven't changed from the default. Multiple screen shots are attached to help clarify some steps. The M3U link can be tested in VLC media player: Media > Open Network Stream > network URL: http://tvheadend:9981/playlist/channels.m3u The channels link can be tested in an internet browser by pasting the link into the address bar. http://tvheadend:9981/xmltv/channels I hope this helps someone docker-compose.yml
  23. teiva

    Benefits to docker?

    Setup: Ubuntu Server 16.04 Docker 1.12.2 Windows 10 client (Bash/Putty) I'm new to Emby, linux and docker. Can someone explain to me how installing Emby server via docker has made my setup easier or better? I hear things like "segregation", "pre-configured" and "seamless". I need some context. How's it pre-configured? Can I skip any of these file system setup steps since I pulled from the dev container? SAMBA setup - Set to automatically mount drives on boot - Setup ownership and permissions on media folders - Setup sharing over network with Window clients Should I be installing other apps into the Emby server docker container or into a new container? For example: - Sonarr - CouchPotato - Sabnzbd ...I'm still in the middle of setting everything up. Thanks in advance!
  24. How to secure Emby using LetsEncrypt and Nginx Reverse Proxy by modifying Docker containers in Openmediavault. https://youtu.be/jYoDyoH2C0A
  25. sebasmiles

    Docker won't start after update

    System: Unraid Docker: Latest (as of 11/02/20) So after the latest docker update, my docker doesn't start. So far all my other dockers are doing well. Below is what it shows me in the docker log, the emby log (from the folder on the shared) isn't showing anything at all since the update so something is happening before it starts saving it. Let me know if there is some other way to pull log info. Update: When I pulled the logs directly from Docker command prompt. the "r" line in logs was actually "Bus error" [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Bus error [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
×
×
  • Create New...