the problem was solved by disabling the apache php7.3 module .. I did not think it was enabled when reconfiguring
thanks to everyone
Yes, that module is not managed by current i-MSCP version. It will be managed in the next maintenance release. Anyway, if the module is there, that mean you have installed it somehow.
The problem is surely the man behind the keyboard...
Please provide us with more information such as the output of: perl /var/www/imscp/engine/imscp-rqst-mngr -dv
Regarding your first question, that currently not possible without make usage of an i-MSCP listener file. See https://github.com/i-MSCP/imsc…ed_override_default_rr.pl for an exemple. Without a listener file, there will be two different record resulting to the so-called Round Robin DNS technique (kind of load balancing).
Regarding your second question:
Normally, the parameters from the /etc/imscp/bind/bind.data file are filled by the i-MSCP installer. Best is to trigger a reconfiguration and just answer the related questions:
Then, when the installer ask you if you want to add slave DNS servers, you need to say yes, and in next dialog, provide the IP address(es) of your secondary DNS server(s). At the end, i-MSCP will regenerate the various DNS configuration files, taking the new parameters into account.
As explained several time already on our forums, there is no support for usage of different SSL certificates. Thus, you need to setup your mail client (SMTP, IMAP/POP servers) using always the same hostname, that is, your server hostname. Of course, you need enable SSL for the i-MSCP services (ftp, smtp, imap/pop) as well. This can be done using the LetsEncrypt plugin at the admin level.
For more details please search on our forums.
No support for such old and unsupported version.
This is the default exception message (for production). To see the real exception message, you need to turn on the debug mode in the /etc/imscp/imscp.conf file. Once the problem is solved, don't forget to turn it off again.
À ce que je sais si tu dois changer un composant du logiciel, tu dois relancer le setup, pas simplement la reconfiguration
La reconfiguration sert pour changer des logiciels dejà présents sur ton serveur
That's not true for composer packages. This is true only for server alternative such as courier vs dovecot, proftpd vs vsftpd
So you need to run:
The problem was fixed by the administrator of the relay server.
There are different rules which has to be changed.
Now it works without SASL authentication (the admin doesn't want to use this and our server is protected with ip rules).
So this mean that the relay' administrator chosen the first option