Posted 1 year ago #
I am installing a networked version of 3.0, which will use subdomains rather than subfolders.
I created the wildcard dns correctly (I think) and changed the .htaccess file and made the changes to wp-config.php as well.
Anyone have an idea why this is happening? It seems as though I am close, but there may be one or two things missing.
Any assistance would be greatly appreciated.
Yes. you need to set a wildcard subdomain records in your DNS.
in A *.yourdomain.com.
Also check with your host to see if wildcard subdomains are enabled on your account on the server side.
Posted 1 year ago #
Thanks for your reply.
I have a dedicated server, so wildcard subdomains SHOULD not be an issue. It appears that the wildcard subdomain is set properly, but I am still getting the same result.
Could there be any additional causes?
Let me know...
Can I get a link so I can ping it?
Like I said above, wildcard subdomains are a two-step process. One for the DNS side, one for the server side.
Look in the vhost entry for your domain. Does it say:
Serveralias yourdomain.com *.yourdomain.com ?
Apache doesn't do this unless you tell it to.
Posted 1 year ago #
the link...
Are you looking for the domain? http://www.1ultima1.com
Next question: How do I find the vhost entry for my domain?
Final question: Do I need to make any changes to apache?
Getting closer, I hope...
Thanks!
Posted 1 year ago #
I have added the following to the apache file:
ServerName 1ultima1.com
ServerAlias 1ultima1.com *.1ultima1.com
DocumentRoot /your/doc/root/
ServerAdmin webmaster@1ultima1.comI found this on your blog, at: http://wpmututorials.com/how-to/enabling-wildcard-subdomains/
is this correct?
Yes.
DocumentRoot /your/doc/root/
Is this just a sample or do you really have it pointed to your doc root on the server? ;)
Posted 1 year ago #
No, this is the exact code I have in the apache file. Is that the right thing to do? If not, how should it be changed?
I was not sure of the syntax.
Also, how do I find the vhost entry for my domain? I still need to make that change as well.
Let me know...
Well, the part with your server name & alias should be in the apache vhost directive area.
The document root should state the actual full path on the server of where your install is.
That would certainly be the issue. ;)
Further reading:
http://httpd.apache.org/docs/2.2/vhosts/name-based.html
Posted 1 year ago #
I have made the change to the path. It is now /var/www/vhosts/1ultima1.com/httpdocs/ . However, it is STILL not working. I am still getting the default page.
Very frustrating!
I thought it was supposed to be easier!
Oh well...
Thoughts?
Well there is a certain level of technical competence you need to run a network, so installing it is the easy part. ;)
If you're mucking around in the server files, there's an assumption you know what you're doing or you're willing to learn it. :D
Did you restart the webserver?
And you added a wildcard subomain in your DNS records?
Posted 1 year ago #
Don't know everything, but I am willing to learn.
yes, I added the wildcard subdomain in the dns record.
I did not restart the webserver, because I do not know how.
Can you talk me down?
Posted 1 year ago #
If you have a cPanel installation with WHM, then you can restart Apache from within that, if you have some other type of control panel, there's still possibly an option to restart Apache.
If you are doing this from shell, then something like /etc/init.d/apache2 restart, but I'd recommend getting a lot more familiar with shell before tackling that.
Posted 1 year ago #
Try actually creating the sub-domain in your server admin panel (cpanel, plesk, etc.)
Posted 1 year ago #
Ignore what TheWiz said - listen to Andrea's early post -
Like I said above, wildcard subdomains are a two-step process. One for the DNS side, one for the server side.
Look in the vhost entry for your domain. Does it say:
Serveralias yourdomain.com *.yourdomain.com ?
Apache doesn't do this unless you tell it to.
/var/www/vhosts/1ultima1.com/httpdocs/ takes you to the ROOT of your hosting space - in cPanel the equivalent would be /home/public_html/
You need the path pointing at the folder where this domain is installed
- it might be - /var/www/vhosts/1ultima1.com/httpdocs/1ultima1/
Note - bad idea to put any site build directly into the root of your hosting space = hacker magnet and you'll be fighting them off forever.
Posted 1 year ago #
Forgot - if your path is using /httpdocs/ in it, are you using Plesk?
Plesk has particular problems with WPMU and WP3.0 subdomain installs - if you get the WP subdomains working, it knocks out your fixed-name subdomains such as pop3, smtp, mail, webmail, ftp and so on - you'll need to do some heavy digging to fix those issues after you get WP subdomains working.
Plesk uses a different set-up and stores config files everywhere. you need to add the wildcard subdomain in an extra included file, usually something like:
/var/www/vhosts/yourdomain.com/config/vhosts.conf
If you put it anywhere else, rebuilding Plesk will wipe it out.
(which may explain things from your other thread)
Posted 1 year ago #
Hmm yes - see what you're driving at - when I did the wipe and rebuild on that one, I can't remember how far up the folder tree I deleted.
Only problem with that logic though is that the /config/ folder is protected and not accessible to customers (me) - only to the hosting admins. The domain name top folder wouldn't have changed and I certainly didn't delete as high as /httpdocs/
Right, but the hosting admins can rebuild plesk and my point was that DOES wipe out any custom edits.
I've been fighting with a borked setup and plesk for a week, so that's how I know. :D
Put stuff in the wrong file, the system does an update and... bye bye...
Posted 1 year ago #
Late addition to this
@kcgleaton - don't forget too, that after getting the wildcard subdomain entry in vhosts.conf file, and setting the wildcard in DNS, and restarting Apache, you then also need to go back into the main blog admin and re-save the Permalinks in Settings - Permalinks
Doing that updates the htaccess file's rules for redirecting sub-blogs and "stuff"
This topic has been closed to new replies.
