Search the Community

Hey, In my network, I have my emby server running (as others do), but when I set up new apps I need to type in the server name, and port - always. This sucks. It would be awesome to have the apps autodiscover this information - and I have three ways of doing this: Use an SRV record in the local DNS zone: SRV records are well known and supported, to help clients discover resources on the network. It would be possible to have a well known name, like: Using this, the app would able to look for _emby._tcp at the local DNS zone (get this from the netcard). In return, the client will discover: The servers name (emby.example.com) The servers port (80) .. thereby saving the user from typing this in. Unlike mDNS, DNS can be configured by a network administrator to support "odd" scenarios, like if a I had a network where I wanted to use a specific Emby server (on the internet, or some other reachable network) - I could configure this in DNS and have the client apps in my network discover this server - even though it wasn't available locally. Use an SRV record in mDNS: mDNS is a DNS system where each participating computer announces itself. Emby Server would be able to join this multicast DNS network, and announce the SRV record from before. Client apps would do the same, and then perform the query in mDNS instead of DNS. The benefit here is that this is likely zero-configuration for an end user. The server will automatically announce itself, and clients can automatically find the server(s) in the network. This and SRV in DNS is also sometimes called "DNS-SD" for "DNS Service Discovery". Create a custom UDP broadcast request and response: Much like multicast DNS, you could send out a custom UDP packet to 255.255.255.255, thereby broadcasting it to the network. The Emby Server could then respond to this, with the server name and port. This will not work well in IPv6 though. Mike.

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.

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, I have configured my local network as `192.168.1.0/24` in the network settings in Emby. Then I have configure some of my users with the option "Do not require an password on the local network". This seems to be working and I can now login without an password. The problem starts when I try to contact the server from an different network (172.16.1.0/24). When I click on my user it signs in without an password. I would expect it to ask for my password because this isn't defined as an local network. In the dashboard the successful login is reported with the ip address 172.16.1.30, which is expected. I am directly connecting to the Emby server (no proxy), tcpdump also shows incoming network packets from the source ip 172.16.1.30 as expected. Tested versions: 4.7.0.18 beta and 4.6.7.0 stable System: Linux Debian 10 (4.19.0-18-amd64)

Hi, i have an issue connecting to my emby server using Emby connect account. My IP is set to be dynamic for the device that is running the server, hence EMBY connect sounded as an excellent option for me to connect across device without going back and forth to my host device for IP address. However, i am unable to connect to the server from any device using the EMBY connect. I read somewhere, opening port solves the issue, unfortunately i am weak in networking skill. I have configured the port to open at 8096 and 8920 with the 192.168.0.xxx (The IP is binded to the device in which the Emby server exists). Yet, nothing is working on the side of EMBY connect. If it makes any difference, the server is running on an android mobile phone, as i thought it would be a good idea to have a portable server which i can connect to my another device using Mobile Hotspot. Long story, short. I want my other devices to connect to the server using EMBY connect without adding the IP manually. Kindly do suggest if there is any fix for it, or am i doing something wrong?

hi guys my isp has blocked port 80 and I'm unable to authorize my certificates for my ddns. for the sake of the noob users on my network it would be helpful if your apps would automatically accept self signed certificates. i understand this is not possible in web browsers but surely its possible in your apps on smart tv's and consoles etc.... i have recently had to give plex my money which i am not happy about. i dont want to stop supporting emby however if i cant use the secure connections its of no real use to me anymore.

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

How does my ISP see my outgoing network traffic? Do they see the actual music titles? Movie titles? and Podcast titles? Or is it just file type information that they see. I have about 15 users. 5 of them are in my house, 7 of them are scattered around the country and a few are in different corners of the world. I'm probably streaming about 10-15 hrs a day to various users mostly HD content. I don't have an SSL cert setup yet and wondering if I should if my ISP is snooping on my data. Thanks!

I would like to have my EMBY server respond on a different IP address to the main QNAP box. I have seen, and unsuccessfully tried to use, settings that suggest this is possible. I suspect that I am missing some pre-requisites though and wondered if anyone can point me in the right direction to get this working.

Hello all! First off, I apologize if this topic has been posted elsewhere, but I could not seem to find a solution that relates directly to my problem. My Goal Is to use my Apache web server as a proxy for all external connections. In other words, I want emby to run under my domain (E.g. app.example.com/emby) My Setup I have a dedicated box running Windows 7, this is where Emby is running. Then, in a virtual machine (same box) I have a Ubuntu install that runs my Apache web server. My Problem Emby (seems) to refuse all incoming connections on the public port (8096). After spending multiple hours tinkering with my Apache server, I eventually tried to just to connect to the server directly using it's internal IP and the port number 8096 (i.e. I punched 192.168.x.xxx:8096 into the browser on both the box itself, and my personal computer). Each case gave me "ERR_CONNECTION_REFUSED". Things I've tried thus far I've checked using a different port for the public port (4141) I've checked the firewall, there is an inbound entry for 8096 Disabling windows firewall completely (Just to see if it was the problem) Setting my Personal computers IP in the Whitelist of Emby (With the filtering mode set to 'Whitelist') I've also followed the Connectivity guide to try and at least get things connected via my public IP. My Configs Here is the 'advanced' section of Emby Here are the entries for Emby in the Windows firewall.

I have couple of users who are outside my network but still can access my server via vpn. I set a bitrate in the playback settings of 1mbit. "An optional per-stream bitrate limit for all out of network devices. This is useful to prevent devices from requesting a higher bitrate than your internet connection can handle. This may result in increased CPU load on your server in order to transcode videos on the fly to a lower bitrate." But it doesn't look like it's working. I want to limit anything outside of my network to 1mbit and force transcoding. Here is my setup: There is NO access from WAN. Server side: 192.168.1.0/24 <-- SITE TO SITE VPN --> 192.168.10.0/24 Remote site It seems when the users access server from 192.168.10.0/24 emby just direct plays content there is no limit. the files that are being played are huge (1080p/ 4k etc... ) so that saturates my upstream immediately. Plex solves this by a setting that you can set "Networks that belong to local net" and anything that's outside that range is considered remote and limits are enforced. Is there a way to implement this?

Hi. Has anyone successfully enabled DLNA in Emby via Docker and has Bridge networking configured instead of Host networking? I follow all the instructions but DLNA is NEVER visible from outside the container. If I change networking to HOST, then everything works fine.

I have a question I'm curious if anyone knows the answer to. I currently use Emby for home use, because for some reason Plex doesn't work on my local network, but I have people that use my Plex for remote access. So yesterday I finally decided to figure and set up Emby for remote access, I added the port forwarding to my router and tested it out, it worked. Then I went to use Emby at home and it wouldn't work on the local network, kept getting errors, but as soon as I deleted the port forwarding I had added to my router it worked like normal again. Ideally I would like to be able to use just one program for both local and remote access, and I believe if I deleted the port forwarding I had setup for plex it would likely fix the issue with that as well on my local network. Does anyone have any ideas of what the issue I am having is and possible solutions? Any help would be greatly appreciated. Nick

Let me start off by saying while I have a lot of experience with windows server, I am new to Ubuntu/linux, so please forgive me if this is a very easy issue to solve. I am running windows server 2008 R2 on my main server with media stored on several raid arrays and shared via windows file sharing across my network. I also run several virtual machines on this box via hyper-v, one of which is Ubuntu server 16.04 LT (command line only) with Emby Server. The Ubuntu server connects to several of the windows shared folders via CIFS (attached the FSTAB configuration file) and mounts automatically when the VM boots. I set up the Ubuntu/Emby VM last October and it worked perfectly until I started getting errors about a month ago. Now after the Emby server has been running for a few errors hours my Movies or TV shows all disappear from Emby. When I open up the Ubuntu server console via hyper-V I get two errors that repeat: “CIFS VFS: Error -104 sending data on socket to server” and “CIFS VFS: Error -32 sending data on socket to server” There is significant network traffic be directed towards the windows server machine and the Ubuntu virtual server has above average CPU usage. When I reboot the error temporarily disappears but comes back after a few hours later. I tried rolling the VM back to a clean install (circa October 2016) but after installing all the ubuntu/emby updates the problem came back. When I try to run “sudo umount –a” I get several errors saying “target is busy”. I can manually browse and play all the media files on any of the windows PCs on my network, so I don’t think the issue is on the windows server side. It looks like CIFS is getting suck in some sort of loop. Can anyone provide some insight on why this is happening? Let me know if there is additional information I can provide to help debug this.

After the most recent updates, I have run into an issue with Emby Server 3.1.6007.33439. Emby Server seems to be binding to the wrong NIC - binding itself to the VMWare VMNet #1 Virtual Network Adapter (a VMWare Host-only Network) rather than to the physical NIC - ASUS PCI-E AC68 WiFi Adapter. This has rendered Emby Server inaccessible to anything on the local network (since VMNet #1 is a Host-only adapter). Disabling the VMWare Adapters forces it to use the WiFi Adapter but this has to be done every single time Emby Server is started. Is there a way to override which adapter is used while this is investigated? The OS is Windows 10 Pro (Insider Preview - Fast Ring but it did it on the Anniversary Release as well which stayed installed up to today) and it's only Emby Server which is binding to the VMWare adapters rather than a physical NIC. Other applications operating on the localhost are binding to the correct network adapter (the ASUS WiFi).

I currently have Emby Server running on Ubuntu Server 16.04. The main problem is that i am able to access the Emby sever on my LAN yet when I attempt to connect to the server for outside of the LAN I get the error "We're unable to connect to the selected server right now. Please ensure it is running and try again". I have read the Wiki of networking and have configured everything as suggested. I have already told my router to port forward port 8096, I have opened the port already through Ubuntu, and I currently have a static IP address for my server. Yet this error continues to show for all devices (Iphone, Laptop, Android) that have attempted to connect from outside of the network. Where I am having trouble with trouble shooting my problem is with how my home network is set-up. I currently have ATT Uverse which forces me to use their router, a Motorola 5268AC, which is a very poor device, so I ended up shutting down the wireless features of this modem/router to behave as a modem only, then routed my personal router to modem. When attempting to set up port forwarding on the Motorola device I have to write a new rule which allows me to select the port ranges which I set to 8096 , then application type with the choices of: FTP, DirectX Game, IRC, PPTP, SIP, or H.323. So my question would be what setting would describe Emby server best. Also there is a list of pre-created rules on the Modem yet none of these allow for the port number of 8096. I know this seems more like an ATT question, I have already contacted them multiple times and none of the Techs could help me with this set-up due to their lack of knowledge of Emby itself. Thanks in advance!

I have no idea where to start. I'm having some trenches dug out in the near future and having power correctly installed to the out buildings rather than a crappy bit of 2.5mm cable running overhead that the old owner ran. Anyway that was cut down and uninstalled the moment I moved in. However with these trenches dug, I will be laying water pipe, then some 10mm 3 Core Armored electrical cable in a sandwich of sand, then i thought i'd lay some network cable ontop of the sand. So I've ordered some pretty good shielded Cat6 (305m/1000ft) to lay ontop, but I will need a Gigabit switch to obviously distribute the network to the outbuildings. I was looking at an 8 port smart gigabit switch which would then feed wireless AP's inside them. I also need the network for CCTV and for audio/video intercom for the front gates when i get round to doing that. I'm shocking with networking, but could do with any help that one of you kind community members may be able to give. If you need more info or diagrams just shout. Cheers in advance

Port forwarding; an overview This is an overview not an in depth discussion of IPv4 networking The basic’s IP addresses have to be unique on a network if they are duplicated then data may not be delivered to its intended recipient. You could think of this like a postman delivering mail on your street, if there are two houses numbered 12 then which does he deliver mail addressed for number 12 too, probably the first number 12 they get to. Needing a unique IP address causes a problem. Due to the way IPv4 works there are simply not enough of these addresses available for every one or device in the world to have a unique IP address. To overcome this limitation of IPv4 two mechanism’s are employed 1. Network Address Translation (NAT). Translates public IP addresses to private ones and vice versa. More info here http://en.wikipedia.org/wiki/Network_address_translation 2. IPv4 addresses are broken into 2 types, termed a. Public, those which can be routed across the internet b. Private, those which can’t, your LAN NAT is a form of firewall. The fact we have to use NAT to overcome the limitations described above when connecting to the internet creates two separate networks, your LAN, which is private and the internet, which is public. This added layer of complexity does offer you a benefit; your first layer of security as nobody outside of your network can access it. Well not without help but that’s another topic. Now NAT is fine if you only need to translate one public IP to private IP address (1 to 1 mapping) or vice versa but what if you have multiple devices on your LAN? You would need one public IP address for each of the devices you needed to access the internet. Fortunately, NAT has another trick up its sleeve in the form of Port Address Translation. Port Address Translation is where a single public IP address, for this discussion, the one assigned by the ISP to your internet (WAN or outside) interface of your router is prefixed with a port number. This means that one public IP address could actually allow 65,536 private devices simultaneously access to the internet. It may simplify things to think of NAT like this. If your computer was out on the street then anyone with a mind too could just walk up to it and start using it. Not very secure. But take this computer and put it in a room with many closed doors (65,536 to be exact, each door individually number) which can only be opened from inside this room (port forwarding) and now you have a more secure computer. Port forwarding Port forwarding = Game & Application sharing As mentioned above port forwarding is the process of opening up a port (a uniquely numbered door) in your router (the room) to allow traffic to access your private network from the internet. For port forwarding to work you need several bits of information · Your WAN or outside IP address. This is the IP address on the connection, connecting your router to the internet. · The port number you wish to open · The IP address of the device on your network (LAN) which you want to forward traffic from the internet too The way in which you use this information to forward a port is down to the manufacture of your model of router but this site http://portforward.com/english/routers/port_forwarding/routerindex.htm is a good place to start if you aren’t sure. It has guides on how to port forward for many makes of router. Bare in mind these guides aren’t necessarily accurate. Further complications DHCP. Dynamic Host Configuration Protocol is designed to help us with IP addressing but in the case of port forwarding it can be a hindrance, Why? You set up port forwarding as shown below to map traffic from the internet hitting your outside IP address with destination port number 999 to be forwarded to a device on your network with IP address 192.168.0.1 listening on port 3389. Protocol TCP Outside Port 999-999 Inside Port 3389-3389 Inside IP 192.168.0.1 This works great then suddenly without warning it stops working! The reason. The device on your network with IP address 192.168.0.1 got this address via DHCP. When the DHCP lease is up this device requests another IP address but this time DHCP issues this device 192.168.0.13. Unfortunately, no one told the router of the IP change to 192.168.0.13 so the router is still trying to port forward traffic to IP address 192.168.0.1. To get this working again you would have to change the configuration setup in the router to match this new IP address as the original configuration is no longer correct. Static IP the way to go Luckily there is something you can do about this. Assign a static IP address to the device you need to port forward traffic to. Static in this context means it won’t automatically change. Now the way you accomplish this will depend on how you have your network setup and the equipment in use and isn’t covered here (in most cases your router will be a DHCP server) but there are two important things to remember when assigning static IP addresses. 1. Two devices can’t have the same IP address on the same network 2. When assigning static IP addresses on a network with an active DHCP server remember to configure the DHCP server NOT to use the IP address you have assigned statically. If you don’t you can end up falling foul of point 1 It’s round about here you remember your ISP saying something about them using DHCP to dynamically assign your Internet IP address. What’s that all about and won’t that cause the same problem we just discussed above? Again, this is DHCP at work. In the UK all ISP’s I’m aware of will assign a DHCP IP address to the Internet connection (WAN, outside interface) on your router. You can get Static IP’s but they’re not free. Yes, it will cause a similar problem as just discussed and again there are way’s around this, DDNS is one. Dynamic Domain Name Service (DDNS) is a way in which you can access from the internet a device on your network when you have a dynamic IP address on your routers internet connection, using a domain name. Unlike the previous problem with dynamic IP addresses and the issue with port forwarding rules dynamic IP address changes on the internet connection don’t affect the port forwarding rule. They affect the ability to contact your router from the internet. Generally this IP address doesn’t change frequently (unless you have technical issue’s) but it does change and again it won’t tell you. DDNS services (free or paid) work by assigning the IP address issued by your ISP to a domain name automatically. Your router, if it has the functionality or a client app monitors the internet connection for IP address changes. When it sees this change sends an update to your DDNS service so the domain name has the new IP address. This way when you use the domain name instead of an IP address to contact your router it will regardless of the fact your IP address changes. Do I need DDNS? Nope, but you will still need to know if your internet connection IP address has changed. You would then have to reconfigure any apps you use to use this new information. So it’ll probably easier to use DDNS. How to find my Internet IP address There are various ways to accomplish this and Google can help but this site is good http://whatsmyip.net/. Example Media browser 3, port forwarding Hopefully you now have a better understanding of what is needed to get port forwarding to work with your router or a better idea of what to search for on Google to find your answers but just to finish off here are the steps for configuring a widely used router in the UK, a BT home hub 2. 1. Open a web browser and type the IP address of your router. In this case the HH2 default IP 192.168.1.254 2. Login 3. You should now be on the home page. Click the Settings tab 4. Click advanced settings. 5. Click Continue to advanced settings 6. Click Application sharing 7. Click Supported Applications 8. Now Click Add new game or application 9. In the Game/Application name field name the rule, MB3 for this example but you are free to choose the name 10. Choose TCP for the protocol 11. Some routers like link Linksys have different pages whether you are configuring a single port or a range of ports. HH2 routers use the same page regardless. So just enter the same port number in both of the fields for Port range and Translate To. For MB3 the default port is 8096 12. Leave the other fields as they are, then Click Add 13. Click Apply That’s it, the port forwarding rule is configured. Now we have to bind the rule to the IP address of the device we want to reach from the internet (our MB3 server). 1. Click Configuration, to the left of Supported Applications 2. Click the Game or application drop down and find MB3 which we just created 3. Hop across to the Device drop down and either select your device (the one you want to reach from the internet) from the list or scroll all the way to the bottom and select user defined 4. A new field will be displayed called Device IP address. Enter the relevant IP address, then Click Add, then Apply That’s it your done configuring, now a basic test. Hang on; what about port 8945? Yes, I know we have only configured port forwarding for port 8096 and haven’t done the same for port 8945. The reason being is you only need port 8096 to access MB3 from the internet. From a device that is out in the internet (not on the LAN) fire up a browser and enter the following. If you have a functional DDNS service http://YourDDNSname:8096/mediabrowser/dashboard/login.html If not just use your Wan IP address http://88.123.1.11:8096/mediabrowser/dashboard/index.html If all is well you should see the MB3 Login page, if not you need to check the steps above and carry out some trouble shooting. Basic trouble shooting From a device on the internet or ask a friend, get to the command prompt on this computer and issue the following (Telnet is not enabled by default on newer operating systems so you may have to “install” it). Here we will just use the IP address to rule out issues with domain name resolution or DDNS. telnet YourWanIPAddress 8096 then press enter. If you don’t see a blank black screen with a flashing cursor (this means port forwarding is working) or get a message stating “couldn’t open a connection” then port forwarding for some reason is not working. This could be for many reasons such as · Windows Firewall · AntiVirus software with firewall capabilities · Port forwarding incorrectly set up Just whilst you are investigating the problem disable any of the above which may be running on the computer you are trying to reach from the internet and re issue the command above. Once it works you can re enable any of the above one at a time, checking with the above command and dealing with any configuration of these programs Final note Some routers such as those manufactured by Zyxel require a two stage configuration of port forwarding due to their more sophisticated functionality. The P-660HN-T1A may require you to disable the SPI firewall function under the security tab whilst AMG1202-T10A will require that you also create an IPMacFilter rule, found under filter, which is under the security tab. Another Final note Way back at the beginning of this long post you mentioned that NAT was a form of security, blocking un invited advances from the internet. Surely leaving ports open is a security risk? Well, yes and no. Whilst it is true that having ports open is a risk, I say no because the open port has to have an active program at the other end (a listener) for any hacker to take advantage of the fact we have opened a port. More than this there has to be known exploits within the program listening on the open port for them to exploit. So, it’s not really the fact the port is open which is the risk. Please remember, it is good practice to have all ports closed by default, only opening those ports which are needed, thereby minimizing the surface area for attack. Finally Bearing in mind you have now made your media collection available from the internet, by you. Use strong passwords. If you don’t, you may find others accessing you media from the internet too!