Port forwarding not working? Check these things first
A new router will not fix a service that is stopped, a firewall rule pointing at the wrong device, or carrier-grade NAT. Work through the path from the device to the internet.
1. Check the service inside your home
Find the server's current local address and the port its application actually uses. From another device on your home network, try the application's normal connection method using that local address. If it fails here, stop: an internet-facing forwarding rule is not the next fix.
Check that the application is running and listening on the network interface, rather than only on localhost. Check its own access settings and the device's firewall. Prefer a narrowly scoped rule for the application over disabling the firewall. A successful local connection is your first useful checkpoint.
2. Compare your router's WAN address
Turn off any VPN or proxy on the checking device. Open your router's status page and read its WAN or internet IPv4 address. Enter it in the CGNAT and double NAT check. Keep IPv4 and IPv6 separate: an IPv4 forwarding rule cannot be tested using an IPv6 address.
If the router is behind the provider's NAT, ask the provider about a public IPv4 address. If two routers in your home are doing NAT, check the double NAT explanation before changing either device. Buying a different router does not remove your provider's NAT.
3. Check the destination and protocol
Reserve the server's address in DHCP so a restart does not move it. Confirm the forwarding rule's internal address, external port, internal port and TCP or UDP selection against the application's documentation. Enable only what it needs. The port reference explains common uses; the application's own settings are the final authority.
4. Test from outside
Use a separate connection, such as a phone on mobile data with Wi-Fi turned off. Testing your public address from inside the same network can fail when the router does not support NAT loopback, even though external access works. Keep the application running during the test. This site does not scan your ports.
If it still fails
Record the local test result, your WAN address comparison and the exact rule. Check whether your provider blocks inbound traffic or the application requires extra configuration. For reaching your own devices, an outbound mesh VPN may suit better than a public service. A consumer privacy VPN is not automatically a remote-access solution.
Close unused rules afterwards. Do not expose a router's administration page or a camera stream just to see whether forwarding works.
Source and next step
TP-Link's port forwarding documentation explains address reservation and the rule fields. Exact menu names differ across models. Start with the address comparison, then return to the first checkpoint that fails.