The biggest problems caused in this case was ISPConfig once installed, it will die by itself after few minutes, then must reboot the server, and it dies again few minutes later, then reboot the server again and so on, each process in between takes from few minutes to hours to reach the login page. Successfully installed ISPConfig 3 with Ubuntu 20.04 in AWS Lightsail Visit the login page gets ERR_CONNECTION_TIMED_OUT or ERR_TIMED_OUT Reboot the server and logged in with server IP, change admin password, add firewall Few minutes later, ISPConfig dies out itself Reboot again and takes long time to reach the server login page, sometime can reach and logged in, sometimes no, and sometimes logged in but the page keeps loading with no header menu Installation Guide Followed howtoforge dot com - ispconfig-autoinstall-debian-ubuntu - Unsuccess (Unable to use links as new user here) With add '--no-quota' to the installer - Success Anyone can help will be much appreciated
Most likely your server is too small. How much RAM does it has? A system with all services installed must have 2GB RAM or more. This just means you are using a system that does not has support for traditional Linux quota.
Thanks for your reply Till. Servers I have tried to install with are as follows and both of the installs are the same results unfortunately. I have searched everywhere and tried every possible to install the ISPConfig with both the plans below for 70 times from 29/09/2022 to 30/10/2022. 2 GB 1 vCPUs 40 GB SSD 4 GB 2 vCPUs 60 GB SSD How do I get the quota supported in this case e.g. from the Lightsail or the Ubuntu?
This just shows that your issue is not directly related to the installation or auto installer. Especially that it works at the beginning means that there is some kind of issue with the virtualization system itself which then fails and locks up. The best option to diagnose this is that you monitor it tightly right after reboot to find out why it locks up e.g. if it runs out of memory. Connect to it with a console and e.g. use the top command and maybe connect with a second console and monitor io with iotop and disk space with df command. A wrong partition scheme might also cause issues, e.g. if you decided to use several small partitions instead of a big one and one of them is full while the other partitions have plenty of space. The quota issue is not related to Ubuntu or ISPConfig, quota on Ubuntu when run on a system that is capable of providing quota works perfectly, it's a problem with the virtualization or OS image that you have chosen. Most like amazon tried to save space by using a limited Linux kernel. Try installing a kernel that supports Linux filesystem quota before you install ISPConfig. Another possibility is that amazon uses an incompatible filesystem, Ubuntu by default uses an ext file system and that's what the auto-installer expects, if you have chosen to use a different file system (which may support file system quota as well as xfs), then you can try to configure quota after installing ISPConfig manully.
The ISPConfig dies out below 2% of Sustainable zone after every reboot, not every reboot can reach the login page and/or logged in. The Sustainable zone reaches 95% to 100% and above when the server is rebooted. As the quota is not configured during the ISPConfig installation, can you please provide a step by step to set it up? RE: Amazon Lightsail use ETS file system: Amazon EFS Amazon EFS is a simple, serverless, set-and-forget, elastic file system that makes it easy to set up, scale, and cost-optimize file storage in the AWS Cloud. In this guide, you create and connect to an EFS file system from Lightsail instances using VPC peering.
ISPConfig is not a daemon, so it is not consuming any memory permanently. Basically, you have a virtual machine that is not capable of running standard software like apache, MySQL, postfix, dovecot and Bind. So you must try to find out why the system you have chosen is not capable of running such standard applications. As mentioned earlier, most likely the VM or container you use has too limited resources and you have to try to find out which resource is too limited. I doubt that this filesystem supports Linux quota. You can use ISPConfig without quota, you just can not restrict the size of a website. If you need quota, get a real virtual server (and not a container without quota support) that many providers and data centers offer or a root server. ISPConfig and quota work flawlessly on any standard Ubuntu and Debian system, you are using a very limited and crippled system, probably a container and not even a VM, and that's why standard Linux services might fail or are unavailable.
i would suggest not using lightsail and just use standard ec2 instances instead. i know from experience that they work without problems ( as long as you add the kernel packages to allow quotas if using them ) especially as aws themselves consider ec2 instances to be an upgrade on lightsail instances.
