Emby/JellyFin playback not allowed

Emby/JellyFin playback not allowed

Emby/JellyFin playback not allowed
Emby/JellyFin playback not allowed
2025-06-27 13:03:57 - last edited 3 weeks ago
Model: Archer BE550  
Hardware Version: V1
Firmware Version: 1.1.2

Hi everyone/all,

 

I've purchased a BE550 as a precursor to upgrading to the BE900... to get a feel for how it runs, the app and GUI interface as well as making sure any of the features I wanted were locked behind their subscription service.

 

Having moved from an Asus ROG BE98 where nothing was paywalled I was surprised how much I liked this router, both for its wifi capabilities somehow reaching further or being stronger than my (supposed) more powerful deposed router and pleasently finding that IoT network, parental governance etc were at least deployable and only more advanced versions of these settings were part of their subscription.

 

My issue arises when my Emby server fails to play media. I can access the app on any of my devices it's installed on (windows, Nvidia shields, smart TVs and multiple tablets) but it won't play anything. When I go into the server from the GUI from my NAS manager it says the server is online, I can reboot it, edit libraries and generally manage it remotely so it's all reachable but actually clicking to play something just bring up an ever spinning loading wheel.

 

I've followed all the help in articles on Emby assistance, I manually added TCP ports 8096 and 8920 as well as UDP port 7349, I enabled UPNP and checked that I'd restarted the router after applying these settings, then rebooted the Emby server to make sure it loaded up based on these settings. All to no avail. No change, no matter what stage of making these changes I was at, it's worth mentioning at this point that I had NEVER had to configure my old router AT ALL to get Emby working.

 

It's a little concerning that when I tried to apply a static IP address to the NAS from within the TP-Link settings, I requested the IP address the server used to be on when it was connected to the BE98 router, it would never actually apply it though. That's weird, right? I checked for IP conflicts but there were none... so I'm at a loss to explain that anomaly but based on the fact that on any of the devices I've installed Emby player on, it still sees the server regardless of whatever IP address it's got. So for that reason, I have not contacted Emby support as I don't believe it's their issue. It seems squarely at the feet of TP-Link.

 

I tried installing a Jellyfin server, adding media, and this too was discoverable on a Jellyfin player installed on a couple of devices. Logged in, brings up the library, I can effect that library's metadata or even delete it from the library but when I went to play something I was even more surprised to learn that this didn't play either.

 

I have a good enough understanding of networking and router configuration that I've not changed any settings unbeknownst to me or unwittingly deactivated something naively but I'm looking to get this resolved quickly so any and all input/advice would be most welcome especially if you've experienced the issue before because I'm dumbfounded! Never had to do any of this on any of the routers I've owed, and I've moved from Plex to Jellyfin to Emby across multiple routers and upgraded NAS systems over the years.

 

Thank you in advance

  0      
  0      
#1
Options
4 Reply
Re:Emby/JellyFin playback not allowed
2025-06-27 18:32:19

  @ArmageddAdam 

 

Problem solved... Turns out the reason it wouldn't assign the IP I wanted was because I was already in use (no popup or alert to say so) and even though I'd checked for no conflicts in my Network Map, there's another list in the advanced settings called the DHCP Client List... This showed 3 devices not even listed in my Network Map!

 

So I tracked down the offending device (thank God I'm geek enough to keep a log of all MAC addresses in my home) which was an IP Camera, then turned it off. I actually set the static IP from within my NAS' web GUI and then restarted my router to allow it to release the IP address from the previous device.

 

Lo' and behold, it all worked within minutes and I'm once again able to play content on EMBY. None of this explains why EMBY wouldn't work on any given IP as it should, nor why TP-Link have 2 lists of your connected devices and one shows clients that the other doesn't.

 

If either company sees this, then please action those points in earnest and save other users facing a lot of issues, granted this thread received zero replies but it shouldn't have been an issue in the first place really.

 

Hope this helps others in the future???

  0  
  0  
#2
Options
Re:Emby/JellyFin playback not allowed
2025-06-27 19:50:50

  @ArmageddAdam 

 

Hi,

 

I agree that it could be helpful if the GUI notified the user when an IP address that is currently in use by another device is entered into the "Add a Reservation Entry" dialog box. 

 

By the way, the "DHCP Client List" shows "devices that are currently assigned with IP addresses by the DHCP server", just like it says right above that list. That does not imply the devices in that list are currently "connected".
Clients that are currently "connected" are shown in the "Clients" list in the Network Map menu.
So the two lists serve two different purposes.

 

  0  
  0  
#3
Options
Re:Emby/JellyFin playback not allowed
2025-06-27 20:13:07

  @woozle 

 

Thank you for the clarification but by that logic the device would have been in both lists as it had been assigned an IP address AND was currently connected to the router, but it wasn't in the Clients list, only the DHCP one.

 

So the issue may not have been 'why have two lists if they show different info' as I'd incorrectly perceived but nevertheless raises the issue 'why are devices that are connected not populating the clients list'

  0  
  0  
#4
Options
Re:Emby/JellyFin playback not allowed
2025-07-01 10:56:06

Hi@ArmageddAdam ,

Welcome to our community.

 

You mean the IP that was supposed to be assigned to the Emby server was already occupied by the camera, right?

Although the camera is running correctly, it is only displayed under the DHCP clients list as an unknown device. The Connected devices list under the Network Map does not show the camera device, right?

 

If I understand your question correctly, we can basically determine that the display of the clients' list may have some problems.

The tech team has been made aware of your issue; they will likely reach out to you via email to continue troubleshooting. Please check your email inbox and confirm.

  0  
  0  
#5
Options