Need advice - Multi server ISPConfig 3.2 installation - configuration

Discussion in 'Installation/Configuration' started by raziel00, Jan 2, 2021.

  1. raziel00

    raziel00 New Member

    Hi,
    I want to build a small infrastructure with ISPConfig. I have never used the product before, but saw it work, so some parts are new to me.
    In a test lab, i have installed 2 servers ispconfig1 and ispconfig2 using the following guide, and I have successfully configure so that ispconfig2 is a slave and ispconfig1 is master.
    Tutorial: The perfect server ubuntu 20 apache php mariadb pureftpd bind postfix dovecot ispconfig3.2 beta
    But instead of the beta version i used the latest official version 3.2.

    This is the setup I have.
    ISP1 (ispconfig1 . comp. com) : web, db, ftp, dns
    ISP2 (ispconfig2 . comp . com) : mail

    I was able to setup a test website and a test mailbox using the same domain name, lets say tester.com.
    Here is my situation:
    if I go on www. tester. com it opens the website.
    if I go on www. tester.com/webmail -> it doesnt exist
    if I go on tester. com/webmail -> it doesnt exist
    if I go on ispconfig2. comp. com/webmail -> it works and I'm able to login in test mailbox.

    How can i configure that for every client i create a new website based on there domain i can have the following:

    newclient. com:
    www. newclient. com (hosted on ispconfig1. comp. com)
    newclient.com and www. newclient. com /webmail (hosted on ispconfig2. comp. com)

    Thank you in advance for the help.
    Raziel00
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    This is not possible as the DNS records for those domains point to ispconfig1. You could set up a redirect though.
    - Create DNS record for webmail.example.com that points to your webmail server
    - Create site webmail.example.com, disable auto subdomainamd enable Let's Encrypt (all on the webmail server)
    - Under the tab "Options", add this to Apache directives:
    Code:
    DocumentRoot "/var/lib/roundcube"
    Alias "/stats" "{DOCROOT}/stats"
    On the webserver, create a config file for apache:
    Code:
    nano /etc/apache2/conf-available/roundcube-redir.conf
    and put this in there:
    Code:
    Redirect /webmail https://webmail.example.com
    Then enable the config:
    Code:
    a2enconf roundcube-redir
    Now, if you go to clientdomain.com/webmail, you will be redirected to webmail.example.com (with a 302 redirect).
    Replace example.com with your own domain :)
     
  3. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    I think anydomain.tld/webmail could work fine, even without the suggested redirect above, whether in apache2 or nginx web server, as step 16 of apache2 PST or step 15 of nginx PST each covers the same, provided it is a single server setup.

    For a multi server setup, what is described above is the way to go.
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Not if webmail is on different server ;)
     
  5. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Yes. That is what I said in your quote. ;)
     
  6. raziel00

    raziel00 New Member

    Hi Th0m,
    Thanks for your reply. Sorry took time to answer. Your solution works and I would like to know if it would be possible to do the following.
    Let's say I'm a hosting company.
    With your solution this is what we are doing:
    www. client. com/webmail (ispconfig1) goes to webmail. hostingcomp. com (ispconfig2)

    Now do you think we can something like this:
    www. client. com/webmail (ispconfig1) goes to webmail. client. com (ispconfig2)
    Keep in mind that I will have at least 12 domain names when I start using this infrastructure.

    Thanks in advance.
     
  7. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Yes, you could do this, but it will be quite some work to manage this as you have to create a DNS record for this subdomain for every domain, create the web / aliasdomain, and generate a SSL cert. For 12 domains this is doable but in the future it will become more and more work - both in creating and maintaining it. So I would not do it.
     
    ahrasis likes this.
  8. raziel00

    raziel00 New Member

    Hi,
    Thanks for the input. I'm starting to agree with you. :)

    Thanks.
    Raziel00
     
    Th0m likes this.

Share This Page