topic Re: Can't allocate fixed IP to connected device in Broadband

Connected Devices not showing on MySky

Caramon — Sat, 14 Mar 2026 10:21:27 GMT

Just switched back to Sky Broadband (full fibre superfast 500). Had a weird issue when trying to set up a port forwarding rule for my Plex media server, which essentially crippled wi-fi. stopped me logging into the admin screens on my laptop, and it refused to reset back to default settings until we cut the power for a few minutes, rebooted and then held WPS for 30+ seconds. Then it reset back to default settings.

So there's the context. Start of full day #1 back with Sky having just had to reset the system this morning. In trying attempt #2 to set up a port forwarding rule for my Plex media server (for remote acess), my Plex box - an old WD MyCloud Home - shows up in the admin screens on my computer as a 'connected device' but it doesn't appear on 'MySky' when trying to create the port forwarding rule.

Assuming I can get this to appear again (as it did appear earlier before the whole system decided to have a hissy-fit), I'm not 100% sure if I need to configure port-triggering as well, or instead of port forwarding?

Any pointers gratefully received!

Re: Connected Devices not showing on MySky

Caramon — Sun, 15 Mar 2026 09:39:15 GMT

I'm not able to get the connected device to show up on the MySky app when it does show up if I login as admin on my computer. Anyone got any tips or suggestions on how to force it to refresh on the app? If I can't get it to show, then I can't add the port forwarding or port triggering rule (which I am also none the wiser on which of those two I should be using)?

Thanks,

Re: Connected Devices not showing on MySky

JimM1 — Sun, 15 Mar 2026 10:53:11 GMT

@Caramon As you used the WPS reset method, have to assume you are sky Max (White) hub, so once the hub is onboarded to sky at the connection which can take a few day's to all gell together the MySky app is the way to do it all, the web manager interface to the Hub get's all shut down!

Sky Max change settings link.
https://www.sky.com/help/articles/change-wifi-max-hub-settings-a

Re: Connected Devices not showing on MySky

ItWasAllMichele — Sun, 15 Mar 2026 10:51:44 GMT

Hi @Caramon We’ve sent an invite to chat.

Please be aware conversations automatically close if there is no response within 48 hours.

Re: Connected Devices not showing on MySky

Caramon — Sun, 15 Mar 2026 19:49:34 GMT

Yes, sorry. I should have mentioned that it is indeed a white Sky Max hub.

Whilst I never used to mess with 95% of the settings on the older Sky hubs, I did used to set up a few things for Plex, a Minecraft server for my sons, and so on. I really don't like using apps on a phoe to do things and would much prefer a proper and comprehensive admin screen to be able to set things up the way I need it to.

Re: Connected Devices not showing on MySky

JimM1 — Sun, 15 Mar 2026 20:03:56 GMT

@Caramon Did you NOT get the invite to do the one to one chat with SKY? As you have now got the sky Max, the saying is "" Once you go Max you NEVER get to go back "".... See the linked info below for you!

My Post Has Been Escalated – What Happens Next on Sky Community

Re: Connected Devices not showing on MySky

Caramon — Mon, 16 Mar 2026 11:09:03 GMT

Yes, and I replied but have had no response so far.

Re: Connected Devices not showing on MySky

JimM1 — Mon, 16 Mar 2026 11:39:22 GMT

@Caramon You are in the hands off sky now and assume you got the bubble etc as shown on the click link. they do need to look at your account side that it is all tied together since you have went sky Max!

Can't allocate fixed IP to connected device

Caramon — Wed, 18 Mar 2026 11:11:47 GMT

Having now got my port forwarding set up for my Plex media Server, I find that my Sky Max (white) hub now won't let me set a fixed IP for that device. I can edit, choose reserved IP, leave the current IP (allocated via DHCP) as it is, add a comment and save, but it then returns me to the connected devices list and the device is still set to DHCP. if I edit again, it shows the comment was saved but it has remained set by DHCP. Is this expected behaviour? Should I have reserved the IP before enabling the port forwarding rule?

Re: Can't allocate fixed IP to connected device

JimM1 — Wed, 18 Mar 2026 11:30:40 GMT

@Caramon Not sure if you can set it when using the sky Max hub, the sky Broadband hub yes no issues, why not do it on the device itself if you have an issue that way!

Re: Can't allocate fixed IP to connected device

Caramon — Wed, 18 Mar 2026 14:47:37 GMT

I don't see any options on the MySky app to edit the connected device and give it a fixed IP from there. I only see that on the admin web UI.

Re: Can't allocate fixed IP to connected device

Caramon — Wed, 18 Mar 2026 14:51:08 GMT

Just to clarify, the Edit option is on the Sky Max Hub web UI when you login as admin. The issue is that it is ignoring when I edit the settings to change to a reserved IP rather than DHCP. Save loos like it's working fine, but when taken back to the Connected Devices list, it is still shown as being allocated an IP address via DHCP.

Re: Can't allocate fixed IP to connected device

JimM1 — Wed, 18 Mar 2026 15:10:04 GMT

@Caramon Hopefully someone else will pop in and suggest, do not use the sky Max at all so not Even sure what can be adjusted if anything once it get's onboarded to the sky system, all i was aware off is that uPnP can be done, but maybe other settings also, not much help afraid, SR203 can tell you what that sucker does and fixed IP is easy to do on it!

The device itself can you not go and take it off DHCP mode and stick the details needed there!

Re: Can't allocate fixed IP to connected device

Caramon — Thu, 19 Mar 2026 08:06:21 GMT

I',m not aware that any device has an influence on whether it gets its IP address from DHCP or not. That's governed by the Router/Modem hub. The other annoying thing is that the UI on the Sky Max hub doesn't show me a list of connected devices with their IP addresses. I have to edit each device in turn to see that information. It would be much more useful to see an IP address list, so if I want to change an IP address for a connected device and then reserve it, I can refer to the list before I allocate an address. The UI seems to have been dumbed down a bit too much IMHO.

Re: Can't allocate fixed IP to connected device

Chrisee — Thu, 19 Mar 2026 15:02:52 GMT

@Caramon go into the web interface of the Sky Max hub go to Gateaway>Connection>Local IP configuration and you will see the DHCP range is from 192.168.0.2 to 192.168.0.100 -- the last figure is editable . You can assign a fixed IP address higher than the upper limit for example 192.168.0.200 without a risk the DHCP server can issue it. Given the subnet mask is 255.255.255.0 any address up to 192.168.0.254 should be vusible to the hub.-

Re: Can't allocate fixed IP to connected device

TimmyBGood — Thu, 19 Mar 2026 17:18:27 GMT

@Caramon wrote:

I',m not aware that any device has an influence on whether it gets its IP address from DHCP or not. That's governed by the Router/Modem hub.

Switching off the DHCP service (sometimes called Automatic Address or similar) on a client device will almost always give an option to set a fixed IP through its own network configuration settings. It will not then send DHCPDISCOVER broadcast or respond to address offers from the DHCP server (router)

https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol

Re: Can't allocate fixed IP to connected device

Caramon — Fri, 20 Mar 2026 10:44:19 GMT

Hi, I know this but unfortunately I can't see a way in the UI to show me a list of devices and their current IP addresses. That used to be available in older hubs, and it would make choosing a fixed IP address for a device much easier. As it stands, I have to edit each connected device and make my own list of which IP addresses are currently in use. This UI seems to be a retrograde step compared to how things used to be done.

Re: Can't allocate fixed IP to connected device

Caramon — Fri, 20 Mar 2026 10:46:28 GMT

I've not seen any options on my WD MyCloud Home device (which is running the Plex Media Server) where I can disable DHCP on the device itself, so I have to conclude that isn't availble to me. If the option to switch to a 'reserved IP' was working on the Sky Max Hub then I wouldn't have to do that.

Re: Can't allocate fixed IP to connected device

Caramon — Fri, 20 Mar 2026 10:58:20 GMT

When we first took delivery of the hub, I set up port triggering for Plex and the hub did allow me to reserve the IP address on the connected device. When I then tried to set up a port forwarding rule, that's when the hub locked up and in the end (after talking to Sky Broadband technical help on the phone), I had to reset the hub to its default settings and start again. I've not touched Port Triggering since. From what I've been told, port forwarding is like having the specified port open all the time for that one connected device, whilst port triggering only opens the port when traffic to that particular port is detected. I have no idea if triggering is suitable for the Plex media server, or why setting a reserved IP appeared to work when I used triggering rather than forwarding on my first attempt. The recommendation from Plex is to have a fixed IP address on the media server when allowing remote access (which is what I allow), but I am aware that unless something else tries to grab that IP address (unlikely) on my LAN then the 2-day IP address lease from DHCP will just get perputually renewed for the device anyway, so I could just leave it on DHCP. However, the issue I'm concerned about is the Hub ignoring my request to reserve an IP address, when (unless someone can explain why it won't) it should be a simple thing to do.

Re: Can't allocate fixed IP to connected device

TimmyBGood — Fri, 20 Mar 2026 11:21:13 GMT

@Caramon wrote:

I've not seen any options on my WD MyCloud Home device (which is running the Plex Media Server) where I can disable DHCP on the device itself, so I have to conclude that isn't availble to me.

Unfortunately I think that's correct: it's a somewhat unusual device in that respect because the underlying operating system (almost certainly some flavour of Linux) would always have locally fixed IP as an option.