Women in Technology

Hear us Roar



Article:
  Apache Web-Serving with Mac OS X: Part 1
Subject:   me too : Cannot access username via the http://127.0.0.1/~username/
Date:   2002-01-31 23:23:23
From:   francis_st-laurent
Bonjour !


With a browser located on my Apache server machine - an iBook - I can access my “personnal” site http://127.0.0.1/~fderive/, now viewing the page that has been installed by Apple.


I cannot do so with a browser located on another machine - Mac OS 8.1 - on the same ethernet/appletalk network as the Appache server machine.


Just after start up, the command httpd -t in a terminal window says :


“[alert] httpd : Could not determine the server’s fully qualified domain name , using 127.0.01 for Servername.”


The access_log and error_log files are left with the effect of the first successful access, no more for the rest of unsuccessfull ones.


error_log :
127.0.0.1 - - [01/Feb/2002:07:12:49 +0100] "GET /~fderive/ HTTP/1.1" 304 -
127.0.0.1 - - [01/Feb/2002:07:12:50 +0100] "GET /~fderive/images/web_share.gif HTTP/1.1" 304 -
127.0.0.1 - - [01/Feb/2002:07:12:50 +0100] "GET /~fderive/images/macosxlogo.gif HTTP/1.1" 304 -
[localhost:~] fderive%



access_log :
Processing config directory: /private/etc/httpd/users
Processing config file: /private/etc/httpd/users/fderive.conf
[Fri Feb 1 07:00:03 2002] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Fri Feb 1 07:00:03 2002] [notice] Apache/1.3.20 (Darwin) configured -- resuming normal operations
[localhost:~] fderive%



May be this problem is already the case when I fail to connect to the Mac OS X machine from the Mac OS 8.1 - I see it in the chooser but Mac Os x admin username&password does not succeed -.


Reciprocally, connecting to the Mac OS 8.1 from the Mac OS X machine is OK.


Can you help me joining Apache club ?

Full Threads Newest First

Showing messages 1 through 3 of 3.

  • Morbus Iff photo me too : Cannot access username via the http://127.0.0.1/~username/
    2002-02-01 06:56:24  Morbus Iff | O'Reilly Author [View]

    The ServerName directive, as described from the Apache documentation: "The ServerName directive sets the hostname of the server; this is used when creating redirection URLs. If it is not specified, then the server attempts to deduce it from its own IP address; however this may not work reliably, or may not return the preferred hostname."

    http://httpd.apache.org/docs/mod/core.html#servername

    Basically, since Apache isn't getting a name, it's guessing at one, and choosing the 127.0.0.1 address, as you see in the message you copied for me. If your OS X machine has an IP address on your network, then you should use THAT as the URL to try and get to from your OS 8 machine.

    When you try to get to 127 on your OS 8 machine, you're, in essence, saying "hey! I have a server on this OS 8 machine! use it!". Since that's not the case, you've got to say "hey! I have a server on my OS X machine, which is called 192.168.176.22 (example)! use it!".
    • me too : Cannot access username via the http://127.0.0.1/~username/
      2002-02-03 22:54:40  francis_st-laurent [View]

      80.9.14.211 - - [02/Feb/2002:12:31:33 +0100] "GET /~fderive/ HTTP/1.1" 200 6186
      80.9.14.211 - - [02/Feb/2002:12:31:34 +0100] "GET /~fderive/images/macosxlogo.gif HTTP/1.1" 200 2829
      80.9.14.211 - - [02/Feb/2002:12:31:34 +0100] "GET /~fderive/images/apache_pb.gif HTTP/1.1" 200 2326
      80.9.14.211 - - [02/Feb/2002:12:31:34 +0100] "GET /~fderive/images/web_share.gif HTTP/1.1" 200 13370
      80.9.14.211 - - [02/Feb/2002:12:35:03 +0100] "GET /manual/ HTTP/1.1" 200 5556
      80.9.14.211 - - [02/Feb/2002:12:35:05 +0100] "GET /manual/images/apache_header.gif HTTP/1.1" 200 4084
      80.9.14.211 - - [02/Feb/2002:12:35:05 +0100] "GET /manual/images/pixel.gif HTTP/1.1" 200 61
      80.9.14.211 - - [02/Feb/2002:12:52:49 +0100] "GET /~fderive/ HTTP/1.1" 304 -
      80.9.14.211 - - [02/Feb/2002:12:52:50 +0100] "GET /~fderive/images/web_share.gif HTTP/1.1" 304 -
      80.9.14.211 - - [02/Feb/2002:12:52:52 +0100] "GET /~fderive/images/macosxlogo.gif HTTP/1.1" 304 -
      80.9.14.210 - - [02/Feb/2002:13:40:17 +0100] "GET /~fderive/ HTTP/1.1" 200 6186
      80.9.14.210 - - [02/Feb/2002:13:40:18 +0100] "GET /~fderive/images/macosxlogo.gif HTTP/1.1" 200 2829
      80.9.14.210 - - [02/Feb/2002:13:40:19 +0100] "GET /~fderive/images/apache_pb.gif HTTP/1.1" 200 2326
      80.9.14.210 - - [02/Feb/2002:13:40:19 +0100] "GET /~fderive/images/web_share.gif HTTP/1.1" 200 13370
      80.9.14.210 - - [02/Feb/2002:14:10:50 +0100] "GET /~fderive/ HTTP/1.1" 304 -
      80.9.14.210 - - [02/Feb/2002:14:20:58 +0100] "GET /~fderive/ HTTP/1.1" 304 -
      80.9.14.210 - - [02/Feb/2002:14:31:26 +0100] "GET /~fderive/ HTTP/1.1" 304 -

      Hello !

      Any comment ?

      I had forgotten I had played with a little ethernet network for which I had these Mac 0S 8.1 machines 211 and 210, the latter having an ISDN Sharing connexion to the internet.

      You see everything is OK now - I *do* understand more the addressing matter !

      Machines 211 and 210 can connect to 212 - not shown - which is Mac OS X machine with the Apache server.

      I think I started with the address I found on the 210 machine and then I installed the same "80.9.14" on the Mac OS X machine, making it different with the last number.

      Now, the Mac Os X network prefs lives with TCP/IP "Manually" - having 80.9.14.210 as Router -, or "Manually using DHCP router", in that case the address of the router is found automatically - I guess -.

      That leaves other network *basic* questions...

      For no rest, I checked I could connect to the Internet from 210 and 211 through 210, but did not succeeded from the 212 Mac OS X machine. That is not an Apache question.

      I appreciated a lot the quality of your chirurgical explanation.

      Merci beaucoup.
      • me too : Cannot access username via the http://127.0.0.1/~username/
        2003-04-12 17:03:59  anonymous2 [View]

        127.0.0.1 is a loopback address. It accesses the current machine you are on. Therefore, you cannot access another machine with it. To access the other machine, you have to know its IP address, which can easily be obtained by opening a DOS prompt and typing:
        ipconfig /all