Error while install in both 22.04 and 24.04

There must be an issue with the underlying system, then. Add the following options to the install command to see more details:

--debug --interactive

 

But the instructions are about 127.0.1.1 for the server hostname and not 127.0.0.1. Be careful to not mix that up.

 

This file is wrong; see the tutorial. As I said, you mixed up 127.0.1.1 with 127.0.0.1. That's two completely different I addresses for different purposes and mixing them up will cause a malfunction of your server.

Correct would be:

Code:

The following is the hostname
127.0.0.1 localhost
127.0.1.1 hosting.24x7monitor.xyz hosting

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
158.220.98.52 vmi1508005.contaboserver.net vmi1508005

Assumed that hosting.24x7monitor.xyz is the server hostname which is returned when you run:

hostname -f

command.

 

The nameserver of a domain is the one that you have set at the domain registry. Do not create DNS records or a zone on a different server, like your ISPConfig server, if that server is not the authoritative DNS server of that domain.

 

https://www.howtoforge.com/ispconfig-email-account/

 

You seem to have done quite a few things wrong after installing ISPConfig. First, all recent ISPConfig systems use acme.sh and not certbot. Installing a conflicting LE client like certbot will give you all kinds of SSL cert issuing and renewal problems from now on. Then, never manually issue a cert for a website created in ISPConfig; this totally messes up the LE issuing system. Then, the LE cert of the system is for the hostname. It seems as if you also messed that up by issuing a cert manually. If you want to use the SSL cert of a website for the hostname as well, then you must follow this procedure: https://www.howtoforge.com/securing...server-with-a-valid-lets-encrypt-certificate/

That's the direct way to destroy the system's LE issuing and website management. Never issue a website certificate manually, let ISPConfig do that, and never install a second conflicting LE client.

 

The problem is this: if you install a hosting control panel like ISPConfig., CPanel, Plesk, or DirectAdmin, then the panel configures and manages all services that are part of the hosting setup like mail, web, SSL certs and DNS of your system to work as a well-configured and perfectly working unit. If you start to throw out pieces or replace them with other incompatible software or settings, then the system will start to fail. Hosting control panels are meant to manage your system, so if you install one, then you should use it to configure your system and avoid messing with the services manually. On the other hand, if you want to manage everything manually like issuing SSL certs, creating websites and mailboxes, then don't install a hosting control panel. Both ways are perfectly fine and depend on what the system shall be used for and the knowledge of the admin, but it's a decision that must be made before start setting things up, as you can't alter that easily at a later stage.

 

No. But ISPConfig has a remote API that you can use to integrate it into your website: https://git.ispconfig.org/ispconfig/ispconfig3/-/tree/develop/remoting_client?ref_type=heads