I just purchased a VPS system to host my blog network, and while everything's working, I'm still having a few lingering issues.
My domains are all hosted through another provider and point to the IP address of my VPS. My Network is configured to use subdomains:
*.eamann.com. All of the subdomains work, and I'm very happy with the network.
Next comes domain mapping. I installed the latest version of the WordPress MU Domain Mapping plug-in and configured it the same was as I did on my previous shared hosting. Once I had things set up, the regular .com domains were displaying the correct content. I'd use the regular .com domain to log in (
site.com/wp-admin) and I was redirected to the right subdomain and logged in to the system.
But this is where the weirdness started. When I went back to the front page of the site (the regular .com address), I was no longer logged in.
It's a confusing problem indeed, and I'm at my wit's end trying to figure it out. If you want to take a crack and try to help, here are the details.
- I'm running 9 sites in a Multisite network configured for subdomains.
- I'm using version 0.5.4 of WordPress MU Domain Mapping
- My VPS is running CentOS 5.5 with Apache 2.2.3, MySQL 5.0.77, and PHP 5.1.6
Below is the Virtual Host configuration I'm using in Apache to point everything at the right place. The domain I'm specifically having issues with is
prosepainting.com. It's supposedly the mapped domain for
prose.eamann.com. Both domains are hosted with 1and1 Internet and pointed to my VPS using an A Record (pointing to IP 22.214.171.124).
<VirtualHost *:80> ServerName prosepainting.com ServerAlias www.prosepainting.com *.prosepainting.com DocumentRoot /var/www/html/eamann </VirtualHost> <VirtualHost *:80> ServerName prose.eamann.com DocumentRoot /var/www/html/eamann </VirtualHost> <VirtualHost *:80> ServerName business.eamann.com DocumentRoot /var/www/html/eamann </VirtualHost> <VirtualHost *:80> ServerName eamann.com ServerAlias www.eamann.com *.eamann.com DocumentRoot /var/www/html/eamann </VirtualHost>
I'm pretty sure this is a configuration issue on my end, but I'm not sure where. Any idea where I should look or what I can do to diagnose?