Can't connect via static IP

[#1]

Hi there.
Recently I installed a TP-Link mesh system into my house. I turned the Plusnet router into a modem by turning on bridge mode. Everything has been working fine for a couple of weeks and I have been able to access my NAS via the static IP until just this morning. Any ideas what I might be doing wrong? Just to be clear it was working perfectly and I could access remotely from my phone .
Cheers, Steve

[#2]

Are you still connected on the static IP?

[#3]

Not sure what you mean amigo? I can't connect to the static IP.
When I type the URL into chrome I get:

Forbidden
Rejected request from RFC1918 IP to public server address

[#4]

@black2112 seems like it may be a TP link issue https://community.tp-link.com/en/home/forum/topic/520662

Is your phone connected to the local network or on a mobile (4g) connection ?

[#5]

Ah right. Thanks for the heads up. That's pushing me in the right direction at least. Much appreciated 👍👍👍

[#6]

The thing is, it was worrying perfectly just this week (I've had the mesh for nearly 3 weeks). I was out the house and I could connect to the NAS remotely. Could there be an issue at Plusnet?

[#7]

---

@black2112 wrote:
Not sure what you mean amigo? I can't connect to the static IP.
When I type the URL into chrome I get:

Forbidden
Rejected request from RFC1918 IP to public server address

---

You stated that it all used to work (one presumes as per the current set up) when accessed from your mobile REMOTELY.  Logically that would lead to the possibility that you are not connected to the internet on your known static IP.  There are circumstances where this can happen.

However the added information of the error message clearly indicates that the mobile is connected LOCALLY ... so not the same as when it was working before.

Many routers will not permit one LAN device to access another LAN device via the WAN interface.  Try switching off WiFi on the mobile and see if it starts working again.  This is nothing to do with Plusnet ... but might well be everything to do with the third-party networking technology you have installed.

[#8]

@Townman.
Thanks for that very detailed reply. I'm a doughnut: I was still connected to my Wi-Fi as you correctly pointed out. I've now disconnected from the Wi-Fi, typed the URL into Chrome again and it's just hanging with the usual Chrome statement:

This page isn’t working
If the problem continues, contact the site owner.
HTTP ERROR 408

[#9]

I should say, thanks to everyone who's replied so far. Very nice community you have here

[#10 · Accepted solution]

Good news then - you are now looking at a different aspect of an issue - see 408 Request Timeout - HTTP | MDN

This is a DELIBERATE action of something in your network to refuse to play.  The logs in the TP Mesh or the NAS might offer some clues.  Are you confident that the port forwarding for this service are intact given your investigation (and possible modifications) of the failure when connected LOCALLY?

[#11]

All fixed. Rookie error..... I had forgotten to set up port forwarding 😲
Thanks to everyone who took the time to reply. Really appreciate it