I'd start by looking at your router. Is the port forwarding done right?
This is what your system sent to me
Code: Select all
root@aplus /tmp # wget --server-response http://www.grahammelbournephotography.com/
--2016-01-04 11:16:24-- http://www.grahammelbournephotography.com/
Resolving www.grahammelbournephotography.com (www.grahammelbournephotography.com)... 2.127.21.102
Connecting to www.grahammelbournephotography.com (www.grahammelbournephotography.com)|2.127.21.102|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Mon, 04 Jan 2016 11:16:29 GMT
Server: Apache
Last-Modified: Tue, 13 Oct 2015 17:27:21 GMT
ETag: "e1-521ffc222f040"
Accept-Ranges: bytes
Content-Length: 225
Vary: Accept-Encoding
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
Content-Language: en
Length: 225 [text/html]
Saving to: ‘index.html’
index.html 100%[=====================>] 225 --.-KB/s in 0s
2016-01-04 11:16:24 (2.59 MB/s) - ‘index.html’ saved [225/225]
Can you run
wget --server-response http://pi.local on your system because I suspect that page is being served by your router.
Can you take a look in your /var/log/apache2/* logs there should be a hit from "80.xx9.xx2.243" if my request got through to your raspberry pi. Something like
Code: Select all
www.grahammelbournephotography.com:80 80.xx9.xx2.243 - - [04/Jan/2016:11:20:45 +0000] "GET / HTTP/1.1" 200 1151 "-" "Wget/1.16 (linux-gnueabihf)"