Ports 80 & 443 remain stubornly closed

[#1]

I took delivery of a "Plusnet Hub Two" router today and have set up port forwarding rules for a web server running on a RaspberryPi:

But this handy tool shows that these ports are closed to incoming requests from the internet: yougetsignal.com/tools/open-ports 

Home > Advanced Settings > Configuration > Firewall is set to Default. As a temporary experiment I also tried setting it to Disabled - no change.

I've logged into the Member Centre and turned Safeguard off.

Searching this forum, I've seen reference to disabling the Member Centre firewall, but I can't see any firewall link in the Member Centre (only Safeguard).

Any suggestions gratefully accepted.

[#2]

@easleydp The Member Centre firewall does not exist on new connections, or, IIRC, on the Hub2 at all. Can't help with the closed ports question, though, it is not in my skill-set. 

[#3]

@easleydp 

If the members centre firewall exists on your account it will be found ->Home -->Broadband (scroll down the page) --->Firewall

This link might work https://www.plus.net/member-centre/broadband/firewall 

The rules image you have posted look fine to me, when you attempt a connection you should see the inbound connection in the Hubs event log found ->Home -->Advanced settings --->Technical log ---->Event log and will be in this format

hh:mm:ss, dd mmm. FWL Port Forward Server(server IP Add) TCP nnn accepted a new connection from <client IP Add>

where <server IP Add> is the raspberry pi, TCP nnn will be 80 or 443, <client IP Add> will be the remote device IP Address.

The port checker should create a event log entry.

I take it a local test is successful?

With a new network are the IP Address, default gateway and DNS settings correct for the Hub two network?

[#4]

Thanks for the direct link to the firewall page, Dan. It looked promising for about one second (just enough time for me to see links to basic and advanced settings) before the main portion of the web page went blank, and the Firefox browser console shows an error "can't access property "map", this.props.handles.basic is undefined". Likewise in Chrome with a similar error message.

> when you attempt a connection you should see the inbound connection in the Hubs event log
Interestingly, the ougetsignal.com tool I linked to earlier didn't result in any event log activity yesterday but this morning it does! For one click on the tool's "Check" button I see 6 FWL events over a period of 3 seconds: "FWL Port Forward Server(192.168.1.63) TCP 80 accepted a new connection from 198.199.98.246". 192.168.1.63 is correct (the RaspberryPi).

> I take it a local test is successful?
Apologies, despite being reasonably technical I don't know much about networking. Please could you elaborate on any further tests I might perform.

> With a new network are the IP Address, default gateway and DNS settings correct for the Hub two network?
Again, not sure, but here's a screenshot that may be relevant:

[#5]

Here's a local test, performed from my PC (which has a wired connection to the router):

404 is the correct response from the Pi, so a successful local test.

[#6]

192.168.1.63 would be a static IP address on the device rather than a DHCP allocated IP address from the Hub. For a DHCP allocated IP you would be something between 192.168.1.64 and 192.168.1.253

Can you ping sites like google.co.uk and bbc.co.uk from this pi?

If no reply, this would suggest a default gateway issue use this command to print out the default gateway

ip route
default via 192.168.10.1 dev wlan0 proto dhcp src 192.168.10.205 metric 600
192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.205 metric 600

as above ip route will provide the current default gateway, for my example mine is 192.168.10.1 checked from device 192.168.10.205

For you I would expect to see default via 192.168.1.254

What was your previous router?

EDIT: the event log messages do prove a accepted connection.

Are you using a VPN?

[#7]

From the pi I can ping the router but not external sites, e.g.

"ping: bbc.co.uk: Temporary failure in name resolution"

`ip route` output:

default via 192.168.1.1 dev wlan0 src 192.168.1.63 metric 303
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.63 metric 303

Previous router was a Sky Hub. Here's a screenshot I grabbed (amongst many others in case needed) before

decommissioning:

I am not using a VPN.

I should also perhaps mention that the pi is on the other side of a WiFi range extender.

[#8 · Accepted solution]

@easleydp 

192.168.1.1 is the issue, you need to change the default gateway and DNS to both be 192.168.1.254

Edit: you have rebooted the pi since you changed to a Hub

[#9]

That makes sense. I elected to change the router IP address from 192.168.1.254 to 192.168.1.1. Now it's working fine!

Thank you so much for your help, Dan - much appreciated!

Dave

[#10]

After I posted I did consider changing the Hub Two to 192.168.1.1.

Pleased all good now.