Title: First Install: Apache Problems, I Think&#8230;
Last modified: August 22, 2016

---

# First Install: Apache Problems, I Think…

 *  [PeterNYC](https://wordpress.org/support/users/peternyc/)
 * (@peternyc)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/)
 * Installed WP on my Linux Ubuntu box at home. First time installation. My intention
   is for a network of WP using the per-directory (not per-domain) method.
    -  WP installation: /usr/local/share/wordpress.
       Main website: /www/mydomain:
      I think WP network sites are in: /srv/www/wp-content
 * I currently have:
    -  /srv/www/wp-content/foo
       /srv/www/wp-content/bar /www/foo –> /srv/www/wp-
      content/foo (symlink) /www/bar –> /srv/www/wp-content/bar (symlink)
 * When I navigate to [http://mydomain.org/foo](http://mydomain.org/foo) I see 403
   forbidden, probably because there’s no index.html (or whatever) in that directory.
   Just this:
    -  blogs.dir/
       [@languages](https://wordpress.org/support/users/languages/) 
      [@plugins](https://wordpress.org/support/users/plugins/) [@themes](https://wordpress.org/support/users/themes/)
      upgrade/ uploads/
 * When I go to [http://mydomain.com/wordpress](http://mydomain.com/wordpress), 
   it looks like a blog without a theme or stylesheet.
 * When I go to [http://mydomain.com/wordpress/admin](http://mydomain.com/wordpress/admin),
   it looks more or less like a normal admin page. I think this is what it’s supposed
   to look like.
 * When I look at my Apache logs, I see this errors:
 * > Request exceeded the limit of 10 internal redirects due to probable configuration
   > error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use‘
   > LogLevel debug’ to get a backtrace., referer: [http://mydomain.org/wordpress/sample-page/](http://mydomain.org/wordpress/sample-page/)
 * So I *think* what’s wrong is Apache’s rewriting rules, which I *think* take urls
   like [http://www.mydomain.org](http://www.mydomain.org) and rewrites them to 
   take content from elsewhere in the filesystem.
 * I’m really not very knowledgeable about WP and Apache, so I’m out of my element
   here. Does anyone know what I should be focusing on? Help? 🙂

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [RossMitchell](https://wordpress.org/support/users/rossmitchell/)
 * (@rossmitchell)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635380)
 * I have been running localhosted websites on my Ubuntu setup for years.
 * I don’t understand:
 * > using the per-directory (not per-domain) method.
 * The only sense I can make of this is that you want your various websites to be
   accessed as:
 *     ```
       http://localhost/site1
       http://localhost/site2
       http://localhost/phpmyadmin
       ```
   
 * etc.
    And have the files located (or linked) at directories:
 *     ```
       /var/www/site1
       /var/www/site2
       /var/www/phpmyadmin
       ```
   
 * I find the localhost environment to be a much better reflection of the real internet
   if instead I configure my websites each as “VirtualHost”
    I strongly suggest 
   this alternative.
 *  Thread Starter [PeterNYC](https://wordpress.org/support/users/peternyc/)
 * (@peternyc)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635383)
 * I think we’re on the same page, but just to be sure, suppose the website is [http://www.site.org](http://www.site.org)
   and I have two blogs, named blog1 and blog2. I’d like requests for:
 * [http://www.site.org/blog1](http://www.site.org/blog1)
 * to go to blog1, and requests for:
 * [http://www.site.org/blog2](http://www.site.org/blog2)
 * to go to blog2, from a purely external point of view. I’m agnostic as to where
   the files and such are located, since this is my server. I’m free to do whatever.
 * From an internal point of view, suppose document root is /var/www/site. Then 
   I assume the symlinks need to be set as:
 * /var/www/site/blog1@ –> /usr/share/wordpress
    /var/www/site/blog2@ –> /usr/share/
   wordpress
 * There must be some kind of PHP variable to prefix MySQL table names to keep the
   blogs separate. Somehow, this PHP variable gets set differently depending on 
   whether you request [http://www.site.org/blog1](http://www.site.org/blog1) or
   [http://www.site.org/blog2](http://www.site.org/blog2). Maybe mod_rewrite helps
   with this.
 * I also gather that mod_rewrite must also help in translating URLs for image files
   and such from the WP installation dir, /usr/share/wordpress, to the content directory,/
   www/www/wp-content. I think the same thing goes for plugins and language files.
 * Is this the general way things work?
 *  [RossMitchell](https://wordpress.org/support/users/rossmitchell/)
 * (@rossmitchell)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635385)
 * Some of your expectations will not work.
 * > /var/www/site/blog1@ –> /usr/share/wordpress
   >  /var/www/site/blog2@ –> /usr/
   > share/wordpress
 * Your different websites must have distinct sets of files, for a starter the contents
   of “wp-config.php” are specific to each website. Similarly the files in “wp-content/
   uploads” are also different. Yes many of the files are the same across sites,
   still there are essential differences.
    Yes, there is a thing called multi-site,
   I do not believe it is appropriate to your situation.
 * Also:
 * > There must be some kind of PHP variable to prefix MySQL table names to keep
   > the blogs separate.
 * The way this happens is that each site has its own wp-config.php file.
 * Mod_rewrite is used to perform permalinks, it is possible to run sites without
   it.
 *  Thread Starter [PeterNYC](https://wordpress.org/support/users/peternyc/)
 * (@peternyc)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635386)
 * Maybe I misunderstood, then. For example, from [this](http://www.wpbeginner.com/wp-tutorials/how-to-install-and-setup-wordpress-multisite-network/)
   site:
 * >  On the other hand, if you choose sub-directories or path based URLs for subsites
   > on your network, then the only thing you need to do is enable pretty permalinks
   > on your root site.
 * This is spot-on what I was hoping to achieve. It sounds like it would apply to
   me. Is this not the case?
 *  [RossMitchell](https://wordpress.org/support/users/rossmitchell/)
 * (@rossmitchell)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635391)
 * By the look of this article, yes you should be able to run multisite your way.
   
   My opinion is that for a first time install, that multisite is a complication
   you could do without. You should have mentioned that you were configuring multisite
   from the very start, it changes everything. Your further questions more appropriate
   belong in the multisite support forum. Please close this thread.
 *  Thread Starter [PeterNYC](https://wordpress.org/support/users/peternyc/)
 * (@peternyc)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635433)
 * I thought when I mentioned “network of WP” in the original post it implies multisite(
   I thought “network” was the proper term for a “multisite”).
 * OK… I’ll post again in the proper forum.
 * Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘First Install: Apache Problems, I Think…’ is closed to new replies.

## Tags

 * [installation](https://wordpress.org/support/topic-tag/installation/)
 * [network](https://wordpress.org/support/topic-tag/network/)
 * [ubuntu](https://wordpress.org/support/topic-tag/ubuntu/)

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 6 replies
 * 2 participants
 * Last reply from: [PeterNYC](https://wordpress.org/support/users/peternyc/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/first-install-apache-problems-i-think/#post-5635433)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
