New Subdomain sites not created

The problem is most likely that your wildcard subdomains are not set up properly. They’re probably pointing to new directories on your server, when they should all be pointing to the root directory in which WordPress is installed.

So in that case where the the change be made?
here is the htacces that WP generated at install.

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]

and here is the my vhosts file

ServerAlias *.mydomain.com

what more do i need to add to the vhost to make it point properly?

I found this:

1.<Directory /var/www/vhosts/mydomain.com/>
2.AllowOverride FileInfo Options
3.php_admin_flag safe_mode off
4.<Directory

On this page in the Codex: link from the codex.

First off, I’m not familiar with writing these apache codes, but line number for looks like its incomplete. Is that accurate?

Secondly, I did not have to add any extra configuration to my vhost for the install that ‘IS’ working fine.

Any ideas?

I would assume that line number 4 is supposed to be </Directory> rather than <Directory, but I’m not 100% certain. It’s been a while since I’ve set up wildcard subdomains on a server where I had access to any of the .conf files.

Hopefully someone else with more apache experience will come along and help out. As I said, though, from the sounds of it, the subdomains are pointing to their own individual virtual hosts rather than pointing to the root of the WordPress install.

I would assume that line number 4 is supposed to be </Directory> rather than <Directory, but I’m not 100% certain.

you are correct. ??

Thanks, Andrea. I fixed the codex entry.

@oadesign – Did you make sure to restart apache after making the changes to your vhosts.conf file?

Yes I did, several times. Probably the same amount of times I refreshed this page to see in anyone responds with a solution ??

But I noticed on other thing. Shouldn’t this line in the vhosts.conf:

<Directory /var/www/vhosts/mydomain.com/>

read like this?:

<Directory /var/www/vhosts/mydomain.com/httpdocs/>

Mind you I have tried it, but not sure if that is the only issue im having.

I believe the path in that line should be whatever the absolute path is to the directory in which your WordPress installation is stored. Therefore, if your WordPress index.php file is stored in /var/www/vhosts/mydomain.com/, use that. If it’s stored in /var/www/vhosts/mydomain.com/httpdocs/, use that. If it’s stored in /var/www/html/, use that, instead.

Alas, I could not wait any more. I spent quite some time trying to complete this myself, to no avail.

Mind you thin was hosted on a vps, most other details i handle on my own.
I broke down and put in a support ticket to my hosting provider. 15 min later, bam, done working like a charm.

Thanks to Curtiss and Andrea for your replies.

Probably the same amount of times I refreshed this page to see in anyone responds with a solution ??

Up there in the sidebar is the rss feed for the thread, and a subscribe by email link.

this way, for other threads, you can get notified, instead of constantly refreshing. ??