I wish to open Ports 80 and 443 on my BT smart hub. For why, please see httphs://github.com/nextcloud/nextcloud-snap/wiki/Connecting-the-Nextcloud-Box-to-the-Internet
I have followed the BT help and can add port forwarding by logging in to advanced settings. However, the command sudo nmap -sT -O XX.XXX.XX.XX (the latter is the IP address of the smart hub) indicates that port 80 is open but port 443 is closed.
I have tried removing the port forwarding, rebooting the smart hub and adding the port forwarding again, but to no avail.
I can see no apparent reason why 443 remains closed.
If anybody could offer advice, I would be grateful.
I would just like to add that, as a test, I hard booted my BT smart hub and entered all information anew (including DNS and port forwarding). The problem remains:
Host is up (0.0021s latency).
Not shown: 998 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp closed https
Why would you need to open these ports they should be open by default probably the reason why you are are experiencing problems opening 443.
Thank you for these comments. When I open ports 80 and 443 and then check with http://www.yougetsignal.com/tools/open-ports/, port 80 is open and port 443 is closed. This si the same result that I obtain with nmap.
This continues to perplex me. I can only conclude that BT therefore prevents this port from being opened (even though in the configuration of the router it has been included in port forwarding).
BT are not blocking the ports. The image proves this. For the port to show 'OPEN' the application concerned has to be running and listening for requests. When the application is closed here the ports show stealth and open when it's running.
This would suggets otherwise. Strangely it seemed to work fro about 30mins and then the shutters came down. Ideas anyone on how to open them up again?
If you are certain the software is still running, that is actively listening on the ports and you use some form of dynamic DNS service that is updated with every IP address change then it should work.
Check your settings again and if all else fails it might need a factory reset of the hub and then put all your port forward and dynamic DNS settings back.
The hubs I have all had similar port forward issues, so I gave up and got my own third party kit.