404 Not Found

Hello Everyone,

Please help all of a sudden my I cannot view my site through localhost. I’ve restart apache services everything is ok there but still cannot view my site I get.

Not Found

The requested URL /test1.html was not found on this server.

Thanks

helen

Helen,

Insufficient information. Please identify whether you’ve used a “canned application” (XAMPP or WAMPP or ???) and that your URL is and what the server’s response is to you. That would help.

In the mean time, is your URL http://localhost/test1.html? Is test1.html in your htdocs directory? More definition of the problem is required.

Regards,

DK

Thanks DK, I’ve installed Apache 2.2.19 and PHP/5.3.5. both separate. My remote info is Local/Network, Server Model None, Access Local/Network, folders are in htdocs directory, HTPP address Localhost, Links relative to Document. Localhost was my server response.

It was working fine until couple of days ago I have no idea what i’ve done wrong or what happened it’s a mystery. I am wondering if it’s because I am working between two different dreamweavers one is dreamwever 8 the other dreamweaver cs5.5 that one I had to create new site of course using the same folder of site already created from dreamweaver 8.

Any help would be appreciated.

helen :frowning:

Helen,

Okay, the problem is (because it had been working properly) a change in how the server is defined between Dreamweaver installations. Double-click on the site name (in CS5.5), then Server on the left then double-click on Testing Server on the right to open the edit dialog. The server name will be at the top (leave that alone), Local/Network should be selected for the Connection used, USE THE folder to navigate to the htdocs folder and select that then finally use http://localhost/ for the Web URL. Save twice then F12 will work to open the file in the browser.

Otherwise, enter http://localhost/test1.html.

If that doesn’t work, then there are several possible things to check:

  1. Start | search for services.msc then look through the list for a service which has hijacked port 80 (default for http but also used by Skype and, recently, some printers). STOP any service other than Apache 2 then restart Apache.

  2. localhost is the default in the Apache conf file; so is 127.0.0.1 localhost in your c:\Windows\system32\drivers\etc\hosts file - but check them anyway.

Regards,

DK

I am afraid i’ve completely lost apache and cannot re-start from the apache Monitor the ‘Restart’ is greyed out. After receiving 404 Not Found I checked the httpd.conf file and noticed I had another site addressed at the Document and Directory roots in the httpd.conf I then changed it to the new website i am designing but everything stopped.

Hope you don’t mind this is my httpd.conf


This is the main Apache HTTP server configuration file. It contains the configuration directives that give the server its instructions.

See <URL:http://httpd.apache.org/docs/2.2&gt; for detailed information.

In particular, see <URL:http://httpd.apache.org/docs/2.2/mod/directives.html&gt; for a discussion of each configuration directive.

Do NOT simply read the instructions in here without understanding what they do. They’re here only as hints or reminders. If you are unsure consult the online docs. You have been warned.

Configuration and logfile names: If the filenames you specify for many of the server’s control files begin with “/” (or “drive:/” for Win32), the server will use that explicit path. If the filenames do not begin with “/”, the value of ServerRoot is prepended – so “logs/foo.log” with ServerRoot set to “C:/Program Files/Apache Software Foundation/Apache2.2/conf” will be interpreted by the server as “C:/Program Files/Apache Software Foundation/Apache2.2/conf/logs/foo.log”.

NOTE: Where filenames are specified, you must use forward slashes instead of backslashes (e.g., “c:/apache” instead of “c:\apache”). If a drive letter is omitted, the drive on which httpd.exe is located will be used by default. It is recommended that you always supply an explicit drive letter in absolute paths to avoid confusion.

ServerRoot: The top of the directory tree under which the server’s configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point ServerRoot at a non-local disk, be sure to point the LockFile directive at a local disk. If you wish to share the same ServerRoot for multiple httpd daemons, you will need to change at least LockFile and PidFile.

ServerRoot “C:/Program Files/Apache Software Foundation/Apache2.2/conf”

Listen: Allows you to bind Apache to specific IP addresses and/or ports, instead of the default. See also the <VirtualHost> directive.

Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses.

##Listen 12.34.56.78:80
Listen 80

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you have to place corresponding `LoadModule’ lines at this location so the directives contained in it are actually available before they are used.

Statically compiled modules (those listed by `httpd -l’) do not need to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_alias_module modules/mod_authn_alias.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule cache_module modules/mod_cache.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule charset_lite_module modules/mod_charset_lite.so
LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dav_lock_module modules/mod_dav_lock.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
LoadModule expires_module modules/mod_expires.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule filter_module modules/mod_filter.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule speling_module modules/mod_speling.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule status_module modules/mod_status.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule version_module modules/mod_version.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>

If you wish httpd to run as a different user or group, you must run: httpd as root initially and it will switch.

User/Group: The name (or #number) of the user/group to run httpd as.

It is usually good practice to create a dedicated user and group for running httpd, as with most system services.

User daemon
Group daemon

</IfModule>
</IfModule>

‘Main’ server configuration

The directives in this section set up the values used by the ‘main’ server, which responds to any requests that aren’t handled by a <VirtualHost> definition. These values also provide defaults for any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers, in which case these default settings will be overridden for the virtual host being defined.

ServerAdmin: Your address, where problems with the server should be e-mailed. This address appears on some server-generated pages, such as error documents. e.g. admin@your-domain.com

ServerAdmin admin@localhost

ServerName gives the name and port that the server uses to identify itself. This can often be determined automatically, but we recommend you specify it explicitly to prevent problems during startup.

If your host doesn’t have a registered DNS name, enter its IP address here.

##ServerName localhost:80

DocumentRoot: The directory out of which you will serve your documents. By default, all requests are taken from this directory, but symbolic links and aliases may be used to point to other locations.

DocumentRoot “C:/Sugarsweetoccasions”

Each directory to which Apache has access can be configured with respect to which services and features are allowed and/or disabled in that directory (and its subdirectories).

First, we configure the “default” to be a very restrictive set of features.

<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>

Note that from this point forward you must specifically allow particular features to be enabled - so if something’s not working as you might expect, make sure that you have specifically enabled it below.

This should be changed to whatever you set DocumentRoot to.

<Directory “C:/Sugarsweetoccasions”>

 Possible values for the Options directive are "None", "All",
 or any combination of:
 Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews

 Note that "MultiViews" must be named *explicitly* --- "Options All" doesn't give it to you.

### The Options directive is both complicated and important.  Please see http://httpd.apache.org/docs/2.2/mod/core.html options for more information.

Options Indexes FollowSymLinks


 AllowOverride controls what directives may be placed in .htaccess files.
 It can be "All", "None", or any combination of the keywords:
  Options FileInfo AuthConfig Limit

AllowOverride None


 Controls who can get stuff from this server.

Order allow,deny
Allow from all

</Directory>

DirectoryIndex: sets the file that Apache will serve if a directory is requested.

<IfModule dir_module>
DirectoryIndex index.html
</IfModule>

The following lines prevent .htaccess and .htpasswd files from being viewed by Web clients.

<FilesMatch “^\.ht”>
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>

ErrorLog: The location of the error log file.
If you do not specify an ErrorLog directive within a <VirtualHost>
container, error messages relating to that virtual host will be
logged here. If you do define an error logfile for a <VirtualHost>
container, that host’s errors will be logged there and not here.

ErrorLog “logs/error.log”

LogLevel: Control the number of messages logged to the error_log.
Possible values include: debug, info, notice, warn, error, crit, alert, emerg.

LogLevel warn

<IfModule log_config_module>

#### The following directives define some format nicknames for use with a CustomLog directive (see below).

LogFormat "%h %l %u %t \\"%r\\" %&gt;s %b \\"%{Referer}i\\" \\"%{User-Agent}i\\"" combined
LogFormat "%h %l %u %t \\"%r\\" %&gt;s %b" common

&lt;IfModule logio_module&gt;
  # You need to enable mod_logio.c to use %I and %O
  LogFormat "%h %l %u %t \\"%r\\" %&gt;s %b \\"%{Referer}i\\" \\"%{User-Agent}i\\" %I %O" combinedio
&lt;/IfModule&gt;

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a &lt;VirtualHost&gt;
# container, they will be logged here.  Contrariwise, if you *do*
# define per-&lt;VirtualHost&gt; access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog "logs/access.log" common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog "logs/access.log" combined

</IfModule>

<IfModule alias_module>

# Redirect: Allows you to tell clients about documents that used to 
# exist in your server's namespace, but do not anymore. The client 
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://localhost/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL.  You will also likely
# need to provide a &lt;Directory&gt; section to allow access to
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts. 
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client.  The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/conf/cgi-bin/"

</IfModule>

<IfModule cgid_module>

 ScriptSock: On threaded servers, designate the path to the UNIX
 socket used to communicate with the CGI daemon of mod_cgid.

Scriptsock logs/cgisock

</IfModule>

“C:/Program Files/Apache Software Foundation/Apache2.2/conf/cgi-bin” should be changed to whatever your ScriptAliased
CGI directory exists, if you have that configured.

<Directory “C:/PHP”>
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

DefaultType: the default MIME type the server will use for a document
if it cannot otherwise determine one, such as from filename extensions.
If your server contains mostly text or HTML documents, “text/plain” is
a good value. If most of your content is binary, such as applications
or images, you may want to use “application/octet-stream” instead to
keep browsers from trying to display binary files as though they are text.

DefaultType text/plain

<IfModule mime_module>

 TypesConfig points to the file containing the list of mappings from
 filename extension to MIME-type.

TypesConfig conf/mime.types


 AddType allows you to add to or override the MIME configuration
 file specified in TypesConfig for specific file types.

AddType application/x-gzip .tgz

AddEncoding allows you to have certain browsers uncompress
 information on the fly. Note: Not all browsers support this.

AddEncoding x-compress .Z
AddEncoding x-gzip .gz .tgz

 If the AddEncoding directives above are commented-out, then you
 probably should define those extensions to indicate media types:

AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz


 AddHandler allows you to map certain file extensions to "handlers":
 actions unrelated to filetype. These can be either built into the server
 or added with the Action directive (see below)

 To use CGI scripts outside of ScriptAliased directories:
 (You will also need to add "ExecCGI" to the "Options" directive.)

AddHandler cgi-script .cgi

 For type maps (negotiated resources):
#AddHandler type-map var


Filters allow you to process content before it is sent to the client.

 To parse .shtml files for server-side includes (SSI):
 (You will also need to add "Includes" to the "Options" directive.)

AddType text/html .shtml
AddOutputFilter INCLUDES .shtml

</IfModule>

The mod_mime_magic module allows the server to use various hints from the
contents of the file itself to determine its type. The MIMEMagicFile
directive tells the module where the hint definitions are located.

MIMEMagicFile conf/magic

Customizable error responses come in three flavors:

  1. plain text 2) local redirects 3) external redirects

Some examples:
ErrorDocument 500 “The server made a boo boo.”
ErrorDocument 404 /missing.html
ErrorDocument 404 “/cgi-bin/missing_handler.pl”
ErrorDocument 402 http://localhost/subscription_info.html

EnableMMAP and EnableSendfile: On systems that support it,
memory-mapping or the sendfile syscall is used to deliver
files. This usually improves server performance, but must
be turned off when serving from networked-mounted
filesystems or if support for these functions is otherwise
broken on your system.

EnableMMAP off
EnableSendfile off

Supplemental configuration

The configuration files in the conf/extra/ directory can be
included to add extra features or to modify the default configuration of
the server, or you may simply copy their contents here and change as
necessary.

Server-pool management (MPM specific)
Include conf/extra/httpd-mpm.conf

Multi-language error messages
nclude conf/extra/httpd-multilang-errordoc.conf

Fancy directory listings
Include conf/extra/httpd-autoindex.conf

Language settings
Include conf/extra/httpd-languages.conf

User home directories
Include conf/extra/httpd-userdir.conf

Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

Virtual hosts
Include conf/extra/httpd-vhosts.conf

Local access to the Apache HTTP Server Manual
Include conf/extra/httpd-manual.conf

Distributed authoring and versioning (WebDAV)
Include conf/extra/httpd-dav.conf

Various default settings
Include conf/extra/httpd-default.conf

Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf

Note: The following must must be present to support starting without SSL on platforms with no /dev/random equivalent but a statically compiled-in mod_ssl.

<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

BEGIN PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
PHPIniDir “”
LoadModule php5_module “php5apache2_2.dll”
#END PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL


helen :frowning:

helen,

Argh! That’s a dirty trick! Did you even TRY my #1 request above? That would be the reason restart isn’t available (in the monitor) - it can’t start in the first place (because some other program’s hijacked port 80)!

You also have another more serious problem: You’ve installed into the Program Files directory. NEVER install Apache into Program Files (because WinDoze over-protects everything in there which makes editing files - including your htdocs files - nearly impossible). Solution: Uninstall Apache, STOP AND PREVENT AUTOSTART ON ANY OTHER SERVICE WHICH USES PORT 80, then reinstall Apache OUTSIDE WinDoze protected directories (I’ve created a dedicated disk partition for Apache and PHP and use it for all my virtual hosts, too). If you don’t, you’re forced to run Apache as ROOT (no limit on privileges - a major security issue) not to mention the difficulty changing files within WinDoze’s protected directory.

Okay, I’ve run WinMerge on your httpd.conf against my test server and found the following:


ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2/conf" [COLOR="#FF0000"]should be just to Apache2.2, NOT conf![/COLOR]

#LoadModule rewrite_module modules/mod_rewrite.so
#LoadModule speling_module modules/mod_speling.so

[COLOR="#FF0000"]I'd uncomment those two while you're at it as they're both quite useful[/COLOR]


#ServerName localhost:80 [COLOR="#FF0000"]UNcomment[/COLOR]

DocumentRoot "C:/Sugarsweetoccasions" [COLOR="#FF0000"]- this may or may not work. It should be Apache's htdocs folder which is standard. You can use virtual hosts to point to virtual domains elsewhere[/COLOR]

<Directory />
    Options FollowSymLinks
    AllowOverride None[COLOR="#FF0000"] - ALL if you're going to use mod_rewrite[/COLOR]
    Order deny,allow
    Deny from all [COLOR="#FF0000"]- Allow from all on your test server[/COLOR]
</Directory>

<Directory "C:/Sugarsweetoccasions">[COLOR="#FF0000"] - as above[/COLOR]

    AllowOverride None[COLOR="#FF0000"] - All - again for mod_rewrite on a test server[/COLOR]

<IfModule dir_module>
    DirectoryIndex [COLOR="#FF0000"]index.php[/COLOR] index.html [COLOR="#FF0000"]- I would add index.php so you don't have to specify that in your DirectoryIndex statements throughout your virtual hosts[/COLOR]
</IfModule>


    ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/conf/cgi-bin/" - more WinDoze problems



# Virtual hosts
#Include conf/extra/httpd-vhosts.conf [COLOR="#FF0000"]- ENABLE virtual hosts (via httpd-vhosts.conf file) by uncommenting here![/COLOR]



#BEGIN PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
PHPIniDir ""[COLOR="#FF0000"] - insufficient (is PHP installed in your C:\\ directory?)[/COLOR]
LoadModule php5_module "php5apache2_2.dll"
[COLOR="#FF0000"]Type Handler is missing

Remove this garbage and use the following (replacing W:/PHP/ with your PHP directory):
PHPIniDir "W:/PHP/"
LoadModule php5_module "W:/PHP/php5apache2_2.dll"
AddType application/x-httpd-php .php
[/COLOR]
#END PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL

Lots of problems but PLEASE start with services.msc and turn off other services using port 80.

Regards,

DK

Thanks very much i’ve uninstalled apache last night and you may be correct about port 80 being hijacked some random IDM keep pop up when windows starts need to get rid of that wasn’t there before during that time I think my apache stopped working.

Before I install apache and php again perhaps if you don’t mind I ask a few questions.

Would the best place to install apache and php in C:/ folders?
What is the best tutorial to follow for installing apache and php?

This is the tutorials I’ve followed a tutorial please see link below

In meantime I shall pop to apache.org and see what I can find. I’ve saved your edited version of the httpd.conf and shall refer to that also.

helen

helen,

Where: I created a partitioned drive (W: for “web”) and have Apache, PHP, PHPMyAdmin and all my virtual hosts on that drive - MySQL can be installed as a service so it can go in Program Files.

Best Tutorial: I can’t attest to the “best” but I started with Kevin Yank’s book (first edition, now fifth edition: http://www.sitepoint.com/books/phpmysql5/) and made a few modifications based on Windows problems (IIS was started on port 80 by default in those days). I used Chapter 1 (a FREE download) to create a checklist and only looked back when I upgraded to Win7 (the Program Files problem caused me major problems). I have not viewed his 5th edition free chapter to see whether that’s been picked up (or that Skype will also try to hijack port 80 - but I’ve never had that problem) but I’ll still recommend the book (if you need some information on PHP (I did - and have built upon that base) or just the free chapters if all you need is the installation of the test server.

Regards,

DK

I’ve uninstalled and re-installed apache i’m still having problem with instally php with apache but I shall sort it out at a later time. For now apache is going ok and I can browse my website via localhost.

Thanks for the links for book tutorials I definitely need to invest on some books especially css style tutorials.

Helen

helen,

You’re welcome. As I explained, that book (Ver 1) was what started me with PHP and I feel very comfortable using that to do just about anything (that jQuery can’t do). However, your question dealt with setting up a server and all you need to do now is run the PHP installation program again (or merely change the php.ini where your Apache files are specified.

Regards,

DK