11-01-2026 10:45 AM
Hi All,
Another Issue with the Hub 7 Plus, probably on others too.
When i create a Port forwarding rule, it always comes up with an error and doesn't save or eventually when it does save, it has created duplicate rules. Try to remove one and it removes both, aaarrrgghh! These EE hub are very frustrating.
I hope someone who can help sees this and my other post, to help fix these issues.
18-03-2026 07:18 PM
Is port 80 forwarded to the same device as port 21? Is port 80 open from the Internet ?
19-03-2026 07:24 AM
Hi, I'm just using port 21 at the moment. I do get the error message when first creating the rule that the IP address should be static. But it does appear to save it and I don't get duplicate. That use to happen with the previous firmware. But I can't seem to get any port forwarding rules to work. Hope we have some EE software engineers seeing this chat as their are issues with the EE Hub 7 plus. Is everyone having the same problem?
19-03-2026 08:01 AM - edited 19-03-2026 08:10 AM
@SamyM wrote:Hi, I did the reset from the back of the router and then connected it to Broadband then I connected it to the main ethernet switch which connects the whole house. so on that is the TVs, WD Cloud EX2 Ultra x 2, PCs etc. then I did the port 21 forwarding, but does not work. I cannot get it to work apart from enabling DMZ. I believe EE has an issue with the router.
Thanks. And the answer to my other question..?
If the NAS was plugged in, then was it clearly showing as assigned the .155 address in the network map/device list?
i.e. does the IP in the device list match the one you're using for the rule? It might also be worth verifying that the MAC address is as expected and the little port-forward icon is displayed next to the WD EX2 entry.
Is everyone having the same problem?
No, they're not. I posted my findings here when I tried replicating your problem and I was able to forward port 21 for an FTP server on my local network without any issue.
It sounds like you're doing everything you need to but there must be some reason why I can get things to work and you can't. Is there any way for you to temporarily remove the switch from the equation to rule that out? Although, it shouldn't be causing any problems e.g. there are two daisy-chained switches between my hub and the device I installed an FTP server on and that worked without issue.
Did you also try disabling UPnP? On the NAS how are things configured under WD Dashboard -> Settings -> Network - any clues there?
19-03-2026 09:15 AM
I asked if port 80 is open from the Internet, to troubleshooting if its just port 21 closed. Do you have an app with a browser on port 80 that you can port forwarding to? It's a process of elimination, I ask again are you absolutely sure you are using the correct external hub address, because that's exactly the problem I had with my hub 7 which turned out to be a ddns update problem
I have no problem with port forwarding on hub 7, it must be a related issue. I fear you are going down a rathole by thinking its a hub firmware issue, because it clearly is not
As bobpullen said, his port 21 test is fine, and my 80/443 works perfectly. You are looking in the wrong place at the firmware IMHO.
19-03-2026 10:08 AM
Hi, I have tried it with port 21 and done a test from the Ctronics IP camera App and it fails to connect to my WD Cloud. I have configured my WD Cloud to get a static IP address. I have also tried using using https://www.yougetsignal.com/ to test the port and it says is closed.
I have tried using port 80 for http and that is also closed. Do not understand why this is happening on EE Hub 7 Plus. My conclusion is that EE have an issue.
19-03-2026 11:10 AM
@SamyM Is the BT Smarthub2 still all working as before for you with no problems, When did you upgrade the package to get the 7 Plus Hub?
19-03-2026 07:17 PM
Hi, I went to full fibre 900 back at the start of December last year and Had problems with the EE Hub 7 Plus ever since. I see messages that new firmware has been made available, so I plug the Hub 7 Plus to see if that makes any difference. No success yet. The updates always seem to happen overnight even though when you call EE support, they tell you do a reset and it will force the Hub to get the latest firmware within the hour. Which I have found not to be true.
Currently running on EE Hub 2. With my setup at home all seems to be running well. Just cannot make the transition to the EE Hub 7 plus which when I call EE support, they say it’s far superior. But I have to say the Hub manger on the Hub 7 Plus is very clunky, slow, and seems to time out going to different sections sometimes. Don’t get this issue with Hub 2. They have sent me a replacement Hub 7 Plus but that has made no difference. They have offered me to go to another provider with no cancelation fee. This issue has gone on a longtime. Port forwarding such a simple thing, how can it be so complicated to get it to work on Hub 7 Plus.
I'm not giving up.
19-03-2026 07:38 PM

This is my status screen and port forwarding works perfectly.
20-03-2026 07:46 AM
Hi, I'm doing exactly the same as I would for the Hub 2. What are you doing for the Hub 7 Plus. The ports stay closed for me. The only way I get port forwarding to work is to enable DMZ which basicly turns off the routers firewall. I cannot see your picture. For me the rule is created but I initially get an error saying the IP address must be static, which it is. It does not seem to action the rule/instruction when I test. Does yours test ok... https://www.yougetsignal.com/
20-03-2026 09:56 AM
I'd still be interested in hearing the outcome of other suggestions in this thread e.g. do the IP addresses/MAC addresses align, is there a port forwarding icon in the device list, what is the network configuration of the NAS, are you able to try temporarily testing without the switch etc?
Anyway, just spun up the FTP server on one of my machines again. This is a wired desktop connected to my hub via two unmanaged switches: -