Search the Community

Took me a while to figure this out. Hope this helps others. I moved from Finland to Spain. Network in my new place was not what I was used to. Most of my 4K media became unwatchable. Turns out that some years back I had manually adapted my network speed settings in emby and now that network nolonger had 10Gbit connectivity my larger files did not play well. If you are suffering from similar issues check emby APP settings. (Up right corner.)

Hello everyone, Despit of all my researches on the forum, I'didn't get the solution to fix my problem. Currently, I run Emby (4.8.8.0) on a Synolgy NAS DS918+ (DSM 7.1.1-42962), directly with the syno Package Emby. Emby server works fine, I can launch any movies or tv show, but after setting up the trailer plugin (with Emby Premier), when I launch any media, the "trailers" not working and I get the following message "No compatible streams are currently available. Please try again later, or contact your system administrator for details." I've atteched the serve logs. According to it I've a nentworking problem to acces to trailer website, you can see above : 22:25:53.030 https://cl2.buscafs.com/www.metatube.com/public/uploads/videos/456932_mp4.mp4: Server returned 403 Forbidden (access denied) Do you have any idea to solve it ? Thanks embyserver.txt

Are you able to log into your network using a Roku Emby app remotely?

Hi there, Lately, I have found that my upstream internet connection is running out of bandwidth as multiple people are streaming remotely at the same time. I have access to a second internet connection (in another location). I have a couple of ideas on how I could utilise both internet connections to serve content, however, I am not sure if Emby will support some of these methods and was hoping for some guidence. My ideas are: Idea 1: Co-Located File Stores w/ Single Emby Instance (Preferred idea - But probably not possible) In Location A (LocA) I would have my main server with Emby installed, accessible over the internet at foo.com In Location B (LocB) I would store a file server that is mounted into Emby. This file server is not internet accessible (e.g. Behind a NAT). Through some magic files served from LocB would go directly to the client and not via the LocA Emby instance/internet connection. If I mounted LocB files onto the LocA server (e.g. cifs/rclone/etc) and a user started streaming content from the LocB file server, the flow of traffic would be: LocB -> LocA -> client. This does not solve my issue as I want the flow to be LocB -> client. I assume this is not possible? Idea 2: Replicated Instances (Probably not data safe) LocA has a file store and Emby instance LocB has a file store and Emby instance Sync is setup to replicate content and config Load balancer at foo.com which routes users to the most free instance I can see watch history, user settings, etc not being reliable particually if a client is bounced between instances. 2 way sync would also not be functional, probably. I can also see data corruption in the config files. I dont think this is a great idea either. Idea 3: Replicated Content, Seperate Instances Sync content between LocA and LocB, each with a standalone/independant instance of Emby. Some users will be created on LocA, accessible at fooA.com, others created on LocB, accessible at fooB.com Probably the safest way, though a lot duplicated manual work. I think I would probably need a second Emby Premier license too? Misc Ideas: Upgrade my internet connection ($$$$) Stop using ancient hardware and get something that supports QSV and transcode on the fly at a lower bitrate ($$$$) Tell some of my users/family to suck it and get Netflix subscription Any help or other ideas is greatly appreciated. Thanks!

Hello, Environment: Emby Server 4.7.13.0 Emby for Android 3.3.07 Android 13 Premiere enabled What is working: Usage internally: wifi and wired connections in the same LAN as the server. Smartphone, PC, TV, even my car with Android Auto through smartphone. Usage externally: data connection through my router/firewall, no problem with my ISP either. Smartphone, car with android auto, other WAN connections. What is not working: Starting to play playlist inside the LAN and continue after going out, either on smartphone or through Android Auto. I set up Emby behind an apache proxy to ease certificates, DNS and network flows management through firewall, but I guess it's not the source of the issue. Internally and externally Emby is reachable through a unique name (eg. emby.myfancydomain.com) and HTTPS/443. As the proxy is doing the routing job, all Emby network config is left by default, proxy falling back on 8096 HTTP default port, this is maybe the problem but I don't know which parameter to correct, I did several tests without solving. Testing with local terminal DNS cache is instantly discarded and get the public IP, but I need to restart the app to make it works, so I loose the playlist state on smartphone. With Android auto it's even worse, I can't restart with the Android auto interface, I need to disconnect the smartphone from the car, restart the app and then reconnect to the car... And of course loosing the playlist and song state. Fun fact, the reverse action works well, but I don't know if my data connection is still active or if the app switch better when started outside my network and then come back to home. Thanks in advance, Leahkim

Hey Squad, So i decided it might be good to set up SSL but i'm just missing some knowledge i fear, so i was hoping others who've struggled here can help me out. current setup: - macos emby server -> router (with forwarded ports) -> afraid.org DNS forwarding I figured my easiest move might be to just use certbot, but there i run into it asking me for webroot where...i have no clue what path to use. i'm not sure if maybe i'll just need to squeeze a domain name into that chain or if that's not the issue here. Thanks in advance.

Hi everyone... I am a lifetime EMBY Premiere subscriber, and I "LOVE" EMBY, and have been using it for a LOOONG time! Recently, I upgraded my little server to a bit of a more powerful computer system. The new system runs Windows 11, and EMBY ran fine right out of the box, once I had re-installed it and restored my EMBY backup to the new computer. Everything ran GREAT, until...... My server is NOT accessed externally by anyone, and is used strictly as media access within our household. I access the media from an nVidia Shield Pro in the main living room via ethernet LAN cable, and from 2 ROKU TV's in 2 bedrooms, via WIFI. The Shield, of course uses EMBY for Android TV & the 2 ROKU TV's use EMBY for ROKU. A few weeks ago, accessing media became VERY problematic all of a sudden, without having made ANY changes to the system. Once we watch a media file (movie, TV episode, or even music) and return to EMBY's main GUI, the GUI gives me an error message that "EMBY is NOT able to access the network". I also have IPTV set up as M3U access (no PVR, but recordings to HD), and I get a "cannot access live TV channels" message, sometimes before, sometimes after the network error message. The ONLY way to get EMBY to load up properly is to exit the program and re-load it MULTIPLE times (and I mean up to 10 times!) and it will EVENTUALLY load properly and display all the media correctly. I have reviewed EVERY network setting and Live TV setting within EMBY multiple times and cannot find anything that could cause this type of behavior. I am also running a (legal) copy of NordVPN, which I tried disabling, which made no difference. I tried disabling access to IPTV, thinking "IT" might be the problem, but, alas, to no result either. I am by NO MEANS a network expert, but after comparing my previous Windows 10 installation to my new Windows 11 installation, and removing any and all external causes for EMBY to not be able to access the network properly, the ONLY explanation I can find, is that there is SOME hidden network setting that I am overlooking! Can any of you suggest where I might look to see what is impeding network traffic. please??? BTW, both ROKU TV's also have problems accessing the network as well after successfully playing any media file. Thanks in advance to anyone that can shed some light on the subject!!! LONG LIVE EMBY!!! Gerry Emm P.S . - Please advise if you need me to upload any log files or anything to help in troubleshooting this problem...I would upload them right away, but don't know WHICH ONE(S) to upload!!! TYVM once again!!!!

Hi guys, I noticed on my main dashboard that my remote access link includes a port at the end when in reality that is not needed. When I went to the network tab and tried to remove the external port, it indicated it was a mandatory field. Issue is when I click the link above for Remote Access (WAN), I get a: ERR_SSL_PROTOCOL_ERROR Ideally my Remote (WAN) access link should be: http://emby.myaddress.myds.me (no port) Does anyone know how to fix this or if its fixable? Thanks!

Was this ever resolved or a workaround in later releases? I have a similar issue. Part of my library is stored on a remote disk that is mounted via CFS/SMB to my NAS, where Emby is running and the main library is stored. After a disconnected disk, the movies are being deleted from the library and I will need to do a full reboot of both NAS and Emby, do a full re-scan (sometimes it takes a couple of times) to get them back. Metadata is stored with the media but still need to do some manual fixes in terms of selecting proper backgrounds or covers which are missed or not properly recovered. Strange thing is that Movies is much more affected by this compared to TV Series.

Hello, I'm unable to get SSL to work on my Emby server, I've been able to remote connect on http with no problems but would rather be using TLS. Currently have Emby running on Windows 10, Appropriate ports are open on router. Certificate .PFX created with Certify The Web & exported through IIS. Attached screenshots + log from Emby below, Appreciate any help 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 all Half a year ago, I moved my emby instance from my NAS to a seperate machine (Win10) to get better performance. However, as I'm using emby as a DVR and my library got quite ... ähm ... "comprehensive" by now, I also upgraded my NAS and seperated media server and data storage. I'm using SMP paths in my libraries to add the shared folders to emby (location = \\SERVER\FOLDER1). I had a power outage today and (re-)noticed an odd behaviour of emby: as my media server is a lot faster in booting up as my NAS, accessing the library failed when emby service started. As a result, some of my libraries where just gone from the admin interface and in the remaining ones, nearly all the entries were missing. Restoring my nightly backup did fail as well (I experienced the already known bug with multiple entries after restore) ending up with me deleting all libraries and setting them up again. Yes, one could think that the settings were damaged by the shutdown, but I already experienced the same behaviour when I shut down the NAS and media server in parallel a few month ago. Did you experience something similar in the past? If so, it seems that emby doesn't destinguish between "non accessible" and "non existent" when accessing libraries. It might then be a good idea to catch that error and allow some access retries or even "halt" / "pause" a library that can't be accessed instead of just deleting the entries or even the whole library. If not, it might just be my setup and I would appreciate any tips on how to change it to avoid a repetition of that... Cheers!

Hi there I am a complete newbie to emby and these networking things. But I was wondering is it possible to add drives which i can only access through http to emby. For example: I have this folder "http://103.106.238.74/Data4/tvseries/". I was wondering if I could add this as a library. TIA

Hi guys, Looking for advice/help..... Next month I go into jail Hotel Quarantine in Sydney. Two weeks locked in a room with my wife..... I will have my NAS with me, plus a laptop with a single ethernet port, a 16-port switch and a Wi-Fi-router....NAS does not have Wi-Fi, only ethernet ports. I don't know in advance if my room will have Wi-Fi or an ethernet port...however, probably just Wi-Fi. Is it possible, using what I have, to setup a local network so that both of us can connect to Emby on my NAS on our various Wi-Fi devices (another laptop, iPad and Android phones)? I'm not looking to expose my NAS to the outside world, just my room...

embyserverlogidentifyerror.txt I am unable to retrieve tv show metadata from the internet due to a TrustFailure - CERTIFICATE_VERIFY_FAILED Here an error snippet snippet from the attached log: 2021-01-05 11:09:54.348 Info HttpClient: HttpClientManager GET: https://www.thetvdb.com/api/GetSeries.php?seriesname=Downton+Abbey&language=en 2021-01-05 11:09:55.139 Error HttpClient: Error TrustFailure getting response from *** Error Report *** Version: 4.4.3.0 Command line: /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121 Operating system: Unix 2.6.32.12 64-Bit OS: False 64-Bit Process: False User Interactive: False Mono: 6.8.0.105 (tarball Wed Apr 8 20:33:25 UTC 2020) Runtime: file:///volume1/@appstore/EmbyServer/3rdparty/mono/6.8.0.105/lib/mono/4.5/mscorlib.dll System.Environment.Version: 4.0.30319.42000 Processor count: 1 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/4.4.3.0 System.Net.WebException: System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED at /source/mono/external/boringssl/ssl/handshake_client.c:1132 at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00048] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in <b373cc92cfb94ef6a19b4f1140645494>:0 at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool) at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in <b373cc92cfb94ef6a19b4f1140645494>:0 --- End of inner exception stack trace --- at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00262] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x0016a] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <b373cc92cfb94ef6a19b4f1140645494>:0 --- End of inner exception stack trace --- at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebOperation.Run () [0x0009a] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <9d3f0d4bd0fb4c1e8b6c2ac1ba1303ac>:0 Source: System TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult) InnerException: System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. Source: mscorlib TargetSite: Void Throw() at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00262] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x0016a] in <b373cc92cfb94ef6a19b4f1140645494>:0 at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <b373cc92cfb94ef6a19b4f1140645494>:0 InnerException: Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED at /source/mono/external/boringssl/ssl/handshake_client.c:1132 Source: System TargetSite: Boolean ProcessHandshake() at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00048] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in <b373cc92cfb94ef6a19b4f1140645494>:0 at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool) at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <b373cc92cfb94ef6a19b4f1140645494>:0 at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in <b373cc92cfb94ef6a19b4f1140645494>:0 Any help would be appreciated.

Hi all My first post I'm really struggling to connect externally to my network. I've tried using the Emby Connect functionality and failed miserably. Whenever i try to login I just get the sign in error image attached. I even click the forgot password button and just get some page does not exist message attached. I know the password and username is correct as I've logged into this forum. The user is setup in the server to allow remote connections too. So in my wisdom I assumed that perhaps the router is blocking the access after reading the connectivity help. I'm not an expert on router port forwarding so hopefully you can help me please. My Synology NAS has a reserved internal IP of 192.168.1.136 I have setup a forward as attached in the image. I think I've done this correctly?? My router is a talk talk sagem router and is fairly decent at offering forwards and things. I did it with Plex and worked fine. Please can someone help me as I'm really struggling with this and what else to try. I can take more screenshots of anything you need to see. Thanks in advance

I am new to Emby and I have been using plex for a year now. Why can't Emby see my mapped network drive on my server? When will Emby let you add a network drive with a password? I have looked around and it seams this question has been asked a lot over time.

Hi, I have just switch to Emby and was wondering what are some good settings for Transcoding and Network? I'm using iMac to stream over wifi to LG TV. Thanks

Hur påverkas en router/brandvägg av flera flera/många strömmar över internet? Vad blir flaskhalsen i ett normalt hemnätverk? Sitter på 250/250 lina, och funderar på att byta ut min edgerouter x till något mer rejält så som Huawei Security Gateway USG6510E eller Fortigate 30E. Andra rekommendationer mottages gärna. Får man större påfrestning på nätverket vid användning av reverse proxy kontra lägga in certifikatet i Emby? Mvh

I have installed Emby on Ubuntu server 20.04.1 and generated an SSL cert for it for remote use. I generated the cert using OpenSSH for the cert request and Zero SSL for the certificate issuance. Once the cert was created, I downloaded and installed it at /etc/ssl. So now the /etc/ssl path has ca_bundle.crt, certificate.crt and my private key. Then I configured Emby to use SSL and pointed it certificate.crt and restarted Emby. It is not working over SSL (of course, it works fine over 8096). When I looked at Emby's logs, I see: "2020-08-26 14:34:13.628 Error App: No private key included in SSL cert /etc/ssl/certificate.crt." The private key is in the same directory. Any ideas about what I am doing wrong here? Thanks, Bob Reed

I had been running Emby on Windows Server 2016 for some time and watching movies and TV shows on my Mi Box S (MiBox4) Android box on Kodi with Emby plugin without any problem. Last week I migrated my PC to Windows 10 Pro and reinstalled Emby server on it, also did a fresh install of Kodi on my Android box to re-sync everything. Since then, it's been a debugging nightmare for me as no matter what video, large and small, high bit-rate and crap sd, video playback stops randomly every few minutes! First I thought that it might be my router configs (It's a 2.4GHz running at 40MHz wide channel 150Mbps N)... I kept playing with the configs, replaced DD-WRT with OpenWRT, then with the original D-Link firmware, then back to the latest version of DD-WRT; no matter what I did the videos kept stopping. Then I started messing with Kodi on Android's advancedsettings.xml's cache/buffer values, I even installed Emby's Android app, still the same, video drops randomly, sometimes with the "source too slow" message. I then came to my PC, changed the Realtek NIC's configs, Windows registry values, Firewall settings, routes, even reinstalled and reconfigured Emby numerous times, it even got worse! Now I come to thee completely exhausted and out of ideas, looking for help... Any ideas? Here's the most usual error on Emby's logs: 2020-07-20 10:20:55.583 Info HttpServer: HTTP Response 206 to 192.168.0.155. Time: 162278ms. http://192.168.0.125:8096/emby/Videos/1939/stream?static=true&MediaSourceId=72b02541420c7e39fc9d4796d965a2df 2020-07-20 10:21:26.604 Info SessionManager: Session 8b7b1e843b7e2410fdd159d7908f4244 has gone idle while playing 2020-07-20 10:21:26.604 Info SessionManager: Playback stopped reported by app Kodi 4.1.19 playing Deeper, Deeper, Deeper Still. Stopped at 713000 ms I bet it's some kind of f*-up on Microsoft's side as I did not have ANY problem with the same PC, Router, and Box on Windows Server 2016 even with playing very-high-bitrate 30GB 1080p 4-hour movies! If it needs mentioning, there's no problem playing videos on Emby server localhost.

Hi guys, If anyone can help me find a solution it would be wonderful. Accessing my domestic Emby server on my TV worked well until I changed my configuration for practical reasons. My new setup is like this : - TV wired to the router A provided by my ISP. Router A is directly plugged into the wall to receive fiber network - Router B (this one I once bought for wifi expanding) wired to router A - PC server wired to router B. So my guess is that the PC server is not on the same LAN as the TV. How can I setup router B so that my TV can "see" the good IP address and port ? I don't have a very good knowledge in networks. Thanks a lot

I wish I could put DNS names in addition to IP addresses in the "local networks" field If that was possible, I could put the name "dyndns.net" from another address (my beach house). My Internet provider assigns me an IP address that changes frequently. Now I put (for example): "192.168.1.0/24, 52.41.151.131", but the address of my beach house "52.41.151.131" I have to change it frequently. I would like to put something like "192.168.1.0/24, mysecondhouse.dyndns.net" Thank you

So, I've got a baffling issue. I cannot remotely connect to the MB server I have running on a Windows 10 machine. I've tried all suggestions on the connectivity page. But even with the firewall temporarily off, I cannot connect. Local connections work fine. I don't have access to router settings due to the apartment complex having all the routers locked down (whitelist probably). But I even tried using my mobile hotspot and no dice. Canyouseeme reported no response on port 8096 or 8920 using either internet service. I even tried each connection again with a VPN (PIA) turned on on the host machine, though I didn't expect any good results from that.

A fundamental question about security, especially because of the current problems caused by the so-called Emotet Trojan: I use the emby server under Windows10 on the same PC where my Kodi Client is installed. The data is stored on a Synology NAS. Under Windows direct, I did not set up network drives directly on this PC, but use the UNC paths for the libraries, e.g. \\IP\Share\folder\... Since emby does not allow you to specify credentials, the logged in Windows user must have access to this shares on the NAS. In case of a Trojan infestation of the PC, especially Emotet should have no problems with encrypting the complete data on the NAS with these read/write rights, even if the network drives have not been assigned directly under Windows. It would be much safer if the access is not done with the logged in Windows user, but with another user whose credentials have to be transferred in emby. According to my understanding, a Trojan infestation of the PC should then no longer be able to access the data directly from the operating system and possibly compromise them. So is it possible to transfer access data to network drives as well? Thanks a lot.