Search the Community

I upgraded to a new laptop and transferred all my media to an external hard drive and re-installed emby media server on my new device. However it still seems to be snagged on my old computer as it will only let me in via remote connect on the new device. I no longer have the old laptop. And now, all of a sudden, it will not let me log in. I'm using the correct info but it says the log-in information is incorrect, but as the server is still locked on the old device I cannot enact a password reset either. Just paid to upgrade to emby premiere and cannot even utilize that either as I cannot get in to insert the key they sent, and when I access via the TV app it doesn't seem to recognize the purchase or give me the option to activate it - just asks me to subscribe, which I already did. How can I fix this so the server recognizes my new device as the new hub so that I can fix everything else?

I Have a Domain Name from DYNU and I have been using it for several years with no problems. I bought a Single Domain SSL Certificate from them the other day and have not had any luck getting it to work with EMBY. I downloaded the Certificate files from DYNU and placed the folder with all the files in the EMBY Server system directory. I then pointed EMBY to the .pfx file. See my Emby Network Setup in attached images. The .pfx file that was generated by DYNU does not have a password. My Dashboard shows an https link I have opened port 8920 (and port 443) on my router, but when I configure and attempt to access the site using https, (port 8920 or 443) I get 'Can't Reach This Page' error. I get that regardless if I try to access locally, remotely, with Domain name or IP. I have disabled My Anti-Virus Firewall and Windows Firewall with the same result. I also created a .pfx with a password and tried pointing EMBY to that and it did not work. I have restarted EMBY after each change. A TTL Text Record for my Domain was automatically created when DYNU generated my SSL. My http still works fine, local and remote. I'm at a loss. Is there some step I am missing or something else I need to do? Help. embyserver.txt

Hey all, I used a Caddy guide and Caddy combined with a domain from noip to try to set up my Emby server through a reverse proxy. Everything seems to be working correctly when I go to my domain name remotely in a web browser or by manually entering my domain name and port in the apps, but for whatever reason, EmbyConnect is not saving the proper connection or is not connecting properly. Every time I try to log in with EmbyConnect, it says it can't connect. Here's what Caddy shows me when it runs: 2024/09/02 21:55:55.834 INFO using adjacent Caddyfile 2024/09/02 21:55:55.835 INFO adapted config to JSON {"adapter": "caddyfile"} 2024/09/02 21:55:55.835 WARN Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies {"adapter": "caddyfile", "file": "Caddyfile", "line": 2} 2024/09/02 21:55:55.842 INFO admin admin endpoint started {"address": "localhost:2019", "enforce_origin": false, "origins": ["//localhost:2019", "//[::1]:2019", "//127.0.0.1:2019"]} 2024/09/02 21:55:55.842 INFO tls.cache.maintenance started background certificate maintenance {"cache": "0xc000430e80"} 2024/09/02 21:55:55.842 INFO http.auto_https server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv0", "https_port": 443} 2024/09/02 21:55:55.842 INFO http.auto_https enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"} 2024/09/02 21:55:55.844 INFO http.log server running {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]} 2024/09/02 21:55:55.844 INFO http enabling HTTP/3 listener {"addr": ":443"} 2024/09/02 21:55:55.844 INFO http.log server running {"name": "srv0", "protocols": ["h1", "h2", "h3"]} 2024/09/02 21:55:55.844 INFO http enabling automatic TLS certificate management {"domains": ["my doman"]} 2024/09/02 21:55:55.845 INFO autosaved config (load with --resume flag) {"file": "C:\\Users\\Andy\\AppData\\Roaming\\Caddy\\autosave.json"} 2024/09/02 21:55:55.845 INFO serving initial configuration 2024/09/02 21:55:55.848 INFO tls storage cleaning happened too recently; skipping for now {"storage": "FileStorage:C:\\Users\\Andy\\AppData\\Roaming\\Caddy", "instance": "f9be30e8-14fd-4b07-9fdd-7dd8f1b965ad", "try_again": "2024/09/03 21:55:55.848", "try_again_in": 86400} 2024/09/02 21:55:55.848 INFO tls finished cleaning storage units I'm pretty sure I set port forwarding up correctly, but I have a question about that as well. When I go to forward ports 80 and 443, do I forward the external ports 80 & 443 to internal ports 80 & 443, or do I forward them to the internal Emby local ports 8096 and 8290? If anyone has any ideas as to why I can connect to the server in a web browser using the domain name and why I can connect to it using manual entry in the Emby apps, but not with Emby Connect, I would be greatly appreciative of any assistance you might be able to offer. I'm kind of a newbie when it comes to some of this stuff, so if you need more information from me that I didn't think to provide in order to accurately assess or help me troubleshoot my issue, please let me know! Thanks!

My Emby server is on my Synology NAS 923+ in a docker container. I have two major problems I'm dealing with at the moment. In order of importance: 1. This problem started with me trying to figure out why I can't get external access to my Emby server. I have forwarded 8096 and 8920 ports (or so I thought) and still the remote access wouldn't work. I tried going into the Emby Network settings and changing my Internal and External Port numbers from 8096 to 9000 and forwarding to those ports and all that has done is locked me out of connecting to my Emby server altogether now. Anyone know how to fix this issue? I can't even get back into my Emby Network settings because I can't connect to the new internal IP address. How screwed am I here? 2. Once this issue is fixed and I can indeed get back into my server settings, then I need to finish figuring out what is holding external devices back from recognizing my server. I have had zero issues (before problem #1) connecting within my WiFi network, connected to the NAS. Please let me know if there is any more information I can provide to be more clear, thanks.

cant connect over remote unless on the internal via tailscale or something like that. realistically want it linked to my domain and be able to remote connect safely without other clients needing anything but emby. i have port forwarded all relevant ports to the correct internal ips. tried mullvad and proton for vpns but they dont offer a dedicated open port for me to use. using canyouseeme to check if ports are open shows nothing but either refused or time outs on the ping. thanks for reading

Hello, all Coming from the Plex world Secure Connections was easy to turn on (actually on by default). I am trying to determine if Emby has that on by default or what steps I might have to perform or if it's a non-issue. I am really hoping whatever is involved is pretty straight forward. When I (or a friend) is accessing my Emby server remotely I'd like to be reasonably secure. I liked that "no brainier" aspect to Plex. When I looked in the "Hosting" area of Emby server I saw a check box for requiring HTTPS (the equivalent of secure connects... maybe?) but it then asked me about Certs and stuff and I got lost. I'd rather not go to Plex for external access. I really think Emby is a superior product in many ways. Also, if there is a particular section of Emby (Guide/Site or etc) that really breaks down most of the security related data I'd appreciate. I'd like to be more knowledgeabe. What I've found in the forums is not really clear to me and seems to be spread all over the place. Thank You

As more and more ISP's are implementing the dreaded CGNAT due to IPv4 availability, there are more and more support requests in the forums on why their emby 'remote access' is not working. Would it be an idea to test for CGNAT when the 'Remote Access' button is selected in emby ? It's a simple test and then the user can simply be warned that emby will not be able to provide a remote access service on this ISP connection. Maybe provide a link to a 3rd party tunnel solution, but advising this is not supported by emby blah blah. For those that are unaware what CGNAT is (Carrier Grade Network Address Translation) - this is the ISP's own 'private' network in front of the 'Public' internet. It effectively 'shares' public IP addresses with all the IP's on their private network. Subsequently you cannot use it for 'incoming' connections - because that public IP is not exclusive or available to you, it's shared with many others behind a 'private' IP address. There are solutions around it - but they involve a network 'tunnel' - and will be beyond a lot of the users networking knowledge and capabilities.

Hi, all. I'm a bit embarrassed to ask this question, but I'm obviously having a stupid day, and Emby documentation has not helped me, today. I have my Emby Server installed on a Linux x86 laptop, which is always on. It has a dynamic IP address, from my BT hub/ router. At home, I access Emby either through an Amazon Fire Stick, or on my Android 'phone. I don't (currently) have an Emby subscription, but I'd like to be able to watch my media content, when visiting relatives in another UK location. This would be either through another Amazon Fire Stick, or Emby on UK's Sky TV, if it's available from whatever the Sky app store is called. I'm confused about how I can make this work, but also whether I need to buy the subscription service. Can anyone help me on my particularly stupid day? Cheers, Chris

I know VPN & Emby remote access is not a new topic. I'm looking into a secure way to provide VPN for my home and still ensure Emby remote access works while providing the best security possible. I have Emby remote access currently working on my NAS by providing a Google Domain (https://mydomain.com), SSL/HTTPS, and Reverse Proxy. I tried installing OpenVPN on the NAS, but Emby remote access was not accessible; as OpenVPN doesn't support Port 443. I have a 30-day trial version of ExpressVPN currently installed on my NAS and individual devices (LAN connected & WiFi where possible), but I still encounter the same problem; Emby remote access / support for Port 443 doesn't appear to work. ExpressVPN supports VPN Split-Tunneling if installed on a VPN Router, which would provide security for my Home devices, NAS, and allow Emby to bypass VPN for remote access. Since I have a Google Domain (https://mydomain.com), SSL/HTTPS, and Reverse Proxy for Emby remote access, I'm "thinking" this might be the best overall solution. I'm definitely not an expert with VPN, all secure network solutions, etc., so I would definitely appreciate any guidance. Note: If you recommend running VPN via home router, which VPN Router would you recommend?

My Remote (WAN) access address changes between 2 ip addresses for seemingly no reason? Is there a way to make this static? Or any insight into why it changes?

Hi all, I came across a strange situation in which i request help. I have running a dedicated W10 Emby server for quite some years now. Version 4.6.4 already. When i first started the server i had a smartphone with Android One running and i was not able to login through remote access. Tried everything even with the help from you guys and eventually we concluded the isp must have something blocked on their end. When it was time to buy a new phone, i bought an android phone again but not from the Android One program. To my happiness i tried to use emby remotely and it worked! Unfortunately i dropped my phone and it broke this week so i bought a new one which is part of the Android One program again and i just found out i am again unable to login remotely. I have not changed any settings from my router, pc and also we now know the isp is also not the problem. I hope someone can shed a light to help me solve this. Thanks in advance everybody.

I am trying to get a handle on the differences between Plex and Emby. I have been using Plex for sometime and am considering switching to Emby. What I am trying to confirm is whether a remote Emby client can access my home server when it is behind a double NAT scenario. My server is behind my router (which is obviously using NAT). But, in my case, my network service provide also uses NAT in front of my router (WAN side of my router) or rather the router they provide me to connect to their Internet service. Because this is the case they have one router somewhere in their network that represents a number of their clients (me included) with one public IP. I obviously have no access to that router. So adding port forwarding is not an option. An interesting thing with Plex is that when you make a connection to my server by logging into the company Plex server (plex.tv) with a web browser or a Plex app that these apps can access my server even though it is behind this double NAT scenario. The only way this can work is that the plex.tv server has the client port number my server uses to access my account on plex.tv and relays that info to the client app that is trying to make a connection. Then the client app attempts a direct connect using that client port number or relays through the plex.tv server. I assume that Emby server does not offer such a feature. Because so far I cannot make this work. When I log into Emby Connect it shows my server but when I click on it it fails the connection. So, I am assuming all the Emby Connect is doing is a translation from a name to an IP address (similar to the way DNS works). Incidentally, TV's running the Plex app are unable to connect (just like Emby apps). I am assuming that is because the Plex TV apps (or Emby apps) try to make a direct connection to the server at it's known server port number (and are unable to make a connection using the client port number as in the Plex case). Does this all make sense and am I right in my analysis?

Hi everyone, Just set up my Emby library and while it works on my Local network none of my remote users have access. I have read through other threads as well as followed the connectivity guide and connection troubleshooter. I have port forwarding set up and when I check my port on canyouseeme.org and portchecker.com they say it's closed. I've attached my logs and port forward screen so any help would be so very appreciated. embyserver-63743414400.txt

I am a new user of Emby after using Plex and XBMC for many years. I'm having trouble accessing the mac osx server remotely via IOS iPhone X. I'm able to access Emby on the local network with my iPhone but cannot when wifi is turned off on iPhone. I have a airport extreme router and have tried port forwarding with no success. When I click on the server from the IOS app I get the spinning wheel and the message comes up that says: "We're unable to connect to the selected server right now. Please ensure it is running and try again." When I login into Emby from IOS app it show my server but when I click on it nothing happens. I've also tried to add server with lan address and port, and signed into Emby connect, all to no avail. I've attached a log file not sure it is the right one, it is the most recent one.

Just need a 'YES' or 'NO' answer to the above. Because not being a techno type, I have only just found that Emby opens up a port in my router to the internet without my knowing, during the installation. Which to me doesn't sound very safe. So I am hoping that if I purchase the Premiere package that it will provide the necessary SECURED access path, so that I can share my media with my friends who live down-country. I was using Plex and thought I would try Emby too. Plex already has the secure access for sharing, Emby is much faster to use. Thanks for any replies.. Cheers CD in NZ

i've recently come to emby from plex because the plex service has become more and more unreliable over the last 2 yrs to the point of becoming unusable.... ive mabaged to get everything working remotely on port 8096 with no problems whatsoever. however port 8920 is dead in the water as far as emby is concerned.... im using and asuscomm.com ddns with a let encrypt key and have converted it from pem ot pfx as directed in other posts with a passowrd etc.... the ports are forwarded on my router and can both be seen from canyuseeme.org... and yet emby still wont connect via https on any device in or ut of my network.... ive been going through the forum for the last 3 days and am almost at the point of just sticking to netfix and not wasting another dollar or minute trying to get these things to work as advertised..... im not a particularly advance user as im sure you can tell.....and emby has a rediculous amount of logs already so wouldn't know where to begin in providing more information.. i really am at the end of my teather with this

I have Emby installed on a QNAP, which also has a VPN service running through OpenVPN. Scenario 1: VPN turned off, I can remotely connect to Emby Scenario 2: VPN starts up before Emby has started, so Emby uses the VPN address. Unable to access remotely Scenario 3: Disable VPN, start Emby and then restart the VPN. Emby show normal external address (not running through the VPN), and I can access Emby remotely. Is there a way for my to get Emby to use the non-vpn address only (maybe by locking it or something?) Many thanks for any help

OK. This is darn odd. Since the most recent update I am unable to connect to Emby from anywhere but on the server. I have an IOS app, multiple PCs with web browsers and two rokus. None of them can connect to the server, and we are all on the same network. I have tried by direct IP address http://192.168.2.160:8096 and I have tried it by remote DDNS names too. I can ping and connect to the server. I have rebooted every machine in the house, including network switches and routers. I can ping the server, map drives to the server, copy files to the server, even map a drive to the server and play the media file through another app, like Windows Media Player or VNC, but I cannot connect to the Emby service. Also, I can even play Emby through the web client (192.168.2.160) on the server, not the remote ddns address. I have verified the IP address, and as I said before I can map drives and play files and even can play files through Servio. Any ideas?

Hi all. I know this same question has been asked a number of times, but I have so far been unable to find a fix for my situation/setup. I recently purchased a lifetime membership for Emby based on using the software to watch movies/shows locally (through my chromecast) at home. My 'server' is a PC running Windows 10 and I have my media located on an external hdd. I am using a TP-Link Archer C3200 router. I have been trying for the last week or so to figure out how to access my library remotely with no luck. I have tried via the iOS app (sign in with Emby Connect and no dice) as well as on a couple different laptops. So far I have tried/looked into the following: - confirmed uPnP is enabled on my router - confirmed automatic port mapping is enabled on Emby - created inbound rules for Windows Firewall to allow ports 8096 and 8920 on my server - assigned Reserved IP address for my server - set up 'port forwarding' via virtual servers (external port = 8096; internal IP = 'Reserved IP address from above'; Internal Port = 8096; Protocol = TCP) (also did the same for 8920) - confirmed that 'allow remote connections to this Emby Server' is enabled - canyouseeme.org CANNOT see my service at ports 8096 or 8920 Any help would be greatly appreciated.

I'm running emby on 218+ with Linksys ea8500. emby worked great out of the box when playing locally, however when I looked into remote access, I ran into problems. I could not access the server remotely, so obviously like recommended, I had to port forward. I have done that before so I'm familiar with it. So I open the port in the router and remote access works. However, local playback is now crippled. It constantly buffers or won't play at all. If I remove the port forwarding in the router, local playback works again. I have tried port forwarding the default 8096 port and also other different port numbers. Same result. Local playback is crippled. Does anyone know what problem could be? To me this looks to be some kind of port conflict. Local vs remote.. I don't know. Thanks

I tried accessing my server when I was on vacation and I was unable to connect. Remote access has been working fine for the past year, I'm not sure what has changed. I checked my firewall and everything looked good, just to be safe i removed the inbound rules and added them again, but still no luck, I even disabled my firewall completely but it still didn't work. I am able to remote into my computer with Chrome remote desktop connection, so it seems like my network is working as it should. And yes, I do have port forwarding set up. As I said earlier this was working perfectly for over a year, It just stopped recently. Anyone have any Ideas?

Hello, I'm a longtime Plex user wanting to move to Emby. The other night I downloaded Emby server on my computer (Linux Mint), uploaded all of my content from dual 8TB External HD's and added my nephew as a user to test out the remote access function...everything worked great with no problems!! The next day, I turned on my VPN (NordVPN, which does kick me off of the servers until I disconnect it), downloaded some content and that night, Emby worked inside my house but no longer worked remotely for me or my nephew. On Plex you can see if the remote access is red or green but cant fint that function on Emby. Anyway, When we try to connect to emby remotely outside of my house we get "We're unable to connect to the selected server right now. Please ensure it is running and try again" I have restarted the Emby server, restarted the router, restarted the computer, deleted and added my nephew and added him as a user again. Is there a setting i'm missing somewhere? Why would everything work perfect the first night and not work remotely after that?

Hi all, I just got Emby 3 days ago. It works fine in my house. But when I try to watch it at my girlfriend's house on her Roku I am able to select my server and then I just get a spinning wheel. That's as far as Emby works when not in my house. Can anyone please help? Is anyone else having this problem?

In the morning I can not connect remotely to the home server. The settings did not change, the antivirus was turned off, the port was forwarded in the router. There is simply no connection through emby connect, not directly. And the connection attempts were made both through the browser and through the application on the android phone. What could be the problem? http://www.canyouseeme.org/ shows "connection timed out"

Hi all, I have a router running latest Advanced tomato firmware and PIA VPN running on it. I would like to run a script to enable Port Forwarding to the Port PIA provides me so I can access the Emby server remotely. However after searching the internet I am still no clearer on how to achieve this. Any help would be very much appreciated. Thanks