Hello, On an up-to-date Debian 12. Updated IspConfig ISPConfig 3.3.0p2 This installation was migrated a week ago using the IspConfig script. I've been using Debian and IspConfig for years; I'm no beginner. I was surprised this morning to discover that one of my VHOSTs had disappeared from the web interface (and the database) of IspConfig. - The site is still online. - Apache2 configuration files are present in /etc/apache2/sites-available/ and /etc/apache2/sites-enabled/ - IspConfig configuration in /etc/fstab and /var/www is still present. I did delete two unnecessary VHOSTs this morning, but I'm sure I didn't delete the VHOST I'm looking for... These VHOSTs have been properly deleted from the database, the Apache2 configuration, and the /var/www directory. I tried resynchronizing the sites with the Ispconfig tool, without success. I'm no better with ispconfig_update.sh --force. My question: If I recreate an identical vhost in IspConfig, won't that create a conflict with the files in /etc/apache2/sites-*, /var/www, and /etc/fstab, the UIDs/GIDs, etc. ? Wouldn't the simplest thing be to recreate the vhost directly in dbispconfig since the files seem intact on disk? I'm having trouble crashing Apache 2, so I'd prefer your opinion before doing anything. The VHOST is simply a reverse proxy, so there's no risk of data loss. Thank you for reading and sorry for my english from a transator...
You can use the datalog viewer in the ISPConfig monitor module to determine when this vhost was deleted and by whom. Does this mean the vhost you do not find in ISPConfig still exists in the system config files? Have you checked the ISPConfig database with phpMyAdmin to confirm that the vhost no longer exists in the web_domain table in ISPConfig? Perhaps you have set a filter in the vhost list that excludes it from being visible in the GUI.
Hi Till, Thanks for you answer. Nothing in Logs (Cron or Ispconfig) about my VHOST today or yesterday. Yes all files are presents and the Vhost works fine. VHOST is not present in Table web_domain in database dbispconfig No filter in the GUI.
These are the two VHOSTs I was talking about that have been properly deleted. There's no trace (or at least no deletion action) of the missing site in the GUI. Edit: The "funny" thing is that I can't find any trace of the VHOST being created either...
If it was created more than 30 days ago, then it's not in the datalog anymore. Not sure how this vhost disappeared from the database, if it would have been deleted from within ISPConfig, then you must find it in the datalog, and also the config files and folders would have been removed.
Hi till, I understand your surprise, which is the same as mine. This is the first time I've encountered this kind of problem with IspConfig, and I've been using it for years. The site was created yesterday. It wasn't intentionally or accidentally deleted from IspConfig GUI. The fact remains that it's no longer there, even though all the configuration files are present on disk. My questions remain the same: If I recreate an identical vhost in IspConfig, won't that create a conflict with the files in /etc/apache2/sites-*, /var/www, and /etc/fstab, the UIDs/GIDs, etc. ? Wouldn't the simplest thing be to recreate the vhost directly in dbispconfig since the files seem intact on disk? Thank you for your time.
This would probably be the best option. But you must ensure that it has the same domwin_if than the original one. The domain ID is the number of the webXXX username.
Hello till, Thanks for the confirmation, that's what I thought. I'll take my time (the vhost is online, there's no rush). One last confirmation: Is it advisable to resynchronize websites with the Resync Tool after inserting the line in dbispconfig?
Hi Till, For information I inserted the missing line without problems. I changed some VHOST settings in IspConfig GUI, and the change was successfully saved in DB and the file in /etc/apache2/sites-available/100-xxx was modified accordingly. I think (And I hope...) the problem is fixed.
i assume you migrated all websites from the source server across. is it possible the migrate script failed adding the website to the new server's db properly but rsynced the whole contents of /var/www/ and /etc/apache2/sites-enabled? maybe the migration script generated a warning/error message at the time that just got missed not sure if the migrate script would do that or if it rsyncs each website individually, but if it does it all in one rsync it could explain the site folders / config all being there but no entry in the dbispconfig db...
The migration scripts sync sites individually, and the sync with rsync covers only the content; you won't have a vhost file then. So that the migration script did not add it to the DB is unlikely as you would not had a vhost file or working vhost then (no webID user and clientID group, no vhost file, no vhost symlink etc.).
Hi, No, the vhost wasn't migrated but created post-migration. One thing is possible now (I'm no longer certain): due to a database problem, I had to rerun the migration script (which works perfectly, by the way, thank you). If I created the VHOST before the second migration, it would simply have been overwritten by the import of an older version of dbispconfig. This is obviously the most plausible version because I don't see how the ever-reliable IspConfig could have deleted a line in dbispconfig on its own...
the migration shouldn't discard any clients / sites that already exist on the new server. depending on choices made during the migration, if the same client already exists it might create a new client appending a number to the client name, or it will add the site to the existing client account. not sure what it would do if the client had a domain / website limit set in client limits that's already maxed though.
The Migration tool will not remove anything on the target system, even if client limits get reached. I suppose we won't be able to determine what caused this or reproduce it.
