So you want to have different web servers on your home network that are exposed to the outside world?  How do you do that?  Most web servers listen on the same ports: 80 for non-ssl and port 443 for ssl. If a request comes in for port 80  

Say your home network is setup like this:

1. Setup a dynamic DNS service.

               Go to duckdns.org (super simple) to create a subdomain url for each computer you’d like to access in your internal network from any computer in the world.   I won’t explain it here as the DuckDNS site does a good job.  In my example you would need to set up 3 subdomains for your home network:

2.  Setup Port Forwarding

                  Normally, if you are outside your home network, say at a coffee shop, and plug “http://homey.duckdns.org” in your browser you most likely will end up either with blank page/unauthorized page or will get the control panel login for your router which is at 192.168.1.1. 

To set-up port forwarding within your home network go into your router (192.168.1.1 in my example) and navigate to the port forwarding section. I use ddwrt so in my home network I would selecte DD-WRT’s NAT/QoS menu selection and set the port forwarding as follows:

Here’s a screen shot of my example setup:

 
Once Saved, you access your sites as follows:

If someone leaves the port out (http://blog.duckdns.org) it would just go to a blank page because it would be forwarded to 192.168.1.1:804  which is a fake port with nothing listening.

Also, if you’re using ssl you’ll need to set up ssl certificates (use LetsEncryptfor free ssl certifices)

As a final note, you could have all of these sites on one computer (personally I’m doing this on Raspberry Pi 3 using lighttpd and homeassistent), but you would have to change the default  listening ports on each server that is running. For example, instead of your blog’s server software listening to 443, you would have the ssl port listen to say 452.   Likewise, your wife’s ssl port would listen to say 574, etc. .