Skip navigation

404 error for personal site

521 Views 5 Replies Latest reply: Oct 29, 2012 4:26 PM by mkm29 RSS
mkm29 Calculating status...
Currently Being Moderated
Oct 29, 2012 8:12 AM

I have my desktop (Mac Pro) set up as my personal web server to host one of my websites (mitchsprogress.org) using DynDNS to handle my dynamic IP address, it works fine except I get this error when I try to access my site locally, but I had my friends test it and it loads properly for them, does anyone know how to fix this or how I can diagnose it? Screen Shot 2012-10-29 at 11.11.12 AM.png

 

Also just FYI I am using Mountain Lion and Server.app

Mac OS X (10.6.8)
  • MrHoffman Level 6 Level 6 (11,695 points)
    Currently Being Moderated
    Oct 29, 2012 9:46 AM (in response to mkm29)

    404 means you got to a web server somewhere, but (if it's your web server) probably not to the virtual host (what Apple calls a "site") that you had intended.  I'll assume you're entering the same string in the browser, whether local or remote.

     

    First, launch Terminal.app and issue the non-destructive diagnostic command

     

    sudo changeip -checkhostname

     

    This command will (usually) indicate whether the network is configured correctly or if there are changes required.

     

    Then issue the following Terminal.app command and see what you get as a response

     

    dig mitchsprogress.org

    dig @8.8.8.8 mitchsprogress.org

     

    You'll probably get your public IP address with both commands.  If you see different addresses returned from these two commands, please indicate that.

     

    Now check the Apache web server logs, and see what the incoming connections are, and what sorts of errors are arising.  If any.

  • MrHoffman Level 6 Level 6 (11,695 points)
    Currently Being Moderated
    Oct 29, 2012 4:17 PM (in response to mkm29)

    So the host name indicated "no changes are required"?  Good.

     

    Are you using the same domain inside your network as you're using outside?

     

    Yes; this IP addressing and DNS stuff matters.  OS X Server requires correct DNS services, and the web view (virtual host, site, etc) that the web server presents to the client is (somewhat confusingly) based on the DNS services name that the client web browser uses. 

     

    If you're getting back an NS nameserver record and not an A machine record from the dig commands, then local DNS isn't right.  For some background, here is how to set up DNS on OS X Server and here is how Apache virtual hosts work

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.