Wordpress Installation Not showing

Hey everyone, decided to rebuilt my system and everything went fine until I wanted to install wordpress. I have all the files places and extracted but when I go to my site, 192.155.91.187 , I can not seem to get wordpress to start its installation. Any thoughts?

14 Replies

A quick guess. You've set up virtual hosts and apache is responding to the default host when using 192.155.91.187 instead of your domain.

What's the contents of your apache config files?

Haven't figured it out myself, Heres my apache2.conf

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# 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.  
#
# The configuration directives are grouped into three basic sections:
#  1\. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2\. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3\. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# 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 "/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# 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 LockFile documentation (available
# at <url:http: httpd.apache.org="" docs-2.1="" mod="" mpm_common.html#lockfile="">);
# 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.
#
# <ifmodule !mpm_winnt.c=""># <ifmodule !mpm_netware.c="">LockFile /var/lock/apache2/accept.lock
#</ifmodule>
#</ifmodule>

#
# 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 15

##
## Server-Pool Size Regulation (MPM specific)
## 

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
 <ifmodule mpm_prefork_module="">StartServers          2
    MinSpareServers       6
    MaxSpareServers      12
    MaxClients          30
    MaxRequestsPerChild   3000</ifmodule> 

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
 <ifmodule mpm_worker_module="">StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75 
    ThreadLimit          64
    ThreadsPerChild      25
    MaxClients          150
    MaxRequestsPerChild   0</ifmodule> 

# event MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
 <ifmodule mpm_event_module="">StartServers          2
    MaxClients          150
    MinSpareThreads      25
    MaxSpareThreads      75 
    ThreadLimit          64
    ThreadsPerChild      25
    MaxRequestsPerChild   0</ifmodule> 

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

#
# 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. 
#
 <files ~="" "^\.ht"="">Order allow,deny
    Deny from all
    Satisfy all</files> 

#
# DefaultType is 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

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., 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 /var/log/apache2/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

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

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
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

#
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined

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

# Include generic snippets of statements
Include /etc/apache2/conf.d/

# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/</virtualhost></virtualhost></url:http:> 

What about the files in /etc/apache2/sites-enabled/ ?

````

domain: bwsurfshop.com

public: /home/hyper/public/bwsurfshop.com/

# Admin email, Server Name (domain name), and any aliases
ServerAdmin webmaster@bwsurfshop.com
ServerName www.bwsurfshop.com
ServerAlias bwsurf.com

# Index file and Document Root (where the public files are located)
DirectoryIndex index.html index.php
DocumentRoot /home/hyper/public/bwsurfshop.com/public

# Log file locations
LogLevel warn
ErrorLog /home/hyper/public/bwsurfshop.com/log/error.log
CustomLog /home/hyper/public/bwsurfshop.com/log/access.log combined

Here is my site file under sites-enabled for bwsurfshop.com

ServerAdmin webmaster@localhost

DocumentRoot /var/www
 <directory>Options FollowSymLinks
    AllowOverride None</directory> 
 <directory var="" www="">Options Indexes FollowSymLinks MultiViews
    AllowOverride None
    Order allow,deny
    allow from all</directory> 

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
 <directory "="" usr="" lib="" cgi-bin"="">AllowOverride None
    Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
    Order allow,deny
    Allow from all</directory> 

ErrorLog /var/log/apache2/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog /var/log/apache2/access.log combined

Alias /doc/ "/usr/share/doc/"
<directory "="" usr="" share="" doc="">Options Indexes MultiViews FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    Allow from 127.0.0.0/255.0.0.0 ::1/128</directory></virtualhost> 

````

and here is the default file

Your default site's DocumentRoot (/var/www) points to a different directory than your bwsurfshop.com DocumentRoot (/home/hyper/public/bwsurfshop.com/public).

Since you are trying to access your server by IP address rather than using DNS to resolve the domain name you need to have your default site's DocumentRoot point to your actual wordpress install.

Apache doesn't know that you want bwsurfshop.com because you're not requesting it (you're requesting the default site).

Does this mean I want to move my wordpress files over to /home/hyper/public/bwsurfshop.com/public and change the path in the default aswell?

My wordpress files are located in, /srv/www/bwsurfshop.com/public_html . would I just want to change the links to point to that? Also, I am using the DNS manager to get my domain www.bwsurfshop.com if that makes a difference using godaddy as a provider.

If you don't have your Wordpress files in "/home/hyper/public/bwsurfshop.com/public" then where do you have them? That's where the bwsurfshop.com vhost file is pointing.

You should put your Wordpress files where you want them (as long as it's a logical location - /root/bin/oops/maybe/heretheyare is NOT a good location :wink:). This location should be readable by the outside world (eg, group = www-data). You should then point the DocumentRoot of your default site vhost file to the same location as you have put the Wordpress files (this will let your IP address access the site).

If you are ever going to use DNS name resolution to get to your website (rather than just the IP address) then you should also have the DocumentRoot in your bwsurfshop.com vhost file point to the location your Wordpress files are located.

If at some point you don't want your IP address to resolve to the bwsurfshop.com Wordpress install anymore you'll have to change the DocumentRoot of the default vhost file to something else.

Remember to restart apache after you've made any changes to the vhost files (# service apache2 restart).

Thanks for all the help! Implementing these changes now, will let you know what happens in a few minutes!

Ok so I have all of my core wordpress files extracted to /home/hyper/public/bwsurfshop.com/public

Here is my default

 <virtualhost *:80="">ServerAdmin webmaster@localhost

    DocumentRoot /home/hyper/public/bwsurfshop.com/public
     <directory>Options FollowSymLinks
        AllowOverride None</directory> 
     <directory home="" hyper="" public="" bwsurfshop.com="">Options Indexes FollowSymLinks MultiViews
        AllowOverride None
        Order allow,deny
        allow from all</directory> 

    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
     <directory "="" usr="" lib="" cgi-bin"="">AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Order allow,deny
        Allow from all</directory> 

    ErrorLog /var/log/apache2/error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog /var/log/apache2/access.log combined

    Alias /doc/ "/usr/share/doc/"
    <directory "="" usr="" share="" doc="">Options Indexes MultiViews FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from 127.0.0.0/255.0.0.0 ::1/128</directory></virtualhost> 

Here is my bwsurfshop.com cfg

domain: bwsurfshop.com
# public: /home/hyper/public/bwsurfshop.com/public

 <virtualhost *:80=""># Admin email, Server Name (domain name), and any aliases
  ServerAdmin webmaster@bwsurfshop.com
  ServerName  www.bwsurfshop.com
  ServerAlias bwsurf.com

  # Index file and Document Root (where the public files are located)
  DirectoryIndex index.html index.php
  DocumentRoot /home/hyper/public/bwsurfshop.com/public

  # Log file locations
  LogLevel warn
  ErrorLog  /home/hyper/public/bwsurfshop.com/log/error.log
  CustomLog /home/hyper/public/bwsurfshop.com/log/access.log combined</virtualhost> 

Still nothing, any thoughts?

It seems my ip adress will work to get to the WP files but not bwsurfshop.com is this an issue in the DNS manager?

Take that back, it worked for a second and now its not Not sure whats going on here lol

EDIT :: Major fail I think, had my DNS taken off by accident, should work once I add the master dns bwsurfshop.com correct? The servers clear every 15minutes as well correct? Excited to get my site up!! :D :D

EDIT EDIT :: No luck with those setting above with DNS up. Totally lost now haha

Both bwsurfshop.com and http://www.bwsurfshop.com resolves to 192.155.91.187 - so that seems to be working (unless you hosed it up and it just hasn't propagated out yet).

So it's probably just your webserver setup.

The default web page location is /var/www/ why are you changing it to the mile long path under home?

Where did you put the wordpress files?

Did you setup the database?

I have my WP files under /home/hyper/public/bwsurfshop.com/public right now ; therefore both of those .cfg files need to point to that right?

Im so confused as to where each of these files needs to point to.

I do have a database made and thought it was all set up but that may not be the case ; my db name is 'bwsurfdb'

www.bwsurfshop.com and bwsurfshop.com are pointing to linode's nameservers but have no A records and 192.155.91.187 isn't responding to http requets, so something's gone terribly wrong. Make sure apache is running and check the Linode manager for DNS records.

Called it quits and just installed the normal wordpress stack script. Couldn't figure out which files needed to point where and I thought I had my DNS set up properly pointing to the IP to change to the domain but I guess not. Having a hard time finding out which config files generally need to be changed to get a site loaded and into a certain location. I have never worked with apache before so I have no idea which files are needed to get the site actually running. Any good guides or anything? Been running through the linode library guides for a little over a month now and keep falling short all the file linking between apache/website/dns/whatever else

EDIT :: Trying to go backwards from the wordpress stackscript to figure out which files need to be edited. Every time I change what tutorials and everyone says everything breaks. $100 for a one time set-up fee to simply get my site all linked up seems worth it right now. Updating and security seem to be the only parts I can get working properly.

EDIT EDIT :: Just installed wordpress stack script, finally got it all set even dns working properly! Just went through everything you all told me and realized that for the source is wants only /var/www nothing more. That kept effecting it for some reason. Thanks for all the help guys! Pretty sure I would know what to change now if I built my own stack. Very helpful awesome community thanks!

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct