moonstone238 1 Posted May 23, 2019 Share Posted May 23, 2019 (edited) So I am sure I am missing something silly, but I am pulling my hair out trying to figure what it could be. I have emby set to allow remote connections, SSL setup correctly, and have zero issues connecting via multiple android phones, a couple ipads, and laptops from remote locations. Everything is great. Except for my parents Fire TV. I was trying to set it up for them earlier, and no matter what I did, no dice. I tried emby connect, as well as manually putting in the server address using multiple iterations. I.E. https://thisismyserver.com and the port number in the port number section. I also tried https://thisismyserver.com:port and leaving the port number blank in the emby app. Emby connect also gets me nowhere. I can log in using the pin, but as soon as I hit next, there is no server listed. I spent an hour messing with it, while watching a movie on my laptop next to me remotely. What am I missing? I am using SSL via cloudlfare.com. Windows 10 server. Ports forwarded correctly. Only thing not working is remote fire TV. Edited May 23, 2019 by moonstone238 Link to comment Share on other sites More sharing options...
moonstone238 1 Posted May 23, 2019 Author Share Posted May 23, 2019 I ended up figuring this out once I got back home and threw my own fire TV on a hotspot. All I had to do was put in my server address, and do nothing port related. -Add server manually - In the server address, just https://thisismyserver.com -In the port section, delete what was there and leave it blank -Hit connect. - ....... - Profit. I now have emby working on every device in my house, including remote access so I can watch from work, and my parents can access my media as well. So long Plex, it was real. Link to comment Share on other sites More sharing options...
ebr 14959 Posted May 23, 2019 Share Posted May 23, 2019 Hi. I'm glad you figured this out but I'm not sure why it had a problem before. What is the external port for your server? Link to comment Share on other sites More sharing options...
Solution moonstone238 1 Posted May 27, 2019 Author Solution Share Posted May 27, 2019 I route everything through cloudflare. I ended up figuring out that cloudflare only forwards certain ports. So even on my router when I was forwarding the emby ports correctly, cloudflare doesnt allow that port to forward. Once I forwarded a port that cloudflare allows for https to the correct emby port on my router, the problem was solved and everything works perfectly. I ended up forwarding port 8443 on my router to the correct emby port. Just in case anyone else runs into this and sees this, below are the ports cloudflare allows traffic on. HTTP proxyingCloudflare can proxy traffic going over the HTTP/HTTPS ports listed below. If your traffic is on a different port, you can add it as a record in your Cloudflare DNS zone file as something we don't proxy (gray cloud = no Cloudflare proxy or caching on a record). The HTTP ports that Cloudflare support are:80808088802052208220862095 The HTTPs ports that Cloudflare support are:44320532083208720968443 1 Link to comment Share on other sites More sharing options...
Luke 37242 Posted May 28, 2019 Share Posted May 28, 2019 When you did enter a port on the server connection screen, what values did you try? Leaving it blank should be the same as if you had entered the default port. 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