Hi, I would like to install the ISPConfig console where users connect to a dedicated server so I can install/add servers in the pool but keep the same url for all users independent on which server their site is assigned too. We use other consoles this way (are migrating to ISPConfig) so our users are used to this. I bought the manual for ISP config, but the information is rather unclear in my opinion. I think I should do this by installing section '3.3.1.2 Install the Master Server". It basically refers to the page: "The Perfect Server - Debian 8.4 Jessie (Apache2, BIND, Dovecot, ISPConfig 3.1)". But I don't see the point to install BIND and Dovecot if you want to install the console only. I suppose it only needs Apache, Postfix (for sending mail), MariaDB and ISPConfig? Or is ISPConfig not designed to be used like this? Should it be installed on each server separate? Thank you.
Check ISPConfig documentation page as latest multi servers setup tutorial is also listed in it. https://www.ispconfig.org/documentation/
If you plan to use Debian, do use Debian 12 or 11. There are some steps for lastest version of Debian that are not compatible with the ones for Debian 8. New guide is here: https://www.howtoforge.com/perfect-server-debian-12-buster-apache-bind-dovecot-ispconfig-3-2/
That is not really an answer to my question. I did already check the documentation and bought the guide that is offered. These, except if I looked over it, all mentioned similar setups, also the multi-server guide, as mentioned in the opening post. Q1: can I install the console separate on a dedicated server only for the console and manage all other servers from that centralized location? Q2: if the answer on Q1 is Yes. What components are mandatory/required for this server, as also the Debian 12 guide mentions: Bind, Dovecot, ... which should strictly spoken not be necessary for serving the management console. Except if the concept/design of ISPConfig is not use a centralized management server to which the users connect, and thus install ISPConfig on each server separate.
Yes. This is the most common and recommended setup if you plan to have a larger installation. Basically, you need a web server installation. https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ so you use options like --no-mail and --no-dns but you should also use options like --no-ftp and --no-jailkit as these are used for web hosting, and as this node will not host sites, you can disable these features. After installation, take care to disable web server option in ISPConfig for this server under system > server services, as you do not want this node to be listed as available web server when creating new websites.
Thank you @till. It worked great. I used: Code: wget -O - https://get.ispconfig.org | sh -s -- --use-nginx --no-mail --no-dns --no-roundcube --no-pma --no-mailman --no-quota --no-jailkit --no-ftp --ssh-harden --unattended-upgrades Which installed a few extra's I rather not liked (awstats, acme,...), but fair enough. I also probably better specified the PHP version used by ISPConfig? Is there now an option to NOT install the console on the next (web) servers, or will it always install it?
Sighed. This is explained in details in latest multi server setup tutorial but wait, why bother reading and going through documentation simply because you can ask and be spoonfed? Good luck!
Yes, limiting to the default PHP version of the OS would be a god option too. That's covered here: https://www.howtoforge.com/tutorial/ispconfig-multiserver-setup-debian-ubuntu/ The code of the GUI will always be copied on the server as its a part of ISPConfig, but it will not be configured and enabled and depending on the services you run on the system, there will also be no web server at all.
I see. That way of installing the servers seems to give a bit more flexibility. So the magic to install the interface happens with these two sections: Code: Shall this server join an existing ISPConfig multiserver setup (y,n) [n]: MySQL master server hostname []: <-- panel.example.com MySQL master server port []: <-- Hit Enter MySQL master server root username [root]: <-- Hit Enter MySQL master server root password []: <-- the password you gave the external root user on the master server. MySQL master server database name [dbispconfig]: <-- Hit Enter Adding ISPConfig server record to database. And... Code: Install ISPConfig Web Interface (y,n) [n]: <-- Hit Enter
The first part you posted is not about installing the interface. It's about connecting a slave server to a master. Only the second part is about enabling or disabling the interface. The interface can be enabled on the master only, if you enable it on other nodes, then you would have to manually reconfigure it to connect to the master server as an interface may not be connected to a slave database.
