installation on brand new server that will be new home for multiple websites on subdomains

4 posts / 0 new
Last post
#1 Tue, 06/14/2016 - 12:46
elcubismo

installation on brand new server that will be new home for multiple websites on subdomains

Hello all,

We just got a new DigitalOcean server that I want to install Virtualmin GPL on. Currently I have about 10+ sites on 3 servers that I want to move over to the new server eventually. The plan was to get everything set up on the new server (site code, databases, etc) before transferring the domain over. We want to minimize site downtime for the transfer.

Basically we have a frontend website that will be running on the main domain (let's just call it domain.com). We will have 9 or 10 other sites running on subdomans (site1.domain.com, site2.domain.com, etc).

I tried installing virtualmin by first using wget to download the install.sh file and running it that way, I noticed we needed perl, so I went about installing some common software that I would normally add to a new server (perl, php, mysql, apache, etc).

Finally I ran the install script again. I also (probably mistakenly) breezed past the FQDN question and I feel maybe this made things harder for me down the line. MySQL login couldn't be configured correctly and I can't login directly from the command line any more.

Questions:

  1. Do I need to install anything other than perl before running the install script? Can installing other software be causing problems with my installation? I'm getting the **Access denied for user 'root'@'localhost' (using password: YES) error**.
  2. Since we don't technically have a domain pointed to the new server, what would I choose as my FQDN? Is this something I can change later if I choose something temporary? Should this be the same as the main site's address (domain.com)
  3. We want our employees to have emails coming from the main site (employee@domain.com). Can/should this be configured after we transfer domains?

Currently we are resetting the server back to the base install so I can try again.

I am willing to answer any follow up questions and I apologize if I left anything out or my wording was vague.

Thanks in advance!

Tue, 06/14/2016 - 22:25
coderinthebox

"I tried installing virtualmin by first using wget to download the install.sh file and running it that way, I noticed we needed perl, so I went about installing some common software that I would normally add to a new server (perl, php, mysql, apache, etc)."

Since you install these manually (except perl), you caused conflicts on the server.

Visit me at coderinthebox.com

Wed, 06/15/2016 - 09:14 (Reply to #2)
elcubismo

I figured as much. I'm used to doing a bunch of default installations and did it without thinking. Our server has been reset, but I'm still not sure what to use regarding the fully qualified domain name. Will there be conflicts if we are planning on pointing domains to the server AFTER the site has been set up using a temporary fqdn?

Wed, 06/15/2016 - 18:17
elcubismo

For anyone who has similar questions, i just used "domain.com" (except the real domain name). I will follow up once we are ready to actually transfer the domain to see if that worked.

Topic locked