• Resolved anuj9122

    (@anuj9122)


    When i clicked on any products i get 404 page not found. Website is working on my own server.

    The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    I’m not sure what’s going on, but this is the content of your site:

    
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
       "https://www.w3.org/TR/html4/strict.dtd">
    <html>
    
    <head>
      <title>57deal.com</title>  
      <meta name="description" content="">
      <meta name="keywords" content="">
    </head>
    <frameset rows="100%,*" border="0">
      <frame src="https://hmail.hmail.us:8100/" frameborder="0" />
    </frameset>
    
    </html>

    and the site you’re framing does not respond.

    Thread Starter anuj9122

    (@anuj9122)

    I am using domian forwarding. You can use this link. https://hmail.hmail.us:8100/ to open the website. I get error 404 not found when i click on any product.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Wow, I hop[e you’re not doing this as a production site. It’s taken over 2 minutes before I even start seeing content.

    How are you hosting that site? I suspect that it may not be respecting .htaccess.

    Thread Starter anuj9122

    (@anuj9122)

    How are you hosting that site?
    -> I have my own server at my home. (Localhost).

    I suspect that it may not be respecting .htaccess.
    –> How to solve this?

    This is the .htaccess file

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    • This reply was modified 5 years, 5 months ago by anuj9122.
    Thread Starter anuj9122

    (@anuj9122)

    This is the .htaccess file

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    • This reply was modified 5 years, 5 months ago by anuj9122.
    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Are you using Apache? If so, look in the config files for this host and find “AllowOverride None”. Change that to “AllowOverride All” and restart Apache.

    Thread Starter anuj9122

    (@anuj9122)

    <VirtualHost *:80>
    DocumentRoot “/var/www/57deal.com”
    ServerName 57deal.com
    <Directory “/var/www/57deal.com”>
    allow from all
    Options None
    Require all granted
    </Directory>
    Alias /awstatsclasses “/usr/share/awstats/lib/”
    Alias /awstats-icon “/usr/share/awstats/icon/”
    Alias /awstatscss “/usr/share/doc/awstats/examples/css”
    ScriptAlias /awstats/ /usr/lib/cgi-bin/
    Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
    </VirtualHost>

    Thread Starter anuj9122

    (@anuj9122)

    This is the original apache conf file

    # This is the main Apache server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See https://httpd.apache.org/docs/2.4/ for detailed information about
    # the directives and /usr/share/doc/apache2/README.Debian about Debian specific
    # hints.
    #
    #
    # Summary of how the Apache 2 configuration works in Debian:
    # The Apache 2 web server configuration in Debian is quite different to
    # upstream’s suggested way to configure the web server. This is because Debian’s
    # default Apache2 installation attempts to make adding and removing modules,
    # virtual hosts, and extra configuration directives as flexible as possible, in
    # order to make automating the changes and administering the server as easy as
    # possible.

    # It is split into several files forming the configuration hierarchy outlined
    # below, all located in the /etc/apache2/ directory:
    #
    # /etc/apache2/
    # |– apache2.conf
    # | `– ports.conf
    # |– mods-enabled
    # | |– *.load
    # | `– *.conf
    # |– conf-enabled
    # | `– *.conf
    # `– sites-enabled
    # `– *.conf
    #
    #
    # * apache2.conf is the main configuration file (this file). It puts the pieces
    # together by including all remaining configuration files when starting up the
    # web server.
    #
    # * ports.conf is always included from the main configuration file. It is
    # supposed to determine listening ports for incoming connections which can be
    # customized anytime.
    #
    # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
    # directories contain particular configuration snippets which manage modules,
    # global configuration fragments, or virtual host configurations,
    # respectively.
    #
    # They are activated by symlinking available configuration files from their
    # respective *-available/ counterparts. These should be managed by using our
    # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
    # their respective man pages for detailed information.
    #
    # * The binary is called apache2. Due to the use of environment variables, in
    # the default configuration, apache2 needs to be started/stopped with
    # /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
    # work with the default configuration.

    # Global configuration
    #

    #
    # ServerRoot: The top of the directory tree under which the server’s
    # configuration, error, and log files are kept.
    #
    # NOTE! If you intend to place this on an NFS (or otherwise network)
    # mounted filesystem then please read the Mutex documentation (available
    # at <URL:https://httpd.apache.org/docs/2.4/mod/core.html#mutex&gt;);
    # you will save yourself a lot of trouble.
    #
    # Do NOT add a slash at the end of the directory path.
    #
    #ServerRoot “/etc/apache2”

    #
    # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
    #
    #Mutex file:${APACHE_LOCK_DIR} default

    #
    # The directory where shm and other runtime files will be stored.
    #

    DefaultRuntimeDir ${APACHE_RUN_DIR}

    #
    # PidFile: The file in which the server should record its process
    # identification number when it starts.
    # This needs to be set in /etc/apache2/envvars
    #
    PidFile ${APACHE_PID_FILE}

    #
    # Timeout: The number of seconds before receives and sends time out.
    #
    Timeout 300

    #
    # KeepAlive: Whether or not to allow persistent connections (more than
    # one request per connection). Set to “Off” to deactivate.
    #
    KeepAlive On

    #
    # MaxKeepAliveRequests: The maximum number of requests to allow
    # during a persistent connection. Set to 0 to allow an unlimited amount.
    # We recommend you leave this number high, for maximum performance.
    #
    MaxKeepAliveRequests 100

    #
    # KeepAliveTimeout: Number of seconds to wait for the next request from the
    # same client on the same connection.
    #
    KeepAliveTimeout 5

    # These need to be set in /etc/apache2/envvars
    User ${APACHE_RUN_USER}
    Group ${APACHE_RUN_GROUP}

    #
    # HostnameLookups: Log the names of clients or just their IP addresses
    # e.g., https://www.apache.org (on) or 204.62.129.132 (off).
    # The default is off because it’d be overall better for the net if people
    # had to knowingly turn this feature on, since enabling it means that
    # each client request will result in AT LEAST one lookup request to the
    # nameserver.
    #
    HostnameLookups Off

    # 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 ${APACHE_LOG_DIR}/error.log

    #
    # LogLevel: Control the severity of messages logged to the error_log.
    # Available values: trace8, …, trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the log level for particular modules, e.g.
    # “LogLevel info ssl:warn”
    #
    LogLevel warn

    # Include module configuration:
    IncludeOptional mods-enabled/*.load
    IncludeOptional mods-enabled/*.conf

    # Include list of ports to listen on
    Include ports.conf

    # Sets the default security model of the Apache2 HTTPD server. It does
    # not allow access to the root filesystem outside of /usr/share and /var/www.
    # The former is used by web applications packaged in Debian,
    # the latter may be used for local directories served by the web server. If
    # your system is serving content from a sub-directory in /srv you must allow
    # access here, or in any related virtual host.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Require all denied
    </Directory>

    <Directory /usr/share>
    AllowOverride None
    Require all granted
    </Directory>

    <Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
    </Directory>

    #<Directory /srv/>
    # Options Indexes FollowSymLinks
    # AllowOverride None
    # Require all granted
    #</Directory>

    # AccessFileName: The name of the file to look for in each directory
    # for additional configuration directives. See also the AllowOverride
    # directive.
    #
    AccessFileName .htaccess

    #
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    #
    <FilesMatch “^\.ht”>
    Require all denied
    </FilesMatch>

    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive.
    #
    # These deviate from the Common Log Format definitions in that they use %O
    # (the actual bytes sent including headers) instead of %b (the size of the
    # requested file), because the latter makes it impossible to detect partial
    # requests.
    #
    # Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
    # Use mod_remoteip instead.
    #
    LogFormat “%v:%p %h %l %u %t \”%r\” %>s %O \”%{Referer}i\” \”%{User-Agent}i\”” vhost_combined
    LogFormat “%h %l %u %t \”%r\” %>s %O \”%{Referer}i\” \”%{User-Agent}i\”” combined
    LogFormat “%h %l %u %t \”%r\” %>s %O” common
    LogFormat “%{Referer}i -> %U” referer
    LogFormat “%{User-agent}i” agent

    # Include of directories ignores editors’ and dpkg’s backup files,
    # see README.Debian for details.

    # Include generic snippets of statements
    IncludeOptional conf-enabled/*.conf

    # Include the virtual host configurations:
    IncludeOptional sites-enabled/*.conf

    # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

    Include /etc/phpmyadmin/apache.conf

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    In whichever location you’ve put your WP files, change AllowOverride None to AllowOverride All.

    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Require all denied
    </Directory>
    
    <Directory /usr/share>
    AllowOverride None
    Require all granted
    </Directory>
    
    <Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
    </Directory>
    
    #<Directory /srv/>
    # Options Indexes FollowSymLinks
    # AllowOverride None
    # Require all granted
    #</Directory>
    Thread Starter anuj9122

    (@anuj9122)

    website is in /var/www/html/ . I have done this.

    <Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
    </Directory>

    All website are down

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    That should not have crashed Apache. Check that you didn’t make any other changes and check your system (and apache) error logs.

    Note that you are not having a WordPress problem, you’re having a sysadmin problem.

    Thread Starter anuj9122

    (@anuj9122)

    I have done only in this

    <Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
    </Directory>

    Let me revert back

    Thread Starter anuj9122

    (@anuj9122)

    Now its working

    Thread Starter anuj9122

    (@anuj9122)

    Thanks for guiding me.Need this code in apache virtual host conf file

    <Directory “/var/www/projectok.com”>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Order allow,deny
    allow from all
    </Directory>

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘404 page not fouund’ is closed to new replies.