OS X Mavericks Server.app doesn't show site, but default Welcome to OS X Server page

Question

I am completely new to Mac OS X Server.app, so sorry if I sound dumb .
1. I installed Server.app to Mavericks.
2. Enabled Websites service in it.
3. Installed MySql.
4. Installed Wordpress using this script: https://github.com/MacMiniVault/Mac-Scripts/blob/master/mmvwordpress/mmvwordpres s-README.md
5. Created coresponding website to Websites
6. I opened Safari and navigated to my new created website: http://predstavitev.net:8081 and all I get is server's default page.
7. I checked what is the content of my "predstavitev.net" folder on server and found that it actually contains Wordpress installation files:
Please help me find out, what am I doing wrong. Thanks.

Answer 1

Check the Console.log for details that might be getting logged there related to this issue.
You're probably using NAT here, which means you'll be using split DNS or using an internal domain and an external domain.  (Confusingly, DNS centrally matters with the web client accessing the web site, and rather less so with the web server itself.)
OS X Server itself requires DNS, irrespective of the web server — usual setup is the local IP network (not in 192.168.0.0/24 nor 192.168.1.0/24 subnets due to collisions with VPN connections later, and preferably somewhere "weird" in the 192.168.0.0/16 or 172.16.0.0/12 or 10.0.0.0/8 private IP blocks — pick a weird range for your subnet, not the first few ones that everybody else uses. 
To verify local DNS services, launch Terminal.app from Applications > Utilities and issue the following harmless diagnostic command:
sudo changeip -checkhostname
That'll require an administrative password, might show a one-time informational message around the use of sudo, and will then display some network information and then an indication that no changes are required, or that there are DNS or network problems.
Do not use .local nor .arpa as your domain.  (That works fine for incidental stuff, but network security and secure connections and related underpinnings all expect the servers involved to have valid DNS — not Bonjour.)
Unfortunate, if DNS is actually incorrectly configured, then various services including the mail server and Open Directory and the profile manager all tend to have problems, and all SSL-based security is dependent on proper DNS configurations.
FWIW, I'd be careful with managing a WordPress server, as breached with that Content Management System (CMS) package are common.  I'd probably either host the site elsewhere (in the "cloud"), or would configure the WordPress web server in a DMZ to isolate the potential damage arising from a breach.   (I use Drupal locally and while breaches with that are somewhat less common than with WordPress, I still lock that down, and still prefer to DMZ that.)  With WordPress or Drupal or any other CMS, keep your patches current, too.