Jump to content

Recommended Posts

Radtech81951
Posted

I've been using Emby for several years now with little to no issues. I recently switched to Google Fiber over the winter, and had no problems at all. I run my server on a windows PC, and did not have port forwarding setup after the ISP change. No issues at all for anyone connecting. As of about a week ago, no one can connect outside of my network including myself. I setup port forwarding for all 3 ports per the Emby help instructions. 2 on TCP and 1 on UDP. I also created inbound rules for all 3 ports and the embyserver.exe. My windows profile is also set to private. I tried to use canyouseeme.org, and it says there's "no route to host" on any of the 3 ports. There's no vpn or virus protection that would be interfering and I even turned off the firewall briefly, but still no luck. I also read somewhere that some have experienced issues after recent windows updates, so I uninstalled all that I could, but still nothing. Can anyone help? I didn't manually change anything before the issue started. I'm fairly tech savvy, but by no means close to an IT pro. So if you have any technical suggestions, please dumb it down a little. TIA

Radtech81951
Posted

Just restarted my router, and could connect from my phone without wifi. I closed Emby and tried again, and no luck.

visproduction
Posted

Is the IP address for your server reserved on your router?  If it isn't, your DHCP could assign the IP address to any other local WIfi user and then the server gets a different IP, the next time it starts.  Reserving the IP address on the router would fix that.  I believe Emby setup includes a step to make this work.  Each router is different.

Example info:
 https://duckduckgo.com/?q=linksys+reserve+and+IP+address&ia=web

Posted

Also @Radtech81951please step through our Connection Troubleshooter:

Connecting from Client Apps

Please try the steps listed there and let us know which ones succeed and which ones do not. Thanks !

Radtech81951
Posted

@LukeI have tried all of those steps, and even recently did a factory reset of my PC that my server is connected to, and I still cannot connect. 

@visproductionIn the google 6e router it forces you to reserve and IP in order to do UPNP port forwarding.

  • Like 1
Posted
2 hours ago, Radtech81951 said:

@LukeI have tried all of those steps, and even recently did a factory reset of my PC that my server is connected to, and I still cannot connect. 

@visproductionIn the google 6e router it forces you to reserve and IP in order to do UPNP port forwarding.

Can you show us how you setup port forwarding?

NeverExists
Posted (edited)

A few people are having this same issue. At least 4 people, so the problem is not on our side. There are 2 other threads on this issue that the Emby team abandoned, thinking the issue was on our end, even though I explained that I tried everything in their guide and never heard back from them, so don't hold your breath. nothing will be done about it until the Emby team stops blaming our setups for the issue and actually takes it seriously and looks at the code. The reason I'm saying this is cause I brought it up in 2 other people's threads and even my own thread, and was ignored on that issue. btw guys, hmmmm, before the update, it was working, then after the update, not working, so it kind of looks like it's on Embys ' end. Also, btw, I have been using Emby for 8 years and have never had to open my ports, but just for peace of mind, I tried everything in their guide,, and nothing worked.

Edited by NeverExists
  • Disagree 2
pwhodges
Posted
7 hours ago, NeverExists said:

A few people are having this same issue. At least 4 people, so the problem is not on our side. 

There are also hundreds of people who do not have this issue, so it not as easy as saying "it's on Emby's end".  Even if it is something in Emby that could be changed to work better in your environment, there is still the need to find out what is different in your cases.  It's hard to know even what questions to ask; but answering those which are is at least a step.

Paul

  • Agree 5
Neminem
Posted (edited)

I for 1 don't have connection issues 🤷‍♂️

Its always something in the server admins setup that's not setup right.

Or has not been done.

Edited by Neminem
  • Like 1
  • Agree 3
RanmaCanada
Posted

Been running Emby for a decade now..never had issues with outside connections. Every time someone has had an issue in the forums it has always come down to a problem at their end. Router could not be opening ports, ISP could be blocking traffic, CGNAT messes, etc.

  • Agree 2
dcook
Posted

Been running Emby since 2015, and I also never had an issue with external connections, many ISP's are using CGNAT now, so its not as easy as it used to be with simply opening a port.

Basic understanding of Networking is important to make sure you run things securely, otherwise you just open ports and get hacked.

  • Like 1
  • Agree 1
  • 4 weeks later...
Radtech81951
Posted

@LukeSorry for the delay. It's been a crazy few weeks. So somehow I was able to get the port open and have verified it using canyouseeme.org. I have no idea how. I did try using bridge mode on the router that google fiber provided. I connected it to my Netgear R9000 that I used previously. When I did that, I was able to connect remotely. And I don't even have port forwarding set up on the old router. The only issue is that the r9000 is a 1g speed router, and my google fiber plan is the 3g so I'm losing a lot of what I'm paying for. So I disabled bridge mode and went back to just my google fiber router. I also purchased a 2.5g network switch to see if I could run both routers from the connection coming from my modem, but neither would work at that point. So I went back to just the google router again. After all that I finally was able verify the port was open. But I was still unable to connect remotely. I've attached screenshots of my port forwarding on my router and my firewall settings. 

port forwarding fiber.png

firewall emby.png

visproduction
Posted

What are the Allow    No  colunns.  Should that perhaps be Allow Yes?

js28194
Posted (edited)

Having the device in DMZ negates any port forwarding at the router level.  Windows Firewall would still be needed and need "Allow" to yes  Best to better understand your external IP address (I understand you don't want to share).  The device is in DMZ so your "remote" apps only need your EXTERNAL ip + port.  

 

I do not recommend ANY server be in DMZ, but that's just me.

Edited by js28194
  • Agree 1
js28194
Posted

Oh, but router Firewall still applies if you insist on using DMZ.  Again, super not recommend.   Opening port 8096, and 8092 on your Router Firewall... and whatever your 7359 is??  I think you aught to take a step back and determine your network configuration and start from ground up.

  • Agree 1
js28194
Posted

If and big IF, you get rid of your Netgear (do this for testing) and just using your Google Fiber thingy... (ONT) then in that, remove the specific IP address of your EMBY server from DMZ.  Then port forward 8092/8096 TCP/UDP to your Emby Server IP address (192.168.10.104).  

Make sure your Windows Firewall allows INBOUND (just do both for now) for EMBY on 8096/8092 TCP/UDP.  Save hit Save, probably hit save again everywhere.

Then on your phone in the Emby App, disconnect from WiFi and add a server.  Use your EXTERNAL ip address (you Google assigned) ip address and port 8096.

That should get you over the hump.  Then come back and re-evaluate your network, because this not the way most long timers would recommend but it "should" work.

js28194
Posted
On 5/27/2026 at 12:22 AM, NeverExists said:

A few people are having this same issue. At least 4 people, so the problem is not on our side. There are 2 other threads on this issue that the Emby team abandoned, thinking the issue was on our end, even though I explained that I tried everything in their guide and never heard back from them, so don't hold your breath. nothing will be done about it until the Emby team stops blaming our setups for the issue and actually takes it seriously and looks at the code. The reason I'm saying this is cause I brought it up in 2 other people's threads and even my own thread, and was ignored on that issue. btw guys, hmmmm, before the update, it was working, then after the update, not working, so it kind of looks like it's on Embys ' end. Also, btw, I have been using Emby for 8 years and have never had to open my ports, but just for peace of mind, I tried everything in their guide,, and nothing worked.

I know this is an older post... but sigh.  Maybe a charge for a basic networking 101 class?  Of course not, we offer our time for free, but these kinda statements are strange.  It's always the code... be careful what you wish for if you want the code to take total control over your network and automagically do everything for you.  Maybe Emby team put a basic networking 101 tutorial?  I don't think they should.  Basic network administration tutorial on how to setup shares and permissions?  I think not.  Linux... well don't even go there if you don't know basic BSD nor Ubunutu.... Some self discovery is in order, but I digress.

Damn.... I sound like a cranky old man.

  • Haha 1
Neminem
Posted (edited)

@js28194Trust me you are not, but as G'N'R said

"Some men you just can't reach..."

Edited by Neminem
yocker
Posted (edited)
41 minutes ago, js28194 said:

If and big IF, you get rid of your Netgear (do this for testing) and just using your Google Fiber thingy... (ONT) then in that, remove the specific IP address of your EMBY server from DMZ.  Then port forward 8092/8096 TCP/UDP to your Emby Server IP address (192.168.10.104).  

Make sure your Windows Firewall allows INBOUND (just do both for now) for EMBY on 8096/8092 TCP/UDP.  Save hit Save, probably hit save again everywhere.

Then on your phone in the Emby App, disconnect from WiFi and add a server.  Use your EXTERNAL ip address (you Google assigned) ip address and port 8096.

That should get you over the hump.  Then come back and re-evaluate your network, because this not the way most long timers would recommend but it "should" work.

I would remove any Netgear from my network.
I believe it was Wendell from Level1 Tech that discovered that they have major backdoors in their routers.
 

 

Edited by yocker
  • Sad 1

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...