Ok, so I just recently ran into this issue.
I added a domain (moneystationiowa.com) to my Virtualmin Pro server. NO PROBLEM
This is going to be the commercial/public website for one of my clients.
I'm developing a "web based" software/crm for them to use. They want this to run on a SSL enabled site with a slightly different domain name (moneystationiowa.net)!
When I tried to register moneystationiowa.net I get the following error:
Failed to create virtual server : A MySQL user named moneystationiowa already exists
So...
I remembered that you could assign a different Administration username using the "Custom username" option instead of the "Automatic" option. Using this feature I tried to set the username to moneystationiowanet instead of the default/automatic username of moneystationiowa.
Then I tried again to register moneystationiowa.net and got the same error, exactly!
Both sites need MySQL, but it seems like it is trying to create the MySQL username from the "Domain name" field instead of from the "Administration username - Custom username" field. Or, maybe it is truncating the "moneystationiowanet" in the "Administration username - Custom username" field, to "moneystationiowa" which shouldn't be happening either!
PLZ Advise!
Comments
Submitted by bamajr on Tue, 11/03/2009 - 17:28 Comment #1
FYI: I attached an image of the System Information screen to save all the "back and forth" on what is running on my system.
Submitted by JamieCameron on Tue, 11/03/2009 - 18:29 Comment #2
So the issue here is that MySQL puts a 16-character limit on usernames, so even if the admin login differs there can still be a clash.
Why not create this other domain as a sub-server? That way it shares the same MySQL account, and there's no clash ..
Submitted by bamajr on Wed, 11/04/2009 - 10:45 Comment #3
After posting this issue last night, I wondered about the MySQL limit...
There is no reason why I can't use the domain as a sub-server unless: - there will be issues related to separate mail delivery. - there will be issues using separate MySQL Databases between both servers.
Submitted by JamieCameron on Wed, 11/04/2009 - 12:04 Comment #4
With a sub-server, mail delivery is still completely separate .. and each domain can have its own databases.
Submitted by bamajr on Wed, 11/04/2009 - 12:20 Comment #5
I thought this to be true, but as the second domain will actually be a separate, fully functional web site, I need it to have all (or most) of the functionality of the first domain. Thus the reason I was checking!
So, just to be sure, what features/functionality will the second/sub-domain loose, that the first/primary-domain will still have?
Submitted by bamajr on Wed, 11/04/2009 - 12:21 Comment #6
Submitted by JamieCameron on Wed, 11/04/2009 - 12:22 Comment #7
The sub-server doesn't lose any functionality - however, it will share the same SSH, FTP and MySQL login with the top-level server. So a sub-server is only suitable if it is being managed by the same customer or person as the top-level server.
Submitted by bamajr on Wed, 11/04/2009 - 12:42 Comment #8
Okay Jamie - thanks!
I think that resolves everything here! I've set the status as closed!