Configuring a Virtual Machine as a Web Server is basically no different then configuring a Physical Machine as a Web Server and the fact that you can access the Guest OSes Web Server from the Host and not from another System on the LAN/WAN means your either not attempting to access it correctly or the Host is blocking communications from other Systems on the LAN/WAN. FWIW I have a Web Server running a Virtual Machine on my Mac and regardless of what type of Network Adapter I'm using in the Virtual Machine's Settings I can access that Virtual Machine from anywhere because I can properly configure it to be accessible and this can require configuring items in the Guest, Host and or Router depending on how I want it configured.
As an example the easiest way to expose the Virtual Machine to other Systems beyond the Host on the LAN is to use a Bridged Network Adapter in the Virtual Machine's Settings and assuming the Host's Firewall is not blocking communications for VMware Bridge Protocol then the Virtual Machine should appear on the LAN just as Host does. You should then be able to access the Virtual Machine directly by its IP Address. If you what WAN Access to that Virtual Machine then you should be configuring Port Forwarding in the Router, that connected to the Internet, to the IP Address the Bridged Virtual Machine is using and the appropriate Port(s).
If the Virtual Machine's Network Adapter is configured as NAT (Share with my Mac) then you will need to enable Port Forwarding and then access the Virtual Machine's Web Server using the Host's IP Address and Port Number is other then Port 80. The Host/Guest Firewalls will need to not be blocking whatever Port(s) you choose and the appropriate Ports need to be open on the Host as well as the Guest. You'll need to modify the VMnet8 nat.conf file if you're using NAT with Port Forwarding.