BROKING ISPCONFIG

Why not Contact ISPConfig Business Support, https://www.ispconfig.org/support/ ?

 

@iniVan How do you manged to get access back to the panel?
Did you try a resync when you are logged in the panel?

 

I have the same problem but I wasn't able to get the panel working again, after php -q update.php and the reconfiguring of the services i still get the problem that I can't login into the panel. I tried to make a manual symlink to ipsconfig.vhost and then I will be able to get access to the site without an SSL Error but I only get the apache root website and if try to open index.php manual i will get an error not found

 

Is it possible to trigger the resync script from the commandline?

 

i tried a re-sync but it said it found nothing
Have you checked the ISPConfig database no some what a novice here !

 

if you're not completely sure what you're doing, best to do nothing.
do you have a backup of the ispconfig database?
if no, even more reason to do nothing. if you do something now that affects the dbispconfig database you wont get anything back.
we can't see the exact state of your system, your safest option, as mentioned, is to contact business support and let them look at it

 

lol i did so much but am awaiting a reply

 

ok guys used Bitvise ssh to have a look around the server /var/www still have its content an /var/vmail still in server

 

yes, but i don't think ispconfig will delete any of those on a resync anyway, i believe it needs to be specifically told to delete a mailbox or website to actually delete the files. if the mailbox, site or database isn't visible in ispconfig and you run a resync, it should just ignore them as externally configured entities.
with everything there, but ispconfig interface not showing any clients, sites etc, either you've lost/deleted/overwritten the original database, or it's looking at a new different ispconfig database.

depending on what you've done, especially regarding updating ispconfig itself, and your answers to it's request to backup the system first, there may or may not be an up-to-date backup of the database that can be restored, and which, itself, may need the ispconfig update re-applied to it.
this is why, at this point, you're much better off letting the official support take a look at your system. there are varying ways this can be resolved but it needs to be determined exactly how and where it's gone wrong to work out the best fix, and that appears to be best done directly now, rather than by questions and answers on here.

 

Hello,
I was unfortunately not precise. The Apache web server is not able to display the login page. During the update only the ispconfig.conf is written in sites-enabled and not the ispconfig.vhost. If I add the symlink manual I can call :8080 again but only the APACHE default page is displayed.

Thanks for the help

 

@jansurfingbad is it possible you installed ispconfig but chose not to install the interface?

exactly where did you point the symlink to? what what is the contents of that target file?

 

@nhybgtvfr
No I did an php -q update.php and said reconfigure services

I ponited the symlink from /etc/apache2/sites-avaible to /etc/apache/sites-enabled/000-ispconfig.vhost
The Target file was the old one from the existing working configuration which was online for over a year now

 

ok, guess the starting point is to check the obvious.

any apache errors when it's restarted?
is there a symlink for 000-default-ssl.conf in there? is the target for that the page you're seeing instead of the ispconfig login?
is https enabled for ispconfig itself? have you double checked the certificate is valid?
when you browse to port 8080, is the certificate it uses the correct one for the ispconfig interface?
does the symlink /var/www/ispconfig still exist? does it point to /usr/local/ispconfig/interface/web

what os are you on? did you try to upgrade the os? did you change the default php version? what is the default php version? what version of ispconfig did you have before? and now?
i'd guess changes to any of those are more likely to show lots of errors rather than the default apache page, but would still be helpful to know of any changes to those.

 

No errors, no there was not an 000-default-ssl.conf present, I also removed all other symlinks just to be sure.
https was enabled and the certificate was also used everything was fine exept that not the ISPconfig panel was show but the default apache site
I upgraded from debian 9 to 10. I had a multiphp system before with 7.0, 7.2 and 7.3 after the upgrade i also got 7.4 but something went wrong with some package after i tried the perfect server tutorial for debian 10 therefore I needed to purge apache and php and then i reinstalled the apache and php7.3 and php7.4 after this i didn't got any errors. PHP 7.3 was also working as default version and i was also able to parse an info.php site inside of the default apache directory.