These are my notes about the recently updated "Perfect" install instructions for Ubuntu v20. I hope this helps. I can expand if required. The beta doc is really good. Thanks. (I know it's mostly copy/paste from the prior doc but that was good too. ) Doc does not include notes for (optional) Metronome XMPP Server. Ref A lot of people have been confused about /etc/hosts over the years. I'm surprised the doc is not clear on this. There is a link from the Perfect doc to a page about installing a minimal Ubuntu 20.04 server. That page includes this for /etc/hosts: But to ensure that `hostname -fqdn` returns the recommended FQDN, this is required: It's not made clear in the doc (and forum posts on the topic) that the FQDN must be a real A-name, and that DNS must resolve to the server. If you cannot type (per above) server1.example.com and access the site, you won't be able to login. The cert is generated from this FQDN too, so if the server FQDN doesn't match the DNS FQDN, you're going to get an invalid cert warning. I rebooted after the first few apt-get install operations, just because... While we should not need to do this and Linux fans would take this as an insult ("what? like Windows!?") the fact is that sometimes a restart is required, and the few seconds delay doesn't hurt. Only download the ISPConfig installer to /tmp when you need it - after a reboot it might get deleted. Or, just put it somewhere else. About "/etc/apt/sources.list", there is a warning about it being a generated file, and "do not edit". So perhaps other instructions should be provided. That said, on my systems where I did a fresh Ubuntu install before ISPConfig (three so far) no change was required anyway. Trivial typo: "shown in read" should be "shown in red". About "/etc/fstab", the instruction to edit this file comes before "To enable quota, run these commands". The command to nano that file should follow that line. Still on fstab, every system will look very different. I would be very concerned about someone blindly edting in the quota detail. Or rather, the rest of the instructions are amazingly easy to follow. Someone who follows the fstab can really mess up their system, compared to all of the other copy/paste-ready commands that are flawless. I think that area needs some comments or links for more info. Because of this issue I did not enable quota (I don't need it anyway). About certs: From prior experience I know that when we enter the detail for certs, hitting the backspace key inserts a ^h rather than removing the last character. So when I type this info, I am VERY careful to get it exactly right. I think there should be a note in there about this. Would "stty erase ^h" or similar help? For anyone who uses an external firewall or security policies, ports need to be opened to access the ISPConfig installation. Please correct or confirm: 8080 : Should be restricted to IP addresses/block owned by admins 25 : Global inbound (0.0.0.0/0) 465+587 as desired by the site Anything else? About the command "openssl req -x509 -nodes -days 7300" for Pure FTPd : I used 360 days. Do recent decisions about limiting cert life apply here? I believe these are only self-signed anyway. So it shouldn't make a difference. Still about that command which includes "rsa:2048" : The certs generated from ISPConfig are 4096 bit. I think this openssl command should be modified for 4k as well. Once the site is up with the self-signed cert. Is there a designated place with instructions about how to generate a proper cert for the ISPConfig site itself? I'm going to familiarize with this environment (named ns1.mydomain.tld) for a couple days and then install a secondary server. Is there anything different in v3.2 about multiserver configurations or setting up our own DNS (as ns2.mydomain.tld) ? Thanks!