I noticed that in the list of web search results, ports 80 and 443 seem to cause bother with hubs. Unless someone else on the forum has a solution it looks like a proper router is required. Just one of the reasons I don't use Hubs, I found a Hub 1, 3 and 5 had issues with port forwarding when trying them, so no reason to expect different from the others. Though some people seem happy with them. Not a lot of help at the moment though.
The ports are only opened when an application is actively listening on them. Just tried here. Ports 80, 443, 8080 and 4433 show closed with Shields Up but when an application is running and listening on those ports they show as open. So can you verify the server is running and the correct LAN IP is being used for forwarding?
If all that is correct then it must be down to the hub.
Is there no WAN access at all?
What error messages from the test site?
Do the ports still register as closed when tested? For example Shields UP at grc.com.
If ports are forwarded to the LAN IP correctly and the ports are still closed then it's likely the Hub not doing the forwarding correctly. About four years ago I thought I'd try using the Hub 3 to see if there were any improvements over the first Hub I had but still had problems with port forwarding and eventually gave up and put the Billion back.
I took the easy option and got a Western Digital MyCloud external drive, I can access it from anywhere. It's about as near plug and play as you can get.
Working with a SmartHub no problem
Are you certain that the Owncloud application is running and listening on the ports that are forwarded? If the server is not running then the ports will be unresponsive 'Closed'.
As here results from grc shields up site.
Port forwarded and application not running:
Same port with application running:
Finally the response you would expect with no forwarding:
I have made no alteration to the default router setting of UPnP default on setting, though I must point out again, I'm not using a BT Hub.