ChuckGB 0 Posted February 2, 2025 Posted February 2, 2025 Replaced the Fire TV cube in my Living room with a new one, and can't get the Emby App on this cube to connect to the server (running on a Synology NAS); no matter what, it says "Unable to Reach Server; We're unable to connect to the selected server right now. Please ensure it is running and try again." Some notes: The IP hasn't changed in 10 years with my internal network setup. It's the same IP that the last cube was connecting with just fine. Its the same App I was using on the old cube, the one titled "Emby for Fire TV" Every other device (phone, laptop, computer, fire TV stick in a different room etc) is able to connect with this IP address. The server is running. I haven't changed ANY configuration settings. For kicks I tried using the WAN IP, and got the same result. When I use the PIN with Emby connect, I get a screen that gives two options, exit emby connect or enter IP manually (which as we've established, doesn't work." The cube is seeing everything else on the network (I was steaming a PC game with Steam Link with no problem). I'm out of ideas on this one. I've changed nothing on the server end and everything else is connecting no problem.
ChuckGB 0 Posted February 2, 2025 Author Posted February 2, 2025 Edit to previous - It's now finally able to see the server, through Emby connect, but now it says that The server is unavailable and cannot be reached (gives options of Cancel/Wake/Remove). Similar to previous, no issues connecting on other devices.
ebr 16169 Posted February 2, 2025 Posted February 2, 2025 9 hours ago, ChuckGB said: with my internal network setup 8 hours ago, ChuckGB said: able to see the server, through Emby connect Hi. Why are you using Connect on your internal network? The fact that the server isn't presented automatically as a login option in the app indicates a network discovery issue. Something is blocking access on the device. Any VPN or proxy?
ChuckGB 0 Posted February 2, 2025 Author Posted February 2, 2025 1 hour ago, ebr said: Hi. Why are you using Connect on your internal network? The fact that the server isn't presented automatically as a login option in the app indicates a network discovery issue. Something is blocking access on the device. Any VPN or proxy? Mornin! I only used Connect because I kinda had to. When I entered in the server address manually, it gives me an error message. or did nothing at all. No VPN running on my router, no proxy. So here's my dashboard info: Which Leads to this on my TV: And after hitting OK, it just sends me back to this screen and 15-20 minutes later, it says Error connecting. Not sure if it's a configuration issue on the server (which is confusing to me, as every other device is seeing it without problem) or an issue with the app itself. Ive also tried deleting and reinstalling the app for good measure.
ChuckGB 0 Posted February 2, 2025 Author Posted February 2, 2025 As for using connect, When I do the PIN thing, it at least gets me to here, where the server is at least showing up: Try to select that server and I get this: Wake doesn't do anything and removing to start the process over again similarly isn't working. Th only way I can get to these screens is using Emby Connect (which I've never had to do on any of my other devices)
ChuckGB 0 Posted February 2, 2025 Author Posted February 2, 2025 Last thing - I tried connecting via the Fire TV's Browser (silk) and it also won't connect - so it makes me wonder if this is a known issue with the 3rd gen fire tv cube, or if this is an indicator that I have a defective unit?
visproduction 315 Posted February 2, 2025 Posted February 2, 2025 I think the new FireTV Cube is connecting immediately through to an outside gateway and outside domains and IP address? Try setting the gateway address in the Fire TV Cube setup to your router IP gateway. This will give the router a chance to recognize that the 192 address is on the internal network.
ebr 16169 Posted February 3, 2025 Posted February 3, 2025 Hi. Emby Connect has no "magic" in it as far as making network connections. That is, if you cannot make a connection using the direct IP address, then Connect won't be able to either. All that means that there is a basic network connectivity issue between your Fire and your server. The Fire cannot see your server for some reason.
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