Environment ISPconfig 3.3.1p1 running on Rocky linux 10.1. Software installed and working via the support guys. Problem was the install used self generated SSL certs and put the DB on the wrong server - not the mysql DB server. Made change to use our SSL certs as the DB server was not happy with self generated SSL certs. Next was the move of the DB to the DB server and making the changes needed in the ispconfig related config files. Problem is that on the ispconfig login page, the graphic is not displayed and admin can not login: Then I ran ispc user set-password admin Result: Username does not exist Next step: check phpmyadmin I assume admin should have been in the client table - but the table is empty How do I get admin back?
The admin is not a client; you can find the admin user record in the sys_user table. The ISPConfig DB is typically on the server where you install ISPConfig, so the db is not on an external DB server. If this is an ISPConfig multiserver setup, then each node has its own MariaDB instance and ISPConfig database locally. If you get a self-signed SSL cert, then this just means that Let's Encrypt was not able to issue a certificate for your system, e.g. because the hostname doe snot exit or you blocked access to it so Let's Encrypt could not reach it.
Thanks - went back to the DB on the ISP server and am working the functions and features. The one SSL Cert per IP is a inconvenience as it will be some months before we get our own Class C network.
ISPConfig does not use or require an IP for each SSL cert. You can have as many SSL certs per IP in ISPConfig as you like. Best is to use the defaults, which is * in the IPv4 field of the website. This way, you can have as many sites on a single IP as your server can handle and each site can have its own SSL cert. The times that you needed an IP for an SSL cert are long gone, and that was not ISPConfig-specific anyway. About 15 years ago, you needed an IP for each SSL site because browsers did not support SNI widely at that time. Today, every browser supports SNI, so you can have as many sites per IP as you want. Typically, a hosting system has just a single IP today, no matter of the number of hosted sites.
