Migrating sites from ISPconfig v3.1 to v3.3 I appear to be running into an issue with database users. Using the migration tool, I found that the database users weren't migrated when the databases were. Not too many sites, need to do a little manual work anyway, moving from Apache to Nginx, so I figured I would just manually create the users and found that when copying over the passwords, the new requirements are stricter. I'm not sure if this is why the users weren't created, but sure I started setting stronger passwords. Only to find that the "c[CLIENTID]" string wasn't generated for the first account. I went to check out the global settings and appended the default string with a '_' as per the old servers. Second account generated fine and added to the database. But now I'm coming to the third user, I can't seem to add it to the database. The drop down list remains empty. So I'm left wondering if ISPconfig no longer likes client0 for database users or if there's something else going on here that's tripping the UI up when trying to add a user to a database. c1 databases manage to pull up c1 users just fine.
Never mind, found the issue: The website the database is tied to must be working (valid SSL, which requires valid DNS entries for the site's domain) I thought I could be clever and get the database + user configured before changing DNS to get a valid certificate on the migrated site, but alas, no. Or maybe I should try migration mode, but that might bite me in the proverbial in other ways.
that's the point with certificates : they need to be up to date to work. maybe an idea for ispconfig can be to enable external dns challenge ?
Database users and databases are not tied to SSL of the website. It neither matters if your site has SSL nor your server. When a user does not show up for a database, then the owner of the website and the owner of the database differ. And having the admin as the owner of a site or database is fully supported. What likely fixed your issue was not SSL, it was that you changed something in the site to make the owner of the database user and the site match. That you also changed something SSL-related did not contribute to the fix. There is no issue with SSL certs; the MigrationTool also copies these over during migration as long as you do not use a different LE client. So having DNS-validated SSL certs won't change anything here; the above issue is not SSL-related.
