Luke 37068 Posted February 10, 2016 Share Posted February 10, 2016 Thanks Luke, I've looked at that website and tried everything it explains. I've tried the port forwarding and I believe I did it right. Is there a way too check that? yes there is. after making your changes, go through the "Test Your External Address" section again. Link to comment Share on other sites More sharing options...
briansmi1116 0 Posted February 10, 2016 Share Posted February 10, 2016 I tried to go through the steps again and I still can't tell if the port is open to the net. I'm not very good with networking. I did the port forwarding and I've tried other steps I found online. I still cant connect to the server and I don't know why. Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 10, 2016 Share Posted February 10, 2016 http://www.yougetsignal.com/tools/open-ports/ Put there your external IP (or url, if you have a domain), fill the port and you will immediately know if your port is open or not to the world. 2 Link to comment Share on other sites More sharing options...
briansmi1116 0 Posted February 10, 2016 Share Posted February 10, 2016 I put in the external ip and the port 8920 in on that evite and I can't access it. I even try the remote address that emby says to use and it won't access it. Link to comment Share on other sites More sharing options...
ebr 14913 Posted February 10, 2016 Share Posted February 10, 2016 I put in the external ip and the port 8920 in on that evite and I can't access it. I even try the remote address that emby says to use and it won't access it. Then it is a problem with the router or firewall setup (assuming Emby server is actually running). You'll need to solve that before you will be able to access Emby with any app. Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 10, 2016 Share Posted February 10, 2016 Brian, you still haven't answered if you're trying to access from a browser or an app (android, ios, etc...) I repeat: if you are using HTTPS (8920), only browser should work, for now. 1 Link to comment Share on other sites More sharing options...
ebr 14913 Posted February 10, 2016 Share Posted February 10, 2016 Yeah, you should check 8096 with canyouseeme... Link to comment Share on other sites More sharing options...
briansmi1116 0 Posted February 10, 2016 Share Posted February 10, 2016 I've tried browser and the app.both have connection issues Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 10, 2016 Share Posted February 10, 2016 Tried all major browsers? As the known https issue is caused by certificate not being trusted, it also depends on the browsers trusted list. And... Did you create your custom certificate or are you relying in the self-signed that emby creates? If the 2nd, it probably will never work in external networks Link to comment Share on other sites More sharing options...
Luke 37068 Posted February 10, 2016 Share Posted February 10, 2016 Many of the apps still have work to do in relation to https, so please perform your testing with http for now to confirm the server is accessible. thanks. 1 Link to comment Share on other sites More sharing options...
Tur0k 143 Posted February 11, 2016 Share Posted February 11, 2016 (edited) I just updated my emby Server to the latest version (3.0.5807.0) and tested again. On the Emby Connect page, after signing into emby.media. I can log in with my credentials (https://app.emby.media/selectserver.html) I can select "Add Server". if I set the host to https://<myDNS.com and the port to 8920 I am now able to connect to my environment. I have blocked port 8096 once again on my Router, and everything is still working!!! thank you much. one last question, do I need to have TCP, UDP, or both types of packets allowed to pass through my router on port 8920? I have now found that I must allow TCP 8096 through on my router for emby connect (http://app.emby.media/, or https://app.emby.media/) to keep the server available. Not entirely sure why this is, but it is a minor problem. Edited February 11, 2016 by Tur0k Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 11, 2016 Share Posted February 11, 2016 Hey Tur0k believe me when I say opening 8096 is not mandatory. Mine works only with https. So performing opened ports test confirmed it's opened and you still can't connect? Have you configured a custom pfx (with .pem chain inside)? In other topic another user taught how to do it 1 Link to comment Share on other sites More sharing options...
Happy2Play 8282 Posted February 11, 2016 Share Posted February 11, 2016 Hey Tur0k believe me when I say opening 8096 is not mandatory. Mine works only with https. So performing opened ports test confirmed it's opened and you still can't connect? Have you configured a custom pfx (with .pem chain inside)? In other topic another user taught how to do it Well what ever port you are using for the server has to be open. So if you able to use 80 or 443 without issue then of course you don't have to open an additional port. 1 Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 11, 2016 Share Posted February 11, 2016 I only had to open port 8920 Link to comment Share on other sites More sharing options...
Tur0k 143 Posted February 11, 2016 Share Posted February 11, 2016 (edited) I have found that if I am using the Emby app on an IOS (iPhone/ipad/appletv) or android device, I believe that it is allowing the connection via the emby connect service. in order to get those devices to work I suspect that a user will likely need: 1. An Emby connect account. 2. an unchanging IP Address assigned to the computer that you have Emby Server installed on. this can be done by: a. Statically assigning an IP address on the computer (http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/)that you have Emby server installed on. note: if you statically assign an address that is within your DHCP IP address pool that your home network uses then the IP address can be assigned inadvertently to another device on your network. to avert this choose an IP address for the Emby Server computer at the end of the DHCP IP address pool (and if you can, adjust the pool size to exclude it from being used). b If your home network Router/gateway supports it, you could DHCP reserve an IP address for the computer that you have Emby server installed on. that way every time that computer connects to your home network it would be assigned the same IP address. 3. Windows Firewall on the computer that you have your Emby server installed on will need to be configured to allow inbound TCP traffic on ports 8096 and 8920. these rules should be added when you install Emby server, but if they didn't, or may have been turned off open a command prompt and type the following: netsh advfirewall firewall add rule dir=in name="EMBY Inbound 8096 TCP" action=allow enable=yes profile=any localport=8096 protocol=TCPnetsh advfirewall firewall add rule dir=in name="EMBY Inbound 8920 TCP" action=allow enable=yes profile=any localport=8920 protocol=TCP 4. your home network router/gateway will need to be configured to pass all inbound TCP traffic on ports 8096 and 8920 to the IP address used for the computer that you have Emby server installed on. I have found that you have to have inbound TCP communications on both ports 8096 and 8920 allowed through your router for Emby Connect/IOS app/Android/ apps to work. 5. often many ISP providers will change your external IP address. This means that when you could connect to your house network on day 1 at http://28.23.73.223:8096, after your IP external address is changed by your ISP on Day 16 your new address could be http://28.23.73.224:8096. http://28.23.73.223:8096 would then not work. While you could pay your ISP for a Statically assigned External IP address this often costs a great deal, there are dynamic DNS services who allow you to reserve a domain name (ex: myhouseVA.ddns.net) and will provide you with a program (that can be setup on your computer, or possibly even on your home network router/gateway) that will allow you to update your external IP address automatically. You would only have to remember http://myhouseVA.ddns.net:8096 to gain access to your Emby server. Edited February 11, 2016 by Tur0k Link to comment Share on other sites More sharing options...
Luke 37068 Posted February 11, 2016 Share Posted February 11, 2016 Emby Connect doesn't do anything to bypass port forwarding requirements. Link to comment Share on other sites More sharing options...
Tur0k 143 Posted February 11, 2016 Share Posted February 11, 2016 (edited) Hey Tur0k believe me when I say opening 8096 is not mandatory. Mine works only with https. So performing opened ports test confirmed it's opened and you still can't connect? Have you configured a custom pfx (with .pem chain inside)? In other topic another user taught how to do it I have confirmed that 8096/8920 are open by using http://www.yougetsignal.com/tools/open-ports/, I use a DHCP IP reservation to ensure that my Emby Server always receives that same IP address on my internal network and I currently have port forwarding setup on my router to forward 8096 and 8920 to my Emby Server Computer. Oddly enough Emby Connect will allow me to add my server from a computer inside my network just fine when only port 8920 is open and port forwarded on my router to my emby server's internal IP address. I won't be able to connect to that saved server in my emby connect account if I, for example, log into emby connect from work and attempt to log into my emby server. I generally just open a browser, bypass the SSL warning and navigate to https://mydomain.pointto.com:8920 and view my server directly instead. When I setup port forwarding on 8096 and point it to my Emby server's internal IP address, I am able to setup emby connect and can connect to my emby server using the Secure host and port settings (Host: https://mydomain.pointto.com and port 8920). I am then able to connect to my Emby server using emby connect from home or my office. I will check out the custom pfx (with .pem chain inside) and get back to this thread on it. Edited February 11, 2016 by Tur0k Link to comment Share on other sites More sharing options...
anderbytes 139 Posted February 12, 2016 Share Posted February 12, 2016 I have confirmed that 8096/8920 are open by using http://www.yougetsignal.com/tools/open-ports/, I use a DHCP IP reservation to ensure that my Emby Server always receives that same IP address on my internal network and I currently have port forwarding setup on my router to forward 8096 and 8920 to my Emby Server Computer. Oddly enough Emby Connect will allow me to add my server from a computer inside my network just fine when only port 8920 is open and port forwarded on my router to my emby server's internal IP address. I won't be able to connect to that saved server in my emby connect account if I, for example, log into emby connect from work and attempt to log into my emby server. I generally just open a browser, bypass the SSL warning and navigate to https://mydomain.pointto.com:8920 and view my server directly instead. When I setup port forwarding on 8096 and point it to my Emby server's internal IP address, I am able to setup emby connect and can connect to my emby server using the Secure host and port settings (Host: https://mydomain.pointto.com and port 8920). I am then able to connect to my Emby server using emby connect from home or my office. I will check out the custom pfx (with .pem chain inside) and get back to this thread on it. Tur0k, to ensure that you are really using HTTPS, disable port forwarding to 8096. That's the ONLY way you'll ensure that emby connect app is not falling back to HTTP port after HTTPS fail. Notice that this "bypass SLL warning" should not exist if you want to access Emby remotely. You need to use a worldwide valid SSL , download the PEM chain of the Certification Authority, and create the PFX based on the generated keys (public + private), plus the PEM chain. This "overpowered" pfx file has everything needed so your webserver can be fully recognized as a trustable server in the internet. This is what will be referred inside Emby SSL path. If ANY of those requirements is not done correctly, probably your Emby won't allow connections. TIP: I created my SSL Certificate in Let'sEncrypt. It's free and lot's of people are migrating to it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now