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 Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • 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
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Hey Emby Sages, looking for some help figuring out why some flac files play via the web interface and some don't. The errors are presenting in Firefox 59.02. They do not occur via the Android App and when I download the offending file to the local storage I'm able to play it in the client's OS (Rhythmbox). docker logs -f [container name] doesn't yield anything past the success of the entrypoint script. Is there a way (possibly via attach?) that I can get a better look at what the decoding/encoding error might be? Thanks in advance Mike
  2. PortableStick

    Example of working Docker install w/Nextcloud

    Hey all, I think it's pretty common for people to want to self-host both Emby and Nextcloud, but for those who are new to Docker or hosting in general, just getting up and running can be a time-sink. This is especially true if you're wanting to use LetsEncrypt. It took me a couple of days to put this information together, so I figured I'd share what I came up with for anyone else to use or to see as an example. Some of this stuff was not well documented, so I hope it helps someone else in the future. https://github.com/PortableStick/EmbyNextcloudDocker
  3. anderbytes

    Docker Bridge vs DLNA

    Hi. Has anyone successfully enabled DLNA in Emby via Docker and has Bridge networking configured instead of Host networking? I follow all the instructions but DLNA is NEVER visible from outside the container. If I change networking to HOST, then everything works fine.
  4. Hey Guys. I want to add Emby to my current setup with a nginx reverse proxy, lets encrypt and nextcloud. I already tried some things but it didnt worked so I hope you can help me. docker-compose.yml: version: '2' services: proxy: image: jwilder/nginx-proxy container_name: proxy ports: - 80:80 - 443:443 volumes: - ./proxy/conf.d:/etc/nginx/conf.d - ./uploadlimit.conf:/etc/nginx/conf.d/uploadlimit.conf:ro - ./proxy/vhost.d:/etc/nginx/vhost.d - ./proxy/html:/usr/share/nginx/html - ./proxy/certs:/etc/nginx/certs:ro - /var/run/docker.sock:/tmp/docker.sock:ro networks: - proxy-tier restart: always letsencrypt-companion: image: jrcs/letsencrypt-nginx-proxy-companion container_name: letsencrypt-companion volumes_from: - proxy volumes: - /var/run/docker.sock:/var/run/docker.sock:ro - ./proxy/certs:/etc/nginx/certs:rw restart: always web: image: nginx container_name: nextcloud_webserver volumes: - ./nginx.conf:/etc/nginx/nginx.conf:ro links: - app volumes_from: - app environment: - VIRTUAL_HOST=nextcloud.mydomain.de, alternative.domain.de - VIRTUAL_NETWORK=nginx-proxy - VIRTUAL_PORT=80 - LETSENCRYPT_HOST=nextcloud.mydomain.de, alternative.domain.de - LETSENCRYPT_EMAIL=my@email.de networks: restart: always app: image: nextcloud:fpm container_name: nextcloud_fpm links: - db volumes: - ./nextcloud/apps:/var/www/html/apps - ./nextcloud/config:/var/www/html/config - /mainstorage/nextcloud/data:/var/www/html/data networks: - proxy-tier restart: always db: image: mariadb container_name: db volumes: - /mainstorage/nextcloud/db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD=securepw - MYSQL_DATABASE=nextcloud - MYSQL_USER=user - MYSQL_PASSWORD=anothersecurepw networks: - proxy-tier restart: always networks: proxy-tier: external: name: nginx-proxy nginx.conf: user www-data; events { worker_connections 768; } http { upstream backend { server app:9000; } include /etc/nginx/mime.types; default_type application/octet-stream; server { listen 80; # Add headers to serve security related headers add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; root /var/www/html; client_max_body_size 10G; # 0=unlimited - set max upload size fastcgi_buffers 64 4K; gzip off; index index.php; error_page 403 /core/templates/403.php; error_page 404 /core/templates/404.php; rewrite ^/.well-known/carddav /remote.php/dav/ permanent; rewrite ^/.well-known/caldav /remote.php/dav/ permanent; location = /robots.txt { allow all; log_not_found off; access_log off; } location ~ ^/(build|tests|config|lib|3rdparty|templates|data)/ { deny all; } location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) { deny all; } location / { rewrite ^/remote/(.*) /remote.php last; rewrite ^(/core/doc/[^\/]+/)$ $1/index.html; try_files $uri $uri/ =404; } location ~ \.php(?:$|/) { fastcgi_split_path_info ^(.+\.php)(/.+)$; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_param HTTPS on; fastcgi_param modHeadersAvailable true; #Avoid sending the security headers twice fastcgi_pass backend; fastcgi_intercept_errors on; } # Adding the cache control header for js and css files # Make sure it is BELOW the location ~ \.php(?:$|/) { block location ~* \.(?:css|js)$ { add_header Cache-Control "public, max-age=7200"; # Add headers to serve security related headers add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Content-Type-Options nosniff; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; # Optional: Don't log access to assets access_log off; } # Optional: Don't log access to other assets location ~* \.(?:jpg|jpeg|gif|bmp|ico|png|swf)$ { access_log off; } } } I already tried something like adding emby: image: emby/embyserver container_name: emby volumes: - /mainstorage/emby/config:/config - /mainstorage/nextcloud/data/user1/files/:/mnt/share1 - /mainstorage/nextcloud/data/user2/files/:/mnt/share2 devices: - /dev/dri/renderD128 networks: - proxy-tier restart: always to the docker-compose file but it didnt work. My Goal is to be able to access emby from a different subdomain than my nextcloud. Like nextcloud access is under nextcloud.mydomain.de and emby is emby.mydomain.de. I hope someone can help me
  5. FredFrin

    Login Session won't expire

    Hi, Emby-server: docker on Linux, Version 3.2.60.0 Client: Chromium Browser This is sort of weird. I was unable to remove some LiveTV test channel data, so I did the folowing: - stopped server - removed the .emby-server directory - all runntime data - cleared all browser history data incl cookies, shift-reload the emby page - re-start server as per https://hub.docker.com/r/emby/embyserver/ docker run -it --rm -v /usr/local/bin:/target emby/embyserver instl - start the emby-server with: emby-server - as expected I'm asked for a media directory on the host .. entered. - parts of the login page seem to blink, but I'm still forwarded to the home page (???) - if I sign-out, I'm redirected to the server config page. - from the server page I can return to the Home page without login. Unsurprisingly I then start seeing these messages in the log: MediaBrowser.Controller.Net.SecurityException: Access token is invalid or expired. I do not seem to be able to force a fresh login & session ... Adding log extract: 2018-01-07 01:49:26.907 Info HttpServer: HTTP POST http://192.168.43.8:8096/emby/Sessions/Logout. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.912 Info SessionManager: Logging out access token 14e63e8b7681463c97ffa28a71bb3e17 2018-01-07 01:49:26.913 Info HttpServer: HTTP Response 204 to 192.168.42.18. Time: 5ms. http://192.168.43.8:8096/emby/Sessions/Logout 2018-01-07 01:49:26.924 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/users/public. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.925 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Branding/Configuration. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.925 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 1ms. http://192.168.43.8:8096/emby/users/public 2018-01-07 01:49:26.928 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/Branding/Configuration 2018-01-07 01:49:26.936 Info HttpServer: HTTP POST http://192.168.43.8:8096/emby/Users/authenticatebyname. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.938 Info UserManager: Authentication request for stef has succeeded. 2018-01-07 01:49:26.938 Info SessionManager: Creating new access token for user 46a857f876aa4b2cb6664cf7a23e8d47 2018-01-07 01:49:26.940 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 4ms. http://192.168.43.8:8096/emby/Users/authenticatebyname 2018-01-07 01:49:26.961 Info HttpServer: HTTP POST http://192.168.43.8:8096/emby/Sessions/Capabilities/Full. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.962 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/DisplayPreferences/usersettings?userId=46a857f876aa4b2cb6664cf7a23e8d47&client=emby. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.963 Info HttpServer: WS ws://192.168.43.8:8096/embywebsocket?api_key=6bb578b4e86343bab9fea70f44d10ff4&deviceId=22bb3ec758cbc33e55cc0ad3397202294371d349. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.965 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/DisplayPreferences/usersettings?userId=46a857f876aa4b2cb6664cf7a23e8d47&client=emby 2018-01-07 01:49:26.968 Info HttpServer: HTTP Response 204 to 192.168.42.18. Time: 7ms. http://192.168.43.8:8096/emby/Sessions/Capabilities/Full 2018-01-07 01:49:26.994 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Users/46a857f876aa4b2cb6664cf7a23e8d47. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.996 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Notifications/46a857f876aa4b2cb6664cf7a23e8d47/Summary. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:26.997 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 1ms. http://192.168.43.8:8096/emby/Notifications/46a857f876aa4b2cb6664cf7a23e8d47/Summary 2018-01-07 01:49:26.997 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/Users/46a857f876aa4b2cb6664cf7a23e8d47 2018-01-07 01:49:27.008 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Users/46a857f876aa4b2cb6664cf7a23e8d47. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.011 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/Users/46a857f876aa4b2cb6664cf7a23e8d47 2018-01-07 01:49:27.037 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Sessions. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.038 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/ScheduledTasks. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.039 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Plugins/SecurityInfo. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.039 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 1ms. http://192.168.43.8:8096/emby/ScheduledTasks 2018-01-07 01:49:27.040 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/Sessions 2018-01-07 01:49:27.040 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 1ms. http://192.168.43.8:8096/emby/Plugins/SecurityInfo 2018-01-07 01:49:27.045 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/System/Info. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.048 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/System/Info 2018-01-07 01:49:27.051 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2018-01-06T00%3A49%3A27.036Z. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.052 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/News/Product?StartIndex=0&Limit=4. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.055 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 4ms. http://192.168.43.8:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2018-01-06T00%3A49%3A27.036Z 2018-01-07 01:49:27.055 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/News/Product?StartIndex=0&Limit=4 2018-01-07 01:49:27.060 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/LiveTv/Recordings?UserId=46a857f876aa4b2cb6664cf7a23e8d47&IsInProgress=true&Fields=CanDelete%2CPrimaryImageAspectRatio&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.060 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.062 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 2ms. http://192.168.43.8:8096/emby/web/configurationpages?pageType=PluginConfiguration&EnableInMainMenu=true 2018-01-07 01:49:27.062 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 3ms. http://192.168.43.8:8096/emby/LiveTv/Recordings?UserId=46a857f876aa4b2cb6664cf7a23e8d47&IsInProgress=true&Fields=CanDelete%2CPrimaryImageAspectRatio&EnableTotalRecordCount=false&EnableImageTypes=Primary%2CThumb%2CBackdrop 2018-01-07 01:49:27.069 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Packages/Updates?PackageType=UserInstalled. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.072 Info InstallationManager: Opening /config/cache/serverpackages.json 2018-01-07 01:49:27.099 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 30ms. http://192.168.43.8:8096/emby/Packages/Updates?PackageType=UserInstalled 2018-01-07 01:49:27.108 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Packages/Updates?PackageType=System. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.130 Info HttpServer: HTTP Response 200 to 192.168.42.18. Time: 22ms. http://192.168.43.8:8096/emby/Packages/Updates?PackageType=System 2018-01-07 01:49:27.172 Info HttpServer: HTTP GET http://192.168.43.8:8096/web/css/images/logoblack.png. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/63.0.3239.84 Chrome/63.0.3239.84 Safari/537.36 2018-01-07 01:49:27.173 Info HttpServer: HTTP Response 304 to 192.168.42.18. Time: 1ms. http://192.168.43.8:8096/web/css/images/logoblack.png 2018-01-07 01:49:30.804 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Users/47e6580c7989434db765cc3ede23f7e3/Items?Recursive=true&limit=1&Fields=DateCreated,Etag&SortBy=DateCreated&SortOrder=Descending&IncludeItemTypes=Movie,Episode&ImageTypeLimit=0&format=json. UserAgent: 2018-01-07 01:49:30.815 Error HttpServer: Error processing request *** Error Report *** Version: 3.2.60.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.10.0.42 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Oct 1 17:55:43 UTC 2017) Processor count: 4 Program data path: /config Application directory: /usr/lib/emby-server/bin MediaBrowser.Controller.Net.SecurityException: Access token is invalid or expired. at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken (MediaBrowser.Model.Services.IRequest request, System.String token) [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateUser (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Controller.Net.IAuthenticationAttributes authAttribtues) [0x0002e] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.HttpServer.Security.AuthService.Authenticate (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Controller.Net.IAuthenticationAttributes authAttribtues) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 at MediaBrowser.Controller.Net.AuthenticatedAttribute.RequestFilter (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Model.Services.IResponse response, System.Object requestDto) [0x00005] in <8c9e2cb1cee44ce5aa58258dd61a92e3>:0 at Emby.Server.Implementations.HttpServer.HttpListenerHost.ApplyRequestFilters (MediaBrowser.Model.Services.IRequest req, MediaBrowser.Model.Services.IResponse res, System.Object requestDto) [0x0006c] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.Services.ServiceHandler+<ProcessRequestAsync>d__15.MoveNext () [0x000bc] in <a12a7c6217e143eaa39430af322cb07e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.HttpServer.HttpListenerHost+<RequestHandler>d__72.MoveNext () [0x006f4] in <a12a7c6217e143eaa39430af322cb07e>:0 MediaBrowser.Controller.Net.SecurityException at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken (MediaBrowser.Model.Services.IRequest request, System.String token) [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateUser (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Controller.Net.IAuthenticationAttributes authAttribtues) [0x0002e] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.HttpServer.Security.AuthService.Authenticate (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Controller.Net.IAuthenticationAttributes authAttribtues) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 at MediaBrowser.Controller.Net.AuthenticatedAttribute.RequestFilter (MediaBrowser.Model.Services.IRequest request, MediaBrowser.Model.Services.IResponse response, System.Object requestDto) [0x00005] in <8c9e2cb1cee44ce5aa58258dd61a92e3>:0 at Emby.Server.Implementations.HttpServer.HttpListenerHost.ApplyRequestFilters (MediaBrowser.Model.Services.IRequest req, MediaBrowser.Model.Services.IResponse res, System.Object requestDto) [0x0006c] in <a12a7c6217e143eaa39430af322cb07e>:0 at Emby.Server.Implementations.Services.ServiceHandler+<ProcessRequestAsync>d__15.MoveNext () [0x000bc] in <a12a7c6217e143eaa39430af322cb07e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.HttpServer.HttpListenerHost+<RequestHandler>d__72.MoveNext () [0x006f4] in <a12a7c6217e143eaa39430af322cb07e>:0 2018-01-07 01:49:30.815 Info HttpServer: HTTP Response 401 to 192.168.43.8. Time: 11ms. http://192.168.43.8:8096/emby/Users/47e6580c7989434db765cc3ede23f7e3/Items?Recursive=true&limit=1&Fields=DateCreated,Etag&SortBy=DateCreated&SortOrder=Descending&IncludeItemTypes=Movie,Episode&ImageTypeLimit=0&format=json 2018-01-07 01:49:30.817 Info HttpServer: HTTP GET http://192.168.43.8:8096/emby/Users/47e6580c7989434db765cc3ede23f7e3/Items?Recursive=true&limit=1&Fields=DateCreated,Etag&SortBy=DatePlayed&SortOrder=Descending&IncludeItemTypes=Movie,Episode&ImageTypeLimit=0&format=json. UserAgent: 2018-01-07 01:49:30.819 Error HttpServer: Error processing request *** Error Report *** Version: 3.2.60.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.10.0.42 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Oct 1 17:55:43 UTC 2017) Processor count: 4 Program data path: /config Application directory: /usr/lib/emby-server/bin MediaBrowser.Controller.Net.SecurityException: Access token is invalid or expired.
  6. Hi, I am hoping this is the right place to ask. I am trying to install emby for the first time and facing some issues. I am using docker and ansible to get it working. Ansible script is pretty simple - name: Install Emby docker: name: emby image: emby/embyserver:latest state: reloaded pull: always privileged: yes restart_policy: always volumes: - "{{ appdata }}/emby/test:/config:rw" - "/tmp:/tmp:rw" - "{{ media }}:/media:ro" ports: - "8096:8096" #host:container - "8920:8920" env: APP_UID: 1050 APP_GID: 1050 APP_USER: "{{dockeruser}}" VERSION: latest The "APPDATA" folder is a CIFS mount on the remote NAS, the all required folders are created and dockeruser has access and permissions to write. bash-4.4# cd /config/ bash-4.4# ls -lah total 4.0K drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 . drwxr-xr-x 41 root root 4.0K Dec 26 02:46 .. drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 cache drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 config drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 data drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 localization drwxrwxr-x 2 dockeruser dockeruser 0 Dec 26 2017 logs But I get an exception on startup of emby: 2017-12-26T02:46:45.103737485Z *** Error Report *** 2017-12-26T02:46:45.103745195Z Version: 3.2.60.0 2017-12-26T02:46:45.103749733Z Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh 2017-12-26T02:46:45.103755378Z Operating system: Unix 3.16.0.4 2017-12-26T02:46:45.103759083Z 64-Bit OS: True 2017-12-26T02:46:45.103762662Z 64-Bit Process: True 2017-12-26T02:46:45.103766230Z User Interactive: False 2017-12-26T02:46:45.103770132Z Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Oct 1 17:55:43 UTC 2017) 2017-12-26T02:46:45.103775094Z Processor count: 2 2017-12-26T02:46:45.103779418Z Program data path: /config 2017-12-26T02:46:45.103783731Z Application directory: /usr/lib/emby-server/bin 2017-12-26T02:46:45.103787682Z System.AggregateException: One or more errors occurred. ---> SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. 2017-12-26T02:46:45.103793143Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3 db, System.Int32 rc) [0x0001a] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103797254Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3_stmt stmt, System.Int32 rc) [0x00006] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103801365Z at SQLitePCL.pretty.StatementImpl.MoveNext () [0x00056] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103805152Z at SQLitePCL.pretty.DatabaseConnection.ExecuteAll (SQLitePCL.pretty.IDatabaseConnection This, System.String sql) [0x0001d] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.103811208Z at Emby.Server.Implementations.Data.ManagedConnection.ExecuteAll (System.String sql) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103815564Z at Emby.Server.Implementations.Data.BaseSqliteRepository.RunDefaultInitialization (Emby.Server.Implementations.Data.ManagedConnection db) [0x00079] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103819573Z at Emby.Server.Implementations.Data.SqliteUserRepository.Initialize () [0x00008] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103823603Z at Emby.Server.Implementations.ApplicationHost.GetUserRepository () [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103827786Z at Emby.Server.Implementations.ApplicationHost+<RegisterResources>d__308.MoveNext () [0x005ce] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.103831952Z --- End of stack trace from previous location where exception was thrown --- 2017-12-26T02:46:45.103873899Z at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.103898654Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104062434Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104067354Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104071357Z at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104075767Z at Emby.Server.Implementations.ApplicationHost+<Init>d__303.MoveNext () [0x0024c] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104202780Z --- End of inner exception stack trace --- 2017-12-26T02:46:45.104461756Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00242] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104468762Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks, System.Int32 millisecondsTimeout) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104472933Z at System.Threading.Tasks.Task.WaitAll (System.Threading.Tasks.Task[] tasks) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104477195Z at MediaBrowser.Server.Mono.MainClass.RunApplication (Emby.Server.Implementations.ServerApplicationPaths appPaths, MediaBrowser.Model.Logging.ILogManager logManager, Emby.Server.Implementations.StartupOptions options) [0x000d4] in <ce6ca2d6e906484ab100b2c0b72cc4b9>:0 2017-12-26T02:46:45.104481691Z at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x00085] in <ce6ca2d6e906484ab100b2c0b72cc4b9>:0 2017-12-26T02:46:45.104723594Z ---> (Inner Exception #0) Busy: database is locked 2017-12-26T02:46:45.104743338Z SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. 2017-12-26T02:46:45.104748462Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3 db, System.Int32 rc) [0x0001a] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104758565Z at SQLitePCL.pretty.SQLiteException.CheckOk (SQLitePCL.sqlite3_stmt stmt, System.Int32 rc) [0x00006] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104763157Z at SQLitePCL.pretty.StatementImpl.MoveNext () [0x00056] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104766973Z at SQLitePCL.pretty.DatabaseConnection.ExecuteAll (SQLitePCL.pretty.IDatabaseConnection This, System.String sql) [0x0001d] in <926d5dc8f35f4aae9a6008f11f233fd0>:0 2017-12-26T02:46:45.104770851Z at Emby.Server.Implementations.Data.ManagedConnection.ExecuteAll (System.String sql) [0x00000] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104774649Z at Emby.Server.Implementations.Data.BaseSqliteRepository.RunDefaultInitialization (Emby.Server.Implementations.Data.ManagedConnection db) [0x00079] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104795683Z at Emby.Server.Implementations.Data.SqliteUserRepository.Initialize () [0x00008] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104801831Z at Emby.Server.Implementations.ApplicationHost.GetUserRepository () [0x00027] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104805745Z at Emby.Server.Implementations.ApplicationHost+<RegisterResources>d__308.MoveNext () [0x005ce] in <a12a7c6217e143eaa39430af322cb07e>:0 2017-12-26T02:46:45.104809863Z --- End of stack trace from previous location where exception was thrown --- 2017-12-26T02:46:45.104814200Z at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104819577Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-12-26T02:46:45.104823695Z at System.Runtime.CompilerServices.TaskAwaiter. If I don't mount the location of the emby APPDATA (where I want to store DB files etc...) then emby seems to start. but this isn't ideal at all I don't want to keep this data in the VM or in Docker. Please help. server-63649853436.txt unhandled_f3903ef0-3e41-4099-954d-13d897bd6838.txt
  7. ACoolUsername

    Not playing video through Nginx reverse proxy

    Hey, I have emby installed using the docker and behind an nginx reverse proxy, I used the config from this post https://emby.media/community/index.php?/topic/47508-how-to-nginx-reverse-proxy. Shown below. worker_processes 4; events { worker_connections 8192; } http { include mime.types; default_type application/octet-stream; server_tokens off; sendfile off; gzip on; gzip_disable "msie6"; gzip_comp_level 6; gzip_min_length 1100; gzip_buffers 16 8k; gzip_proxied any; gzip_types text/plain text/css text/js text/xml text/javascript application/javascript application/x-javascript application/json application/xml application/rss+xml image/svg+xml; tcp_nodelay on; server_names_hash_bucket_size 128; map_hash_bucket_size 64; ## Start: Timeouts ## client_body_timeout 10; client_header_timeout 10; keepalive_timeout 30; send_timeout 10; keepalive_requests 10; ## End: Timeouts ## ## Default Listening ## server { listen 80 default_server; listen [::]:80 default_server; server_name _; return 301 https://$host$request_uri; } ##EMBY Server## server { listen [::]:443 ssl; listen 443 ssl; #listen 80; #listen [::]:80; server_name emby.mydomain.com; access_log /var/log/nginx/emby.mydomain.com-access.log; error_log /var/log/nginx/emby.mydomain.com-error.log; ssl_protocols TLSv1.2 TLSv1.1; ssl_certificate /etc/letsencrypt/live/emby.mydomain.com/cert.pem; ssl_certificate_key /etc/letsencrypt/live/emby.mydomain.com/privkey.pem; ssl_session_cache shared:SSL:10m; #add_header Public-Key-Pins ' #pin-sha256="8TzXdhbnv+l6EjDG2Vj9EmgGiSmZenrTZSNUFEwyUE="; #pin-sha256="YLh1dUR9y6Kja30RrAn7JKnbQG/utLMkBgFF2Fuihg="; #pin-sha256="Vjs8r4z+80wjNcr1KepWQboSIRi63WsWXhIMN+eWys="; #max-age=86400; includeSubDomains'; add_header X-Xss-Protection "1; mode=block" always; add_header X-Content-Type-Options "nosniff" always; add_header Strict-Transport-Security "max-age=2592000; includeSubdomains" always; add_header X-Frame-Options "SAMEORIGIN" always; proxy_hide_header X-Powered-By; add_header 'Referrer-Policy' 'no-referrer'; add_header Content-Security-Policy "frame-ancestors mydomain.com emby.mydomain.com;"; location / { proxy_pass http://localhost:8096; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #Next three lines allow websockets proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } } I am able to access emby through the reverse proxy and can browse media and manage server but whenever I try to play videos it just shows a black screen and the loading icon and eventually an error message will appear . I have tested this with Chrome, Firefox, Edge and Opera and they all give the same result (Firefox and Edge show the poster and loading icon). Everything works fine when connecting directly to emby (emby.mydomain.com:8904). Any help would be much appreciated.
  8. Hey guys, I have finally setup emby with docker. Now that I tried to play a movie, I have noticed that the max media playback time starts fairly low and increases every two seconds. I cannot navigate to the middle or end. It looks like the time I see belongs to the copy of the movie which is being transcoded and therefore growing. Does someone have an idea why I do not see the original playback time/duration?
  9. Good night. I just pulled the latest image version and before replacing my installation I tried it in a new container with all the same options as the original (except for name), and I got a nice list of errors on the first run. I'll post it here, and perhaps someone wants to take a look and tell if it's normal or I have something corrupted in my "/config" stout.log sterr.log
  10. I have messed with the stable emby, and the two most recent beta releases. My server is running Unraid and im using the official Emby docker. The server specs are Core i7 4790 with 32GB ram with a 5Gb/s network connection, allot of my media is stored on a separate Synology server that has a 2Gb/s network connection. Just as a reference I have Plex running using the exact same configuration and it is lightning fast. So the issue I am having is that 99% of the time I open the Emby web app, Windows 10 App, or iPhone app, it is excruciatingly slow. I'm talking 5-10min just to load the main screen, another 5-10 min to load any libraries as well as the TV Guide. Everything is just incredibly slow, or never loads at all. However some times it loads almost instantly, but this seems to be rare. Actually playing media, LiveTV, Movies, Shows, Music, is fast, no problems there at all, no buffering, no stuttering, and silky smooth. My libraries are tiny in comparison to the amount of movies many other users have on these forums, I talking maybe 100 movies IF THAT. The only plugins I am using are the Cover Art, and Collections plugin, but I was having this issue before installing them too. I have attached the two most recent logs. server-63639216000.txt server-63639262214.txt
  11. Note that there's a lot of steps to this, but individually none are particularly difficult... I'm not a linux or bsd expert by any means, in fact I'd consider myself a complete amateur. I just pieced this all together from guides I read online, none of this is really my own, I'm just compiling it all in one place. I'm a newb myself so I wrote this as newb-friendly as possible... not to insult anyone's intelligence, just to reach the largest audience possible. That said, docker for freenas has been getting a lot of attention since corral, and while I never migrated to corral, everyone seemed to rave about docker so I really wanted to give it a shot. It's now possible on freenas 11.0, thanks to native VM support. So here i'll explain step-by-step how I got an emby docker container running on ubuntu server VM in freenas. At the end you'll have emby server running in a docker container on a Ubuntu Server VM, with everything set to auto-start on reboot. Set up Docker for Ubuntu Server Note: I installed this on an Ubuntu Server 16.04 VM directly from the Freenas 11 GUI. PreReqs: freenas 11.0-U2 (may work on other 11.0 versions but it's confirmed working on this version for me) Ubuntu Server 16.04 ISO x64 vnc viewer (optional but highly recommended) - dedicated ssh app - i like secureCRT First Step - Create the Ubuntu VM Inside the freenas GUI: Go to VM tab, and create a new VM. Create VM name, and give it a good amount of resources, since this will be your container manager. Based on the specs of my server (xeon 1220v3 w/ 32GB RAM), I gave my VM 4 CPUs and 12GB of RAM. Once VM is created, before you start it, go to devices tab, add CDROM, and point it to Ubuntu Server 16.04 iso image (it's free, just grab it from wherever) Also add a disk, must have zvol to tie to. If no zvol, create a zvol with sufficient size. Mine was 80GB. I won't show how to set up a zvol here, but just search for it, it's a simple process Now you can start the VM and connect initially via vnc viewer to the port specified on the VM details. It should boot to the ubuntu cdrom and start the installation process. Install Ubuntu with basic settings. No GUI, no extra features. Just keep it bare bones to keep it lightweight as possible. It will come up with an option to use UEFI boot. Choose that option as that will allow you to auto-start the VM via the freenas GUI. UEFI Boot Fix One annoying thing is that the freenas VM system will not boot to uefi automatically. There's an extra step you need to follow to fix this. https://forums.freenas.org/index.php?threads/how-to-how-to-boot-linux-vms-using-uefi.54039/ Summarizing steps from that guide, if you have shutdown your VM already and try to reboot it (which was my case), it will not automatically start the VM. Instead it will boot to shell. To eliminate this - Just type exit at the shell prompt, and in the EFI menu system navigate to "Boot Maintenance Manager" and then select "Boot from file" to locate and select your grubx64.efi file. Once the VM is started, log in as root. sudo -i As root, cd to the /boot/efi/EFI directory of your VM in order to create the new BOOT directory and copy the existing grubx64.efi to /EFI/BOOT/bootx64.efi. mkdir /boot/efi/EFI/BOOT cp /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/BOOT mv /boot/efi/EFI/BOOT/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi The end result should look like this, using Ubuntu as an example: root@ubuntu-vm:/boot/efi# tree -L 3 . . └── EFI ├── BOOT │ └── bootx64.efi └── ubuntu ├── fbx64.efi ├── grub.cfg ├── grubx64.efi ├── mmx64.efi └── shimx64.efi 3 directories, 6 files root@ubuntu-vm:/boot/efi# The file bootx64.efi is a copy of the grubx64.efi in your VM. NB: If grubx64.efi gets updated you will need to re-create bootx64.efi Restart the VM from the freenas GUI, and see if it boots directly to VM. Now your ubuntu VM should be up and running, and it will auto-start on reboots. As soon as I got Ubuntu up and running, I made sure to enable ssh access. Set Up SSH Access (Optional but Reccomended) sudo apt-get install openssh-server Now you can access the VM via ssh (I like secureCRT) instead of relying on vnc viewer. Also, make sure to mount NAS folder to give NAS access to your VM - Install cifs-utils apt-get install cifs-utils Create the directory and mount the device using the following commands (I named my mount point "freenas". Name it whatever you want). sudo mkdir /mnt/freenas Now mount the device using cifs mount -t cifs //192.168.0.155/nas -o username=anonymous,password=,rw,nounix,iocharset=utf8,file_mode=0644,dir_mode=0755 /mnt/freenas Change the ip address and folders to match the path to your particular NAS setup. My nas is setup for anonymous access internally. You might want to be more secure if you have multiple users, so change those settings as you see fit. sudo df -Th /mnt/freenas/ Test the directory and make sure your VM now has access to your freenas files. Once tested, you'll wan to make permanent so it persists on reboot. edit /etc/fstab and append - //192.168.0.155/nas /mnt/freenas cifs username=anonymous,password=,rw,nounix,iocharset=utf8,file_mode=0755,dir_mode=0755 Again, change the path and options as it matches your particular setup. Test that all this is working by stopping your VM, restarting it, and making sure that your NAS is still accessible via your mount point. Now you're ready to actually install docker. Installing Dockertaken from here https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04 The Docker installation package available in the official Ubuntu 16.04 repository may not be the latest version. To get the latest and greatest version, install Docker from the official Docker repository. This section shows you how to do just that. First, add the GPG key for the official Docker repository to the system: curl -fsSLhttps://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - Add the Docker repository to APT sources: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu/ $(lsb_release -cs) stable" Next, update the package database with the Docker packages from the newly added repo: sudo apt-get update Make sure you are about to install from the Docker repo instead of the default Ubuntu 16.04 repo: apt-cache policy docker-ce You should see output similar to the follow: Output of apt-cache policy docker-ce docker-ce: Installed: (none) Candidate: 17.03.1~ce-0~ubuntu-xenial Version table: 17.03.1~ce-0~ubuntu-xenial 500 500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages 17.03.0~ce-0~ubuntu-xenial 500 500 https://download.docker.com/linux/ubuntu xenial/stable amd64 Packages Notice that docker-ce is not installed, but the candidate for installation is from the Docker repository for Ubuntu 16.04. The docker-ce version number might be different. Finally, install Docker: sudo apt-get install -y docker-ce Docker should now be installed, the daemon started, and the process enabled to start on boot. Check that it's running: sudo systemctl status docker The output should be similar to the following, showing that the service is active and running: ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2016-05-01 06:53:52 CDT; 1 weeks 3 days ago Docs: https://docs.docker.com Main PID: 749 (docker) Installing Docker now gives you not just the Docker service (daemon) but also the docker command line utility, or the Docker client. All we need for now. Install and Set Up Portainer (Optional but recommended)taken from here https://www.ostechnix.com/portainer-an-easiest-way-to-manage-docker/ sudo docker pull portainer/portainer Let us check whether the Portainer image has been pulled or not. sudo docker images Sample output: portainer/portainer latest ec91653336d4 7 days ago 9.132 MB As you see in the above output, Portainer image size is less than 10 MB, which is very small so that I won’t consume more RAM and Hdd space. We have now Portainer in our local Ubuntu system. Let us start the container using command (this command allows portainer to be persistent on restart): docker run -d -p 9000:9000 --restart always --name portainer -v /opt/portainer-data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer Now, Portainer is running! Let us go ahead and access the Portainer UI. To do so, open your wbe browser and point it to – http://localhost:9000/ or http://IP_Address:9000/.You will be presented with a screen like below that asks to setup a password for the admin user. Enter the password twice and hit Validate button to create the admin user password. Finally - Add Emby Docker ImageTaken from here - https://hub.docker.com/r/emby/embyserver/builds/b7pzevchadukrbdutjzkjtz/ We recommend you install directly from the Docker Hub. Before starting the install procedure please verify the following prerequisites are fulfilled: ensure the user running installation command can run dockerStart the installation by issuing the following command from within a terminal (restart always & define port will make persistent on restart): docker run -it --rm -v /usr/local/bin:/target emby/embyserver instl Set Up Embyrun the emby-server command emby-server It will ask you to add volume locations. Use the mounted freenas directory to give access to NAS (or whatever folder you set up to mount with your NAS) /mnt/freenas That's it for the cli portion of emby set-up. Just ctrl+D to exit. Now, go into portainer, check images. You should see emby server. Click the link hyperlink. Look for the expose detail. Use one of the available tcp ports. For me, it was tcp port 8096. Now just enter the url of the docker VM with the correct port number: That should go directly to the emby set up screen. You're done! But one last thing before we finish... Enable Systemd Emby (Optional - allows emby-server to auto-start with docker VM)By deafult, containers don't auto-start on reboot. If you want this to happen, which is extremely convenient, you need to give it an appropriate run command. There's several ways to do this with docker, but in Ubuntu, systemd seems to be the recommended way to go. This is probably the most complex part of this tutorial, since the contents of your custom unit will vary depending on your personal setup. Use mine as a general guide and tweak as needed. On some emby docker tutorials, there are one-line commands that get emby-server to get included in systemd, but I couldn't get any of them to work for me for some reason, so I had to set up my own systemd service to make it work. I installed an app called systemd-docker for docker auto starts. Found it in a suggestion in the emby docker thread and it worked for me. apt-get install systemd-docker Then create the unit emby-docker.service file that goes into /etc/systemd/system/ things to note on the switches used in the "ExecStart" section - -v = volume -e = environment variable A good tip is to go into Portainer, look at the emby-server container you set up earlier, and look at the details of the container to get the settings of your ENV and volume sections. Then use the switches as shown in my example to configure your unit to match your personal setup. Some other tips - For my set-up, my volume referred to my mount point of my NAS. Change that to match what yours is. I run my emby container as root user. I have no problem with this. If you want to run it as some other user, you need to change the user as needed TZ = timezone. It's important to have that match your local timezone. Look up linux timezones and find one that matches yours. The rest I think you can keep the same and it shouldn't cause you many issues, but of course depends on your set-up. This took me a while to figure out and get right, and there may very well be easier ways to do this. Here's my sample emby-docker.service file. Make sure to give the file full rw permissions so it can be executed by systemd. [Unit] Description=Emby-Server Docker After=docker.service Requires=docker.service [Service] ExecStart=/usr/bin/systemd-docker run --rm --name %n --net=host -v /home/root/.emby-server:/config -v /mnt/freenas:/mnt/freenas -e APP_UID=0 -e APP_GID=0 -e APP_USER=root -e EDGE=0 -e UMASK=002 -e TZ='America/New_York' emby/embyserver Restart=always RestartSec=10s Type=notify NotifyAccess=all TimeoutStartSec=120 TimeoutStopSec=15 [Install] WantedBy=multi-user.target Enable it to make it persistent - sudo systemctl enable emby-docker Then start it sudo systemctl start emby-docker You should see the container running in portainer in your containers list, and you should be able to access your emby server on the default 8096 port. This time however, the container will always auto-start with your VM.
  12. Recently I noticed that my Realtime monitoring doesn't seem to be picking up newly added items. This used to work for me in the past and I don't think I have changed any paths or anything since moving to Docker. Is there anything I can try or check to debug this? The storage is on a NAS but there are shares mounted on the Linux system that point to them, and then Emby maps those paths and uses them in the media library settings.
  13. kentish

    Docker on OMV 3 - Library Access

    Hi I could do with some help on this as I'm confused. Installed Open Media Vault version 3 on my NAS, then installed the docker plugin and downloaded the Emby image and set up some shares to the media library. Emby starts fine, can scrap the media and the UI is super responsive however it won't play anything - tried via the web app / dlna and xbox one app - which is confusing as I've had all the working before and I believe I've set things up the same way and everything worked fine. Attached the docker and server logs. The server is using MergeFS with all libraries owned by root / user and set to 777, Docker is in Host mode with the /config folder sitting on a SSD again controlled by a OMV Share. I'm controlling the docker image via the OMV plugin UI Not sure what i'm missing. Hope some can shed some light on what I'm doing / have done wrong. Kentish DockerLog.txt EmbyServerLog.txt
  14. sebasmiles

    Subtitle download not respecting limits?

    So I have tried on and off to try to get subtitles download to work without success. I tried searching for the problem but the posts I found indicate that once it reaches the 200 limit on a non-VIP it should stop, however that never seems to happen to me. This has happened over several version (last time I tried was months back) including 3.2.19 which I have loaded right now. I clicked only on episode, then save, then went to tasks and hit the subtitle one to run. It proceeds to spam my activity log and balloons my log file into a massive 200mb file before I was able to stop it by hitting stop manually. Below is my subtitles.xml file (deleted my username and password), and the episode flag is back to false since I had to disable it. I am running Unraid, with the official Emby docker (or was labeled as such). <?xml version="1.0"?> <SubtitleOptions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipIfEmbeddedSubtitlesPresent>false</SkipIfEmbeddedSubtitlesPresent> <SkipIfAudioTrackMatches>false</SkipIfAudioTrackMatches> <DownloadLanguages> <string>eng</string> <string>spa</string> </DownloadLanguages> <DownloadMovieSubtitles>false</DownloadMovieSubtitles> <DownloadEpisodeSubtitles>false</DownloadEpisodeSubtitles> <OpenSubtitlesUsername>xxxxx</OpenSubtitlesUsername> <OpenSubtitlesPasswordHash>xxxx</OpenSubtitlesPasswordHash> <IsOpenSubtitleVipAccount>false</IsOpenSubtitleVipAccount> <RequirePerfectMatch>true</RequirePerfectMatch> </SubtitleOptions> This is the error where it shows rate limit, I got spammed by these until I was able to tell the scan to stop. 2017-06-21 18:46:34.4418 Error App: Error downloading subtitles *** Error Report *** Version: 3.2.19.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.4.30.0 64-Bit OS: True 64-Bit Process: True Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Fri Jun 2 05:04:04 UTC 2017) Processor count: 2 Program data path: /config Application directory: /usr/lib/emby-server/bin System.Exception: OpenSubtitles rate limit reached Logfile (its too large to attach): https://www.dropbox.com/s/1tjb09iobrr6wwt/server-63633599999.txt?dl=1
  15. Hello, I installed Emby server on my Raspberry PI 3 recently (Docker official method). It was a little difficult (linux noob inside ) but now all seems to be OK. But, i'm now trying to add a library, but there's a problem as i can't find any folder or share hosted / mounted on the RPi : (as you can see there's nothing but default paths) (network choice empty too) : How Emby detects disks and network shares ? Here is what i have and would want to choose : 1 usb hdd (ext4) + 1 network share (cifs) : If it must be set in Docker, how can i do it (and would it be kept if Emby image is updated ?) Thanks a lot for your assistance. Best regards,
  16. Hello Experts :-) I'm a beginner trying to install Emby server on my Raspberry PI 3 (OSMC 18b based on Debian). I followed the official method that use Docker : (Recommend install method for armhf/armv7 (Tested rpi2/3 running rasbian)) https://emby.media/community/index.php?/topic/43166-arm-devices-official-instructions/ I don't know Docker very well. It seems correctly installed and started : Ports 1900/udp, 8096/tcp, 7359/udp, 8920/tcp and opened in router for the IP address of the Raspberry PI 3 (192.168.0.20). I use other web interfaces / tools like Transmission, PhotoShow Albums, or Pyload (no Docker), that work perfectly fine. Since Docker installation, I have now 2 new network interfaces docker0 + veth***** : Plus, 2 new FS linked to docker (overlay + shm) : >> In the end : If i try to open Emby server URL on port 8096, it's not OK (i already tried to docker restart emby-server, or RPi reboot). Do i have to do something to link real RPi IP to docker0 or veth***** interface ? Did i miss something ? I'm lost :-\ Other details that may help (?) : . ps -ef . iptables -L . netstat -plnt (no Emby port displayed !) . find "emby" files : root@osmcpi:~# find / -name emby* /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/etc/emby-server.conf /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/etc/services.d/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/run/emby-server.pid /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/run/s6/services/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/usr/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/emby-server.conf /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/sudoers.d/emby /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/zypp/repos.d/emby.repo /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/default/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/services.d/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/var/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/run/emby-server.pid /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/run/s6/services/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/bin/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/emby-server.conf /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/sudoers.d/emby /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/zypp/repos.d/emby.repo /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/default/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/services.d/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/var/lib/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/bin/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/0747faf49edaaddb71ec938def66162a75c301c09b661328edf0a16346506797/diff/etc/services.d/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/emby-server.conf /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/sudoers.d/emby /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/default/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/var/lib/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/bin/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-connect /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-scroller /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-scroller/emby-scroller.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/089b42346baa4131c4073b6abcb30bfd1f434e7420964d84b2a013ff67b8ca12/diff/usr/lib/emby-server /usr/local/bin/emby-server . ps -ef | grep docker . ps -ef | grep emby Thanks a lot for your assistance. Best regards,
  17. Hi my Emby work on FreeNAS on Docker image I have two strange things: I only download stable version, but now I have 3.2.11.0 beta, and I don't know why My setup on Docker config is EDGE = 1 ( automatic updates ON ) and a not able to update to version 3.2.11.1 I try to restart my docker, I try to start update command on Docker console, but nothing happened ... Is somebody ready answer why? Thanks
  18. I was able to install and run a docker version in another mint 18, just a few days ago. Now I'm install and run the container, it says it's running, but I can not open in the browser. I also noticed that /usr/local/bin/emby-server changed compared to the other mint install. I'm kinda noob in Docker, so sorry if I did not post more info.
  19. vigilian

    problem streaming to chrome

    error in opening the video on chrome (remux) last chrome version and yandex doesn't appear with emby on ios apparently the coding of the video is in itunes but let's see the logs for that. joneses.txt
  20. Hey guys. When trying to build emby-server in a docker container, the following worked untill 3.0.8500: sudo apt-get install -y --no-install-recommends \ ca-certificates \ git \ libmono-system-core4.0-cil \ mono-devel \ mono-runtime \ mono-utils \ mono-xbuild \ wget cd $HOME \ && git clone --depth 1 https://github.com/MediaBrowser/Emby.git I then change to Tools/Linux_Build_Scripts/ and launch MediaBrowser.Mono.Build.sh But since 3.1.1 (I must have missed 3.1.0) I get: ... ======================================== Requirements ======================================== Check if folder mediabrowser exist Creating folder: mediabrowser ======================================== Nuget: Restoring packages ======================================== Restoring NuGet package MSBuild auto-detection: using msbuild version '4.0' from '/usr/lib/mono/4.5'. MsBuild.exe does not exist at '/usr/lib/mono/4.5/msbuild.exe'. Result is the same, no matter if I use a debian docker or ubuntu. What did I do wrong? Anything I am missing here?
  21. See the download page of our website: https://emby.media/download
  22. Ubuntu Server 16.04.1 SAMBA version 2: 4.3.11 Windows 10 client (Bash/Putty) Emby 3.0.8100.0 Docker 1.12.2 "Movies" folder has been added to Emby library but cannot get access from Windows client. "Test" folder Emby cannot locate but I have access from Windows client What I've tried so far... 1. Matching workgroups between ubuntu server and windows client 2. Added automount into fstab 3. Turned off smb2/3 on windows client 4. Created a SAMBA user to match the user logged in on Windows client What I haven't tried... 1. Matching folder/file perms to emby user/group >> default emby user and emby group was not found and I have no idea where to look within docker to get the emby config for users and groups ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- $ ls -l /media/Movies -rwxrwxrwx 1 windowsuser docker 28089 Oct 14 12:14 Warcraft.2016.1080p.BluRay.x264.AC3-BUYMORE-Obfuscated.nfo $ ls -l /samba/Test -rwxr--r-- 1 nobody nogroup 3191 Oct 14 03:11 sambaPerm.txt ---------------------------------------------------------------------------------------------------------------------------------- smb.conf [global] workgroup = WORKGROUP server string = Samba Server %v netbios name = ubuntu disable netbios = yes smb ports = 445 security = user map to guest = bad user dns proxy = no passdb backend = smbpasswd preferred master = yes printing = cups printcap name = cups printcap cache time = 750 cups options = raw usershare allow guests = Yes usershare max shares = 100 usershare owner only = false wins support = no name resolve order = bcast host lmhosts #============================ Share Definitions ============================== [Test] path = /samba/test browsable =yes writable = yes guest ok = yes read only = no force user = nobody [Movies] comment = Movies and videos for kids path = /media/Movies browseable = yes writable = yes read only = no guest ok = yes available = yes valid users = windowsuser,windowsuser2 public = yes
  23. Setup: Ubuntu Server 16.04 Docker 1.12.2 Windows 10 client (Putty) I'm a Linux/Docker newbie. I ping'd my server from Windows to get the internal server IP. http://[ubuntu server internal IP]:8096 http://[ubuntu server internal IP]:8920 Both requests resulted with 'refused to connect' by Chrome. Does my emby server have a different IP from the Ubuntu server since it lives within a docker container? Is there some firewall on the ubuntu server that I need to turn off? If so how? Do I need to complete emby setup via CLI on the server before I can hit it remotely? Thanks, Linh
  24. walnuss0815

    Probleme mit DLNA unter Docker

    Hallo zusammen Bis gestern hatte ich auf meiner DiskStation Emby als Paket laufen. Diese Lösung gefiel mir nicht, da weitere Pakete benötigt werden. Nun bin ich gestern auf die Idee gekommen den Emby-Server in Docker laufen zu lassen. Die Einrichtung verlief Problemlos, jedoch habe ich per DLNA keinen Zugriff auf den Emby-Server. Außerdem kann die Verbindung mit dem Emby-Server über die Seite app.meby.media nicht hergestellt werden (Fehlermeldung siehe Anhang). Folgende Ports des Docker Containers sind freigegeben: 1900 UDP 1901 UDP 7359 UDP 8096 TCP 8920 TCP Alle weiteren Einstellungen sind bitte dem Anhang zu entnehmen. Der Zugriff auf den DLNA Server soll per Windows Media Player erfolgen, was mit dem Emby-Server als Paket Problemlos funktionierte. Folgende Einträge aus dem Log (im Anhang) irritieren mich: 2016-08-30 11:44:11.3236 Info IDeviceDiscovery: Creating SSDP listener on 127.0.0.12016-08-30 11:44:11.3309 Info IDeviceDiscovery: Creating SSDP listener on 172.17.0.8 Es scheint so als würde der Server nur auf dem Loopback-Interface "hören".... Ich hoffe auf eure Hilfe! PS: Das Emby Paket nutzt wenn es läuft folgende Ports tcp 0 0 0.0.0.0:8920 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8096 0.0.0.0:* LISTEN udp 0 0 192.168.0.242:49974 0.0.0.0:* udp 0 0 127.0.0.1:60388 0.0.0.0:* udp 0 0 0.0.0.0:7359 0.0.0.0:* udp 0 0 192.168.0.242:42701 0.0.0.0:* udp 0 0 192.168.0.242:1900 0.0.0.0:* udp 0 0 127.0.0.1:1900 0.0.0.0:* udp 0 0 172.17.42.1:1900 0.0.0.0:* udp 0 0 0.0.0.0:1900 0.0.0.0:* udp 0 0 0.0.0.0:1901 0.0.0.0:* udp 0 0 172.17.42.1:47061 0.0.0.0:* udp 0 0 127.0.0.1:53224 0.0.0.0:* Zum testen werde ich sie in Docker durchgeben. Mit freundlichem Gruß walnuss0815 Server_Log.txt
  25. Hello, trying to see if anyone else has attempted something similar or if there is another better method. Since emby supports path substitution, is it possible to setup a cron/task to create the show names using something like mythlink.pl that are zero-byte in size to a directory Emby can use and then use path substitution to point to the real file. The problem I see is that emby will still look for the name of the zero-byte file created when doing path substitution. If it is possible to trim off part of it (the real show name) and leave the remainder the numeric name mythtv creates the file as then it should work. This part however would need a bit of emby support to do. e.g.: Mythtv records a show (call it Survivor): 1091_2015032302010.mpg (located in /var/mythtv/recordings) cron job runs creating the following in /storage/RecordedTV/Survivor_1091_2015032302010.mpg zero-byte file (i.e. empty file with .mpg extension) (Hopefully emby can organize by the name now) Using emby's path substitution, selecting /storage/RecordedTV/Survivor_1091_2015032302010.mpg would play /var/mythtv/recordings/1091_2015032302010.mpg after removing the name part (Survivor_) Is there anyway something can be done to do this? Thank you.
×
×
  • Create New...