---

Problem

Checklist

1. Try using direct-connect to access your WebObjects application.

2. Check that you can load a static page.

   Corrective action:

   If your browser displays a message saying that it was unable to connect or that the connection was refused, your HTTP server is probably not running. Check that your server is running. Otherwise, see See Checking the Installation for information on how to fix your installation of WebObjects.

3. Check that the WebObjects adaptor is functioning.

   Check that the WebObjects adaptor is installed correctly and can run. Use your browser to open this URL (which specifies the WebObjects adaptor, but fails to specify an application name):

   http://localhost/cgi-bin/WebObjects

   (You may need to replace "localhost" with the name of the host running your HTTP server. You may also need to replace "cgi-bin" with the actual name of the directory that contains scripts and CGI programs on your server.) If the WebObjects adaptor is installed correctly, it displays a list of WebObjects applications running on the local machine.

   If the adaptor is installed incorrectly or can't run, the browser will instead display a message indicating that the requested object cannot be located. The message may look like this:

   404 Not Found
   The requested URL /cgi-bin/WebObjects was not found on this server.

   Corrective action:

   Make sure you've supplied the right names in the URL for the host ("localhost" in the example above) and for the cgi-bin directory (sometimes named "Scripts" or "cgiPrograms" rather than "cgi-bin"). Otherwise, see Checking the Installation for information on how to fix your installation of WebObjects.