Port 8443 closed

[#1]

Does anyone know if port 8443 is blocked?
It's not open when pinged and there is nothing between the ping and the router. I've port forwarded the port to an internal server that has that port open through tcp. Even if I turn off the firewall it shows blocked. I'm stuck... any ideas please?

[#2]

@Halfhidden 

port 8443 is likely closed for unsolicited connections, but a port forward rule should bypass any block.

Which router are you using?

How are you pinging the port?

[#3]

@Halfhidden 

Some further information.

Depending on how long you have been with plusnet there is a broadband account based firewall which needs checking.

Login to the members centre from the landing page navigate

Home >Broadband >Broadband Firewall (you need to scroll down the page)

Make sure the setting is NOT HIGH, for you I would suggest setting to OFF.

Another point is although you may have port open on the target device there has to be an application LISTENING for connections on the port. Depending on the device netstat is the terminal command to use to check

For a Hub Two checking the event log >Home >Advanced Setting >Event log you should see an entry in this format for an accepted INBOUND connection on port 8443

hh:mm:ss, dd mmm. FWL Port Forward Server (Destination IP) TCP 8443 accepted a new connection from (source IP)

Hope this helps

[#4]

Hi Dan_the_van

Yes I have port forwarded the 8443 port my server and that firewall is set for in and out on tcp port 8443.
The router is Plus Hub2. I've also closed down the firewall on the router and then pinged the port again and it is still closed. For clarity I also used a port scanner online to check that the port was closed and that to came back as closed.
This port is closed before the router, so it seems.

[#5]

Hi Again Dan_the_van

Thanks for the heads up on the safety settings on the portal. They were turned off, but a good call none the less.
I'm a bit stumped to be honest. This is the only port that I can't forward and it sort of draws me to the fact that perhaps the router (it's only a household one anyway) is faulty.
I'm going to try and swap that out and see if that solves the issues and go from there.

[#6]

Does the server respond when pinged from within your network ?

[#7]

@Halfhidden 

My port forward rule looks like this

There is not a problem for me using a port forward rule for 8443, event log reports

11:21:58, 29 May. FWL Port Forward Server(192.168.1.201) TCP 8443 accepted a new connection from 148.252.148.126

You will always see the above message when there is an attempt to connect to the port forward IP Address regardless of the device being switch on or off.

https://www.yougetsignal.com/tools/open-ports/  confirms port 8443 is open when the device application is running, as I said before something has to be listening on port 8443 for the test to succeed.

[#8 · Accepted solution]

**Solved**

My son who is also with Plusnet changed his router a while ago and allowed me to use his... This worked straight away. I'm guessing that perhaps mine needs to be flashed. 
Its been driving me mad as I can't understand why only one port would act like that. Normally you would expect the entire port forwarding to be faulty.

Thanks everyone for your input. It's a great community

[#9]

@Halfhidden 

Pleased to hear the issue is resolved, make sure you're using your login credentials and not your sons as the same broadband user logged in twice is not a good thing.