Search the Community

NGINX and emby Config Version 1.0.4 Last Update 1-1-2024 Update by Pir8Radio Why Use NGINX reverse proxy ahead of my application servers like emby? With NGINX or any reverse proxy ahead of an application server you have more control over your setup. You can do things the application servers were not built to handle, have better control over your security and logging, replace lines of code without editing the application server code, better control of caching, etc, etc.... One of the main reasons is so that you don't have to open a new port on your firewall for every application server you host, all you really need to open is 80 & 443 and the internet can reach all of your different servers through one entrance. Will NGINX work on my OS? Most likely, you can find various versions of NGINX for most OS's and they come in different flavors, with options baked in, or just the bare NGINX that you need to compile. See below for download links to get you started. Will NGINX break things on emby? Absolutely if you don't configure it correctly! I HIGHLY suggest when choosing a scheme to setup your domain URL you choose SUB-DOMAIN and NOT sub-directory, more below. Also if you come to the emby forum with things not working, or issues you have and you use a Reverse Proxy, PLEASE make sure that is one of the first things you mention in your forum post. ESPECIALLY if emby works on one platform or client, but not another. So many times people complain "but it works on chrome, so I didn't think it was the reverse proxy". Mention you have a Reverse Proxy please. If the reverse proxy is setup correctly it should be totally transparent to the user and the application server (emby). I'm not going to go into how to purchase and setup a domain name. Lots of how-to's on that out there. Once you have a domain name and its pointed to your IP address, you can go to that domain name and hit your server then continue on.... Sub-Domain vs Sub-Directory: Lets say your domain name is: domain.com there are two main ways you can direct traffic from the internet to your backend application servers like emby. One is sub-directory, something like domain.com/emby or domain.com/other-server This is doable in nginx, but there are some catches and you need to know how your reverse proxy and application server work in detail.. This often breaks different features in emby and other application servers.. To keep with our "Totally Transparent" goal sub-directory doesn't work well, it requires a lot of rewriting and work-arounds to make it work smoothly, if you choose sub-directory you will run into issues you will need to address. The other option is Sub-Domain, this is the cleanest, most transparent, easiest to setup and maintain, it's also what I highly suggest you setup. A sub-domain looks like: emby.domain.com or other-server.domain.com The below config is based on Sub-Domain I will include a sub-directory example as well. NGINX Downloads: Official nginx downloads(LINUX): nginx.org Official nginx downloads(Windows): nginx.org WINDOWS users I suggest this version: nginx-win.ecsds.eu download links are at the bottom of the page. This Windows version has lots of cool features compiled into it already, and is optimized for windows. They keep up with updates, its a FREE (for non-commercial) third party build that I highly recommend. Additional Links: Content Security Policy info (CSP) (For Advanced Users): A CSP WILL break your server if you don't know what you are doing, I suggest reading up, lots of googleing, and understand what a CSP's function is and is not prior to venturing into this area Example NGINX Reverse Proxy Config: 3-29-2020 - ADDED A LINE FOR CLOUDFLARE USERS SO THAT THE X-REAL-IP HEADER IS CORRECTED. THIS ONLY EFFECTS Cloudflare USERS. 4-11-2020 (V1.0.1) - MOVED proxy_buffering off; FROM LOCATION BLOCK TO SERVER BLOCK 12-18-2020 (V1.0.2) - ADDED 301 SERVER SECTION TO FORCE ALL TRAFFIC TO SSL. 9-23-2021 no nginx config change, but cloudflare changed how they cache video files, so emby users that use Cloudflare now need to add a rule like below to make sure video is seekable and playable. 8-18-2022 - added a line for photo sync to cover large uploads of videos and images. (client_max_body_size 1000M;) 1-1-2024 - changed http2 setting per @weblesuggestion in this thread post # 1309363. ** The below "Page Rules" are only needed for Cloudflare CDN users, otherwise ignore. worker_processes auto; error_log logs/error.log; events { worker_connections 8192; } http { include mime.types; default_type application/octet-stream; server_names_hash_bucket_size 64; server_tokens off; ## The below will create a separate log file for your emby server which includes ## userId's and other emby specific info, handy for external log viewers. ## Cloudflare users will want to swap $remote_addr in first line below to $http_CF_Connecting_IP ## to log the real client IP address log_format emby '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port "$http_x_emby_authorization"'; log_format default '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port'; sendfile off; ## Sendfile not used in a proxy environment. gzip on; ## Compresses the content to the client, speeds up client browsing. 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; proxy_connect_timeout 1h; proxy_send_timeout 1h; proxy_read_timeout 1h; tcp_nodelay on; ## Sends data as fast as it can not buffering large chunks, saves about 200ms per request. ## The below will force all nginx traffic to SSL, make sure all other server blocks only listen on 443 server { listen 80 default_server; server_name _; return 301 https://$host$request_uri; } ## Start of actual server blocks server { listen [::]:443 ssl; ## Listens on port 443 IPv6 ssl enabled listen 443 ssl; ## Listens on port 443 IPv4 ssl enabled http2 on; ## Enables HTTP2 proxy_buffering off; ## Sends data as fast as it can not buffering large chunks. server_name emby.domainname.com; ## enter your service name and domain name here example emby.domainname.com access_log logs/emby.log emby; ## Creates a log file with this name and the log info above. ## SSL SETTINGS ## ssl_session_timeout 30m; ssl_protocols TLSv1.2 TLSv1.1 TLSv1; ssl_certificate ssl/pub.pem; ## Location of your public PEM file. ssl_certificate_key ssl/pvt.pem; ## Location of your private PEM file. ssl_session_cache shared:SSL:10m; location ^~ /swagger { ## Disables access to swagger interface return 404; } location / { proxy_pass http://127.0.0.1:8096; ## Enter the IP and port of the backend emby server here. client_max_body_size 1000M; ## Allows for mobile device large photo uploads. proxy_hide_header X-Powered-By; ## Hides nginx server version from bad guys. proxy_set_header Range $http_range; ## Allows specific chunks of a file to be requested. proxy_set_header If-Range $http_if_range; ## Allows specific chunks of a file to be requested. proxy_set_header X-Real-IP $remote_addr; ## Passes the real client IP to the backend server. #proxy_set_header X-Real-IP $http_CF_Connecting_IP; ## if you use cloudflare un-comment this line and comment out above line. proxy_set_header Host $host; ## Passes the requested domain name to the backend server. proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; ## Adds forwarded IP to the list of IPs that were forwarded to the backend server. ## ADDITIONAL SECURITY SETTINGS ## ## Optional settings to improve security ## ## add these after you have completed your testing and ssl setup ## ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ## ## See https://hstspreload.org/ read through the "Deployment Recommendations" section first! ## add_header 'Referrer-Policy' 'origin-when-cross-origin'; add_header Strict-Transport-Security "max-age=15552000; preload" always; add_header X-Frame-Options "SAMEORIGIN" always; add_header X-Content-Type-Options "nosniff" always; add_header X-XSS-Protection "1; mode=block" always; ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client. proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; } } }

Hi there running into a bit of a weird issue with emby connect. I have emby running in a container on one of my VM's. I access it via my traefik reverse proxy pointing at 10.20.66.243:8096. It gets a SSL using a LetsEncypt wild card cert pointed at my cloudflare domain. I do not have emby exposed publicly yet as I am still trying to figure out the best way to go about this. My setup works perfectly fine with the exception being emby connect. I have added emby connect to my main admin account. The problem seems to be when i sign in it does not auto add my server like it should. I have read through the docs but I don't understand what I am doing wrong. My emby server is accessible via the information shown in the emby dashboard. I can manually add the server but this defeats the purpose of using connect. Is there a setting on my emby connect account that needs to be changed? LAN networks Local IP address: 10.20.66.243 Local http port number: 8096 Local https port number: 443 Allow remote connections to this Emby Server: Yes Remote IP address filter: blank Remote IP address filter mode: whitelist Public http port number: 8096 Public https port number: 443 External domain: emby.mydomain.com Read proxy headers to determine client IP addresses: yes Custom ssl certificate path: blank Secure connection mode: Handled by reverse proxy Enable automatic port mapping: yes Max simultaneous video streams: Unlimited Internet streaming bitrate limit (Mbps): blank 2024-10-05 19:40:00.177 Warn Server: AUTH-ERROR: 10.20.66.243 - Access token is invalid or expired. 2024-10-05 19:40:00.177 Error Server: Access token is invalid or expired. 2024-10-05 19:40:00.177 Info Server: http/1.1 Response 401 to host2. Time: 1ms. GET http://emby_remote_ip/Users/850d6b7da5c647c4bfac2e41b51355b9/Items/Latest?Limit=12&ParentId=3 2024-10-05 19:41:50.275 Info Server: http/1.1 GET http://host2:8096/emby/Auth/Keys?IncludeItemTypes=ApiKey&Fields=BasicSyncInfo,CanDelete,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating,DateCreated&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=0c2b2b73-4323-49d3-bddf-c69d742f43fc&X-Emby-Client-Version=4.8.8.82&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us. Source Ip: host1, Accept=application/json, Connection=keep-alive, Host=host3, User-Agent=Mozilla/5.0 (Windows NT 10.0; rv:130.0) Gecko/20100101 Firefox/130.0, Accept-Encoding=gzip, deflate, Accept-Language=en-US,en;q=0.5, Origin=host4, DNT=1, Sec-GPC=1, Priority=u=4 2024-10-05 19:41:50.285 Info Server: http/1.1 Response 200 to host1. Time: 10ms. GET http://host2:8096/emby/Auth/Keys?IncludeItemTypes=ApiKey&Fields=BasicSyncInfo,CanDelete,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating,DateCreated&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=0c2b2b73-4323-49d3-bddf-c69d742f43fc&X-Emby-Client-Version=4.8.8.82&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us

因为网络原因，我无法直接访问到 元数据 的服务器，Auto Organize之类的插件因此失效，希望能给元数据搜刮提供 HTTP/SOCKS 代理功能。 谢谢 embyserver.txt

Hola, qué tal? Quería pedirles ayuda, por favor. Tengo el servidor Emby instalado en un NAS Asustor, y no puedo conectarme de forma remota desde Smart TV (por medio de navegador web, no tuve problemas). Como decía, tengo Emby instalado en un NAS Asustor, el cual me configura por defecto un proxy inverso (en una aplicación del propio NAS, no modifica la configuración del servidor Emby). Dicho proxy inverso está configurado con un puerto externo con protocolo https y el puerto interno por defecto -http- de Emby. Luego el router tiene abierto el puerto asignado por el proxy, con el protocolo https. Por otro lado, para evitar el problema de IP variable del ISP, tengo configurado en el router el servicio de ddns de No-IP. Conectándome desde navegador web, no tengo inconvenientes para ingresar al servidor Emby, pero desde Smart TV no se conecta: "No es posible conectarse al servidor seleccionado en este momento. Por favor asegúrese de que se encuentre en ejecución e inténtelo nuevamente." Alguien sabe cuál puede ser el problema? Muchas gracias!

I using the emby server in docker env. in my region (CN) access other network is diffuclt somes like the Cloudflare Workers ,my strm file resource is pass the CF network.In that, i have to use the proxy. for the network setting , set the proxy. - 'HTTP_PROXY=http://127.0.0.1:7890' - 'HTTPS_PROXY=http://127.0.0.1:7890' the ffprobe don't use the env variable，must add the argc like -http_proxy http://127.0.0.1:7890 i test in my windows terminal add the argc the cmd work good.So i wanna help devoloper can take some if addition, if env.http_proxy : cmd take the -http_proxy http://127.0.0.1:7890 additionally. If that's the case, I'd be incredibly grateful. server.log

I think I already know the answer but I just wanted to check in case I missed it. But is there any proxy setting for the EMBY server itself? I need to use a SOCKs proxy for IPTV traffic but don't want to set the proxy on host OS (windows 11) as I don't want all network traffic going over that proxy, I just want the IPTV traffic from EMBY.

@pir8radio @pwhodges thanks for trying to help me I have converted Let’s Encrypt to work with emby directly without using Nginx Cer add to emby setting surf to my server and now working without any warning from the browser about the Certificate .. and the video payed as well. ok now when I try with the emby app, the video still give me an error. So it is not related with Nginx ... there is an issue with the app itself @Luke this issue only I have with Galaxy Note 5 The device is Galaxy Note 5 Android 7.0 emby 3.2.56 Server emby 4.7.5.0 (Ubuntu Linux 20.04.4) log file is attached please note that I have replace my domain name and IP to my_domain.com and my_ip on the log file Many Thanks embyserver.txt

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

Hi, I have a native installation of Emby on Ubuntu 18.04 server My problem is that the machine has no direct access to the Internet. Usually this problem can be solved by "export http_proxy=..." either in console or "/etc/environment". Unfortunately Emby doesn't use this environment variable and therefore I can't download any metadata or subtitles... I haven't found any setting nighter in GUI Dashboard or "/var/lib/emby/config/system.xml" (I think <IsBehindProxy>true</IsBehindProxy> means is behind reverse proxy) but I think the trick is changing "MONO_ENV" in "/etc/emby-server.conf". Can anybody help me with this please?

Continuing with this topic, I want to share my current working Apache reverse proxy setup. Before Nginx users kill me, let me say that I prefer Apache because i'm used to it (I know Nginx is better in reverse proxy scenarios), I find it simpler, I have a Nextcloud server running in the same machine and here they recommend using Apache instead of Nginx, even if i'm not using it for an enterprise deployment. At the moment, i'm having 0 issues with any App (Web, TV, Android, iOs, etc.), the chrome console is clean without any error when connecting through the Web App. My apache is redirecting all traffic including the websocket traffic. I use my server with a CNAME of my domain, so that's why I don't locate it in "/emby" location, I do it in "/". This is my apache .conf file for Emby reverse proxy (located at /etc/apache2/sites-available): <IfModule mod_ssl.c> <VirtualHost *:80> ServerName cname.domain.com ServerAdmin youremail@address.com RewriteEngine on RewriteCond %{SERVER_NAME} =cname.domain.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent] </VirtualHost> <VirtualHost *:443> ServerName cname.domain.com ServerAdmin youremail@address.com <proxy *> AddDefaultCharset off Order Allow,Deny Allow from all </proxy> ProxyRequests Off ProxyPreserveHost On ProxyPass "/embywebsocket" "ws://127.0.0.1:8096/embywebsocket" ProxyPassReverse "/embywebsocket" "ws://127.0.0.1:8096/embywebsocket" ProxyPass "/" "http://127.0.0.1:8096/" ProxyPassReverse "/" "http://127.0.0.1:8096/" SSLCertificateFile /etc/letsencrypt/live/cname.domain.com/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/cname.domain.com/privkey.pem Include /etc/letsencrypt/options-ssl-apache.conf </VirtualHost> </IfModule> As you can see I'm using Let's Encrypt certificates. As @@curtisghanson said here, I also have an "A" in Qualy SSL Labs: Well I was scared of the performance but It's true that the maximum concurrent users I have are around 5-20, it's little. This is the server usage when 7 users are connected playing content at the same time (all my content is Direct Played): And that's all, hope you liked it and find it useful! Any improvement to the Apache conf file is welcome. Edit: Forgot to say thanks to @@fc7 who was the man that did all this possible .

I just got a new router, which means my server has moved from local IP 10.0.x.x to 192.168.x.x. I added exactly the same port-forwarding rules to the new router that I had in the old router, changed the local IP address in the NGINX config, restarted NGINX and...it doesn't connect. The domain gets a CloudFlare 524 error. My IP address followed by ports 80, 443, 4343, 8920 and 7241 fails. My IP address followed by port 8096 succeeds. This doesn't make any sense. I have Emby's ports in the network config set to 4343 for secure and 7241 for non-secure. CanYouSeeMe.org can only see me on port 8096. NGINX isn't jumping in front of any of the attempts at direct-IP access, which from memory it's supposed to.

Hi there, I've installed Emby server on my QNAP TS-231P2, it worked well. However, recently due to the internet blockage, when Emby tried to pull metadata from TMDB, it always got a time-out. So I'm thinking of using a proxy to solve the problem. Unfortunately, I didn't find any HTTP proxy settings in Emby control panel. Therefore I decided to install shadowsocks and privoxy to turn Socks5 proxy into a HTTP one. Too bad the privoxy rules just didn't work. Even after I added HTTP_proxy and HTTPS_proxy into the environment variables, and the command like curl or wget worked fine for api.themoviedb.org, the traffic from Emby seemed not to pass through the proxy and got time-out again. I wonder if there is any other means to solve the problem, either from a system level or software level. Also, I'd like to know if you are adding proxy settings in the future versions of Emby. Thanks for your help in advance. Any suggestions are welcome. A piece of log is attached to show the typical situation. 2020-04-20 19:58:13.506 Info HttpClient: GET https://api.themoviedb.org/3/movie/342588?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=casts,releases,images,keywords,trailers&language=zh-CN&include_image_language=zh-CN,zh,null,en 2020-04-20 19:58:33.521 Error HttpClient: Connection to https://api.themoviedb.org/3/movie/342588?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=casts,releases,images,keywords,trailers&language=zh-CN&include_image_language=zh-CN,zh,null,en timed out 2020-04-20 19:58:33.590 Error ProviderManager: Error searching *** Error Report *** Version: 4.3.1.0 Command line: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll -programdata /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA -updatepackage emby-server-qnap_{version}_arm-x41.qpkg -noautorunwebapp Operating system: Unix 4.2.8.0 64-Bit OS: False 64-Bit Process: False User Interactive: True Runtime: file:///share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Program data path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata Application directory: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://api.themoviedb.org/3/movie/342588?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=casts,releases,images,keywords,trailers&language=zh-CN&include_image_language=zh-CN,zh,null,en timed out ---> System.OperationCanceledException: The operation was canceled. at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts) at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) --- End of inner exception stack trace --- at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at MovieDb.MovieDbProvider.GetMovieDbResponse(HttpRequestOptions options) at MovieDb.MovieDbProvider.FetchMainResult(String id, Boolean isTmdbId, String language, String country, CancellationToken cancellationToken) at MovieDb.MovieDbProvider.DownloadMovieInfo(String id, String preferredMetadataLanguage, String preferredMetadataCountry, CancellationToken cancellationToken) at MovieDb.MovieDbProvider.GetMovieSearchResults(ItemLookupInfo searchInfo, CancellationToken cancellationToken) at MediaBrowser.Providers.Manager.ProviderManager.GetSearchResults[TLookupType](IRemoteSearchProvider`1 provider, TLookupType searchInfo, CancellationToken cancellationToken) at MediaBrowser.Providers.Manager.ProviderManager.GetRemoteSearchResults[TItemType,TLookupType](RemoteSearchQuery`1 searchInfo, BaseItem referenceItem, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.OperationCanceledException: The operation was canceled. Source: System.Net.Http TargetSite: Void HandleFinishSendAsyncError(System.Exception, System.Threading.CancellationTokenSource) at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts) at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)

Hello, I was able to successfully configure windows IIS as a reverse proxy using URL re-write and AAR. I also enabled SSL offloading so I can put my Let's Encrypt cert in IIS and manage it through there as well as control the level of SSL Ciphers that IIS can use. Emby comes up perfectly and works.. Right up until you click play on a movie. The playback seems to take forever to load, it eventually does but then another issue comes up. The CPU on the server jumps to 99% and it never stops. From what I can tell of the logs it is doing a Remux of the file and then playing it which is causing the CPU to run hot. I was playing "The Fifth Element" as a test and when I viewed the stats for nerds it states that the "media bitrate exceeds limit" which I find odd as the movies overall bitrate is just 12/Mb. As a test I then disabled the reverse proxy and used the built in emby way of encrypting the server. I passed the .pfx12 file and its password and changed the port to 443 and did another test with the same movie and it played perfectly. It loaded instantly and the CPU stayed at around 1% usage. Could it be the SSL offloading that is causing this ? Could it be IIS itself ? Is there specific things I need to change within IIS in order for this to work correctly ? Has anyone here been able to successfully get an IIS reverse proxy with SSL offloading to work with emby ? Let me know Thank You

I have had a few people ask me to explain how I set up my Apache server to forward to my Emby server. Here is a breakdown of how mine is set up should anyone else wish to try this. This is just my way of doing this (yeah, I know, Nginx exists but I have always been an Apache user). Note that I use RPM based distributions, and my frontend Apache server is running on Fedora Server Edition (so that I can have the http/2 goodness). My instructions will emphasize this type of Linux distribution, so you will need to read up on how your particular flavor of Linux handles Apache installations. First off, here is an overview of my network. Everyone's network is different, but this is what I have set up: edge firewall -> wireless ap/firewall -> apache server -> media server (where the media files are actually stored) On my firewalls, I only have ports 80 and 443 tcp opened up, and they forward to my Apache server. No other ports are exposed to the Internet. My Emby server is not configured with SSL. All SSL is terminated at my Apache server. This way, I can use one SSL certificate to encrypt any web services that I run on my network, without trying to get a certificate for each individual server installation. Anything that comes in on port 80 automatically gets forced over to port 443 (this is done by my Apache server itself). I am also using HTTP/2 which has helped with the various web services that my Apache frontend is exposing to the web. Also, all of my internal servers are running host-based firewalls. There is nothing wrong with security in depth here, and I have personally not heard a valid reason to not run a host-based firewall for your networking services. I use https://letsencrypt.org/ for my SSL certificate. It's free, and their tools are awesome. If you use their services, please donate to them as they are providing a valuable service to practically every community. I also have my own domain name set up and registered, with a dynamic IP from my ISP. There are a plethora of services that will let you register your dynamic IP for a domain name, so search around for the one that suits you best. Personally, I am using Google Domains for mine. My firewall assists in keeping my latest IP registered for my domain. This is extremely handy for mobile devices and family members who wish to use my Emby server remotely. Here are the general steps I would recommend to someone setting this up for themselves: Use an edge firewall. The extra protection is worth it. Use your edge firewall to keep track of your public IP, and use whatever agent that your dynamic DNS provider provides to keep your latest IP registered for your domain. I do not recommend doing this from your Apache server, as your Apache server should be further into your network and protected by your other firewall(s). Set up an SSL certificate for your domain. Again, LetsEncrypt is pretty awesome. Install Apache on a server that can handle a fair amount of network traffic. If you are using LetsEncrypt, set up the agent to keep up with your SSL certificate on this server. dnf groupinstall "Web Server" dnf install mod_http2 Configure your Apache server. On a Fedora, CentOS, RHEL system create a file called /etc/httpd/conf.d/00_yourdomain.conf (the two zeroes are there to make sure that your domain file is loaded first). Here are snippets of my configuration (cleaned up a bit for, you know, security): <VirtualHost *:80> Protocols h2c http/1.1 # Send everything over to https instead, best practice over mod_rewrite ServerName example.com Redirect / https://example.com/ </VirtualHost> <VirtualHost _default_:443> # Enable http/2 Protocols h2 http/1.1 <IfModule http2_module> LogLevel http2:info </IfModule> SSLEngine on SSLProtocol all -SSLv2 -SSLv3 SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:ECDHE-RSA-AES128-SHA:DH-RSA-AES128-GCM-SHA256:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4 SSLHonorCipherOrder On SSLCompression off Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains" Header always set X-Frame-Options SAMEORIGIN Header always set X-Content-Type-Options nosniff SSLCertificateFile /etc/letsencrypt/live/example.com/cert.pem SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem SSLCertificateChainFile /etc/letsencrypt/live/example.com/fullchain.pem <Files ~ "\.(cgi|shtml|phtml|php3?)$"> SSLOptions +StdEnvVars </Files> <Directory "/var/www/cgi-bin"> SSLOptions +StdEnvVars </Directory> BrowserMatch "MSIE [2-5]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 ServerName example.com ServerAlias example.com ErrorLog logs/example-error_log RewriteEngine on RewriteRule ^/emby(.*) http://127.0.0.1:8096/emby$1 [proxy] RewriteRule ^/emby http://127.0.0.1:8096 [proxy] RewriteRule ^/embywebsocket(.*) http://127.0.0.1:8096/embywebsocket$1 [proxy] RewriteRule ^/embywebsocket http://127.0.0.1:8096 [proxy] <location /emby> ProxyPass http://127.0.0.1:8096/ ProxyPassReverse http://127.0.0.1:8096/ </location> <location /embywebsocket> ProxyPass http://127.0.0.1:8096/ ProxyPassReverse http://127.0.0.1:8096/ </location> </VirtualHost> So what this does for me is let Apache handle all incoming port 80 requests, and turns them into encrypted traffic. All connections to and from the server (that can support it) are encapsulated in HTTP/2 packets. All of my SSL encrypted web traffic is handled by one certificate, so I can have multiple URL paths served by the same domain name, with only the https port used, and it just plain looks cleaner. For example, you can have: https://example.com/emby https://example.com/nextcloud https://example.com/hello_kitty_island_adventure Or whatever suits your needs. My Emby server doesn't have to worry about any proxy configurations or SSL, as Apache takes care of all of that. My example is using the localhost IP address to direct all incoming and outgoing Emby requests, but if you are using a separate host that runs Emby, just make sure to use the IP of that system instaed and that you have port 8096 open and available. I hope that others may find this helpful.

Last night I updated both Emby and mono to versions 3.1.0 and 4.6.2.7. Since then I'm not able to access Emby from the internet, through an Apache reverse proxy, anymore. I can access the webclient without any issues within the LAN but if I try the same from the internet via the proxy I get this: 0 0 HTTP/1.1 200 OK X-UA-Compatible: IE=Edge Access-Control-Allow-Headers: Content-Type, Authorization, Range, X-MediaBrowser-Token, X-Emby-Authorization Access-Control-Allow-Methods: GET, POST, PUT, DELETE, PATCH, OPTIONS Access-Control-Allow-Origin: * Vary: Accept-Encoding ETag: "4a131dd81c597e10d17c1a65ab8851f4" Cache-Control: public Content-Encoding: deflate Expires: -1 Server: Mono-HTTPAPI/1.1, UPnP/1.0 DLNADOC/1.50 Content-Type: text/html; charset=UTF-8 Date: Tue, 20 Dec 2016 17:41:38 GMT Content-Length: 789 VMs0WsR(=NYĢd$9iڂgKVU,\-I*9?phy*nlD$Uk?< HMyY@<Q~5bGBW5uRZ9P..!gR[JVOUA ZiSQsp*@B]jCRei]KgĎq)֥CF&4Ll~S"pNTt' 2n2 q1tE҂=aT$..x awJ^i)֏a6<s'|l 7O47F0i N*p̈ ZƐwCӨq#>sxfv:z7gGA!GtX0o\_ZaXt6&ɿkv>Ё'XiXT|f֦?{I@-XH{\My.6{Rr=C+BϦ3J%ݢR&ɧ8%P*F '*fS?KIv]$+4o0.6wݹc.*0ь׏#F7?p[0WTz(R "vB~Wr0"{} V}-:W>'h?YW[lzp{"bj}{ h݉r65N5~wb/V`Ǖcv- And that's all. Trying to refresh the page, it will keep loading forever. Before the upgrade I took a VM snapshot so I went ahead and roll back and everything went back to normal. I will provide the server log as soon as possible. Thanks.

Hi, I bought a Google mini to play around with, but I can't seem to get Emby to connect. The things I did: My server (v 4.2.0.40) is behind a reverse proxy on port 443 (https://emby.website.com) I created a Emby Connect user and I can log in with my browser at https://app.emby.media/ I link Emby Home in Google Home. I fill out the credentials and get to choose which of my servers (only have 1) I want to connect with. Then I get this message: Which seems weird to me because the app knows the name of my server. How can I fix this? Thanks, Jelle

I seem to be having issues accessing my server from the internet in certain situations. Currently, my SSL connections is handled by a reverse proxy, apache. This URL is (for example) https://emby.server.com/ but the URL listed on my dashboard is listed as https://emby.server.com:8920/. When connecting to my server with the reverse proxy URL I never have any issues establishing a connection but the URL posted in the dashboard seems to go down randomly. This is an issue because users connecting to my server with emby connect accounts are usually trying to access the server via dashboard URL. My question is can I drop the port number from the WAN access URL on my dashboard and set it to just https://emby.server.com/ or can we troubleshoot why the dashboard URL is not connecting to my server? Please let me know if I need to provide any logs.

Hello Community, I wanna ask, is there any way, to ONLY tunnel the M3U Connections through a Socks proxy witch is running? I don't want to proxy all Connections on this Server, only the Connections to the Stream-Servers! Thanks, Nice to Hear from you Guys. And BTW: I Use Emby on Debian!

Hello guys, Yes another apache reverse proxy tuto but I'm a bit stuck ! I found a vhost config that works in my case : <VirtualHost *:80> ServerName my.website Redirect permanent /emby https://my.website/emby </VirtualHost> <VirtualHost *:443> ServerName my.website ErrorLog ${APACHE_LOG_DIR}/emby-error_log LogFormat "%t \"%r\" %>s" common CustomLog ${APACHE_LOG_DIR}/emby-access_log common RewriteEngine on RewriteRule ^/emby$ /emby/ [R] <proxy *> AddDefaultCharset off Order Allow,Deny Allow from all </proxy> ProxyRequests Off ProxyPreserveHost On <Location /emby> ProxyPass http://localhost:8096 ProxyPassReverse http://localhost:8096 </Location> <Location /emby/emby> ProxyPass ws://localhost:8096/emby ProxyPassReverse ws://localhost:8096/emby </Location> </VirtualHost> If I only enable this vhost it's working. But ! I also have transmission running with the following configuration: <VirtualHost *:443> ServerName my.website ServerAlias www.my.website Redirect permanent /transmission https://my.website/transmission RewriteEngine on RewriteRule /transmission[/]?$ /transmission/web/ [R=permanent] ProxyRequests On ProxyPreserveHost Off <Proxy *> Order allow,deny Allow from all </Proxy> ProxyPass /transmission http://127.0.0.1:9091/transmission ProxyPassReverse /transmission http://127.0.0.1:9091/transmission </Virtualhost> <VirtualHost *:80> ServerName my.website ServerAlias www.my.website Redirect permanent /transmission https://my.website/transmission </Virtualhost> If I enable emby first (by renaming the file 01-emby and 03-transmission) : emby is working but transmission is not. If I enable transmission first (01-transmission and 03-emby) : transmission is working and emby is not with the following error message : You don't have permission to access /emby on this server. So I guess there is some issue with the rewrite rule. In emby dashboard I selected the "Secure connection mode" parameter to "Handled by reverse proxy". For info https://my.website:8920/emby is working. I'm not really familiar with Apache so I may have missed something obvious. Thanks for your help guys !

Hi all Literally just finished a docker install of Emby, and at the moment everything seems to be working nicely, BUT, I cannot retrieve metadata. I am behind a proxy, and have no VPN/other way of connecting to the internet. I have a system proxy configured, but it seems Emby is not taking it into account. It may be that it is because Emby is not aware of it via Docker container, and I am not sure if adding it via an environment variable will help? In the past, with Java based products, I was able to add "-Dhttp.proxy" option to the launching parameters, and it would also help. Is there some similar way in doing it with Emby? I will install Emby as a "raw" server on my Fedora machine, if the Metadata will be pulled via proxy. I just used Docker to see whether or not the product works, and it looks nice. Any ideas would be greatly appreciated!

Hi, I've set up my Emby-server with "HTTPS using reverse proxy" using the "Setting up SSL for Emby (WIP)" guide. My question is: How can I switch between my LAN IP-address 192.168.1.20:8096 if I'm at home and my https: // emby.domainname.com:443 address if I'm on the road (using the Android-app)? Manually adding the other address for the same server doesn't seem to work? Thanks!

I am running a Kodi instance with Emby plugin remotely. The access is proxied via Apache to provide secure SSL. This works perfectly in almost all regards. I can stream FullHD video and all (200/25 connection). The only thing that does not work is the automatic library update. I have to make a manual update each time anything changes. I know the server is ok: - There are local instances that are not proxied, which pick up the changes fine. - Also the remote machine does pick up the changes when I connect to the server via the site-to-site VPN, but that is too slow for actual streaming. So I am pretty sure the problem is in the Apache proxy system. What do I have to make available to allow instantaneous library updates? This is quite a bummer for me right now, because the update already takes a few minutes, and I haven't even integrated the Music library.

I am experiencing the problem precisely as described in this topic, except only in Chrome and only when requesting the actual stream file (https://myserver/emby/videos/id/stream.webm?morestuf). All other pages (logging in, navigating, cover art, ...) work fine in all browsers. I am running Emby 3.0.5821 and use Nginx as the reverse proxy. Firefox and Microsoft Edge work fine but Chrome does not. Using the exact same setup, Firefox sends the Authorization header on all pages while Chrome does not send the Authentication header on its request to the stream file (https://myserver/emby/videos/id/stream.mkv?morestuf). One difference that I can see is that Chrome is asking for a stream.mkv file, while Firefox is asking for a stream.webm file. The result is that instead of my video, I get a popup that sais "Video Error There was an error playing the video.". The popup appears to be a recent addition to Emby, because I updated Emby before making this topic and before the update the popup was not there . Screenshots of the requests made by Firefox and Chrome are attached.

how can i route my emby traffic over a proxy like tor? i would like all requests for movie posters or server updates proxied.

Following on from my thread here, http://emby.media/community/index.php?/topic/33153-proxy-settings/ I'd like to see the ability to configure proxy settings within the theater application itself.