Sorry, if I would have read your OP more closely I would have realized that since your problem states that you can access the website using the localhost loopback address (127.0.0.1) that you were developing and hosting on the same machine. So it's important to note that most routers will balk at going out and coming back in to locally hosted services, it's kinda of the whole idea as to how NAT works, you use local addresses for locally hosted services on your same subnet.
I think the actual problem has something to do with the send and destination address for packet requests being the same (the outside edge address of the router) so when your looking for a webserver with the same address as the outside address of the router it request hits the outside edge and doesn't have anywhere to go as the source and destination is the same.
The next hop, upsteam router would probably answer if at all, with something like, what are you asking me for, you already know the answer to that, it's you. So it doesn't ever really obtain a route path resolution since it's already at where it's going, if that makes any sense at all.