3.0 network installation creates subdomain but resolves to server default page

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)

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. ??

Put stuff in the wrong file, the system does an update and… bye bye…

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”