Well, if you are forwarding the ports from your home router, and you can’t reach, it’s the most probable cause, if you are, that means that there is no public IP reaching your home router.
You could contact your ISP and confirm if this is the case, they could offer to assign a public IP for an extra fee, your only other option is to rent a cheap VPS and tunnel traffic between it and your home, but at this point you could also decide to host stuff on the VPS.
If your ISP (Internet service Provider) doesn’t have you behind CGNAT or Double NAT (meaning that multiple homes share the same public IP), some ISP block the first block of 1024 ports, so any port below that number is blocked.
If the problem is that ports below 1024 are blocked, but you do have a public IP reaching your home router, you could contact your ISP so they unblock these ports for you (I had to do that once, so at least with my ISP it was as simple as asking).
The way you could test if your public IP reaches your home router is by exposing something on a higher port than 1024 like let’s say 8080, if you can reach a simple web or caddy or any other service from 8080, you can at least confirm, that is the issue.
Be aware that most ISP even if they assign a single IP per house, this IP can be dynamic and can rotate on a regular basis, like daily or weekly
Traceroute can be a good hint but try to do one to an IP like 1.1.1.1 and see the initial jumps, another way to confirm is on your router config interface, there should be an IP address it has assigned, subnet and gateway it connects to, with these values you could also verify it depending on what IP ranges it shows, and see if the assigned IP or Router’s WAN IP is the same as shown when you search for “what is my IP” online.
If you can confirm that your router assigned WAN IP is the same as your public IP, then it could be a misconfiguration of the port forwarding on the router or a firewall block either on the router or the computer