Emby Connect not working after changing to wifi

[dillontest1 2]

Hi -

I've been using Emby w/ Premier for about a year with zero issues. Today I built a new main PC and moved my existing PC/Emby Server to a wifi connection and no longer hardwired. This has caused all emby connect users to no longer connect. I have read at least two dozen threads here and other sites online with no silver bullet. 

I still have full access locally on any app on any device/tv. 

 

Things I have tried so far - 

Checked port forward that I did not need to setup previously, but I've since added it just in case for both http and https

 

 

• Switched the wifi network from public -> private and back a few times, no change. 
• verified public ip on https://www.whatismyip.com/ and canyouseeme.org
• Disabled firewall on wifi connection
• Created my own emby connect account that sees the server but will fail to connect via https://tv.emby.media/  or    http://tv.emby.media/
• restarted emby server and machine several times
• using my LAN IP/port via new PC's browser and it connects to emby immediately
• using my WAN ip/port via new PCs browser and it fails (i dont know if this should work)
• using my WAN ip/port on mobile phone (no wifi) it fails
• tried both IPs in emby mobile phone app (no wifi) both fails
• mobile phone app (no wifi) sees server after using emby connect but won't connect

 

embyserver.txt

 

thanks for any help you can provide. I do not want to rebuild the emby server but i'm afraid that's what might be next. 

 

[Abobader 3464]

Hello dillontest1,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[ebr 16169]

Hi.  Your issue is not with Connect.  It is with your remote access setup.

7 hours ago, dillontest1 said:

Checked port forward that I did not need to setup previously, but I've since added it just in case for both http and http

This is always needed.  Before, it was probably just created for you automatically.  This is likely where your issue is as the forwarding does not appear to be working:

7 hours ago, dillontest1 said:

 

 

7 hours ago, dillontest1 said:

using my WAN ip/port via new PCs browser and it fails

If this fails, so will Connect.

So you need to figure out why your port forwarding isn't working.

8 hours ago, dillontest1 said:

Switched the wifi network from public -> private and back a few times, no change

The network definitely needs to be set to private.  Most wifi networks will default to public and this won't work.

[dillontest1 2]

22 minutes ago, ebr said:

Hi.  Your issue is not with Connect.  It is with your remote access setup.

This is always needed.  Before, it was probably just created for you automatically.  This is likely where your issue is as the forwarding does not appear to be working:

 

If this fails, so will Connect.

So you need to figure out why your port forwarding isn't working.

The network definitely needs to be set to private.  Most wifi networks will default to public and this won't work.

 

Thanks for your reply. I never imagined it was Connect causing the issue, but because my connection changed. When you say 'it was created for me automatically' how would that change by moving the machine from hardwire to wifi if the router wasn't forwarding anything prior to that? That's what was stumping me because, it does seem like an inability to reach the machine but nothing changed there. 

This was always enabled, but after this hiccup is when I added the single port forward rules. 

 

I checked the windows defender firewall rules as well;

 

 

 

I've confirmed the wifi connection on the machine is using private, ensured that the port forwarding rules are setup for that machine/ip and those two ports. Anything else worth trying? 

 

Edited August 22, 2025 by dillontest1

[Neminem 1518]

Check your routers wifi part and see if its set to block access to other clients on your network.

In my router the is called "Client Device Isolation" 

In your router it might be called something else, like AP isolation.

But its best to look in the manuel of your router.

[dillontest1 2]

Just now, Neminem said:

Check your routers wifi part and see if its set to block access to other clients on your network.

In my router the is called "Client Device Isolation" 

In your router it might be called something else, like AP isolation.

But its best to look in the manuel of your router.

It does not appear that my google fiber/wifi modem/router has this setting. It also is an issue outside of my network entirely. 

[Neminem 1518]

I'm not a windows firewall expert, but only direction inbound ?

I would expect it to go both ways.

[dillontest1 2]

3 minutes ago, Neminem said:

I'm not a windows firewall expert, but only direction inbound ?

I would expect it to go both ways.

All the items in there are inbound, with no way to add another direction from what i can tell. 

[ebr 16169]

Are you sure the router will route outside traffic to a Wifi address?

Have you ensured that device will always have the same IP address?

[dillontest1 2]

4 minutes ago, ebr said:

Are you sure the router will route outside traffic to a Wifi address?

Have you ensured that device will always have the same IP address?

I don't know how to validate that it will route outside traffic to a wifi device. I'm digging into other google/fiber related posts now. That might be it.

It does have a reserved ipv5 address due to the forwarded port rules.

 

Also, wouldn't the outside networks still be successful? It's not like anything on the network changed and the ports should still be accessible using these test sites.

 

 

Edited August 22, 2025 by dillontest1

[dillontest1 2]

20 minutes ago, ebr said:

Are you sure the router will route outside traffic to a Wifi address?

Have you ensured that device will always have the same IP address?

 

I think this is the issue. the router won't route outside traffic to a wifi address. I looked on my new machine and the hardwire connection was set to public, after changing this to private it will see the port open. 

I have those manual rules enabled for the wifi connection/device ip. Next step is to disable auto upnp port forwarding and see if only having the manual rules route the connection to the right spot. 

 

[dillontest1 2]

To wrap this up, it must have been the new PC set to Public on the Ethernet connection causing the issue. Once I moved this to Private and checked the port was open it started working a few minutes later after a machine reboot. After setting the new hardwired connection to private it appears to be letting the traffic all the way to the wirelessly connected emby server for all external/internal users. 

 

I didn't turn off auto UPnP or make any other rule changes or adjust anything on the server.

 

The connection from this internal PC to the external WAN still fails though. There must be a limitation on connecting back to your own external IP that i cant change. 

Edited August 22, 2025 by dillontest1

[dillontest1 2]

i wanted to add an update and maybe help someone in the future. 

i removed my port fwd rules in my google fiber router and when i went to readd them with the server 192.x.x.x IP it wouldn't work. after a lot of troubleshooting i determined that google would only successfully forward if you choose the device from the list, not by providing the IP. 

for some reason my server had a ghost connection and was showing two connected devices, I renamed the one with the correct local IP to be more unique, set the forward rules to that and it worked instantly. 

[Luke 42077]

Thanks for following up.