ehcp control panel doest work

Today when i want to open the control panel it didnt work, and redirect to a special site!
yesterday night i was redirecting a subdomain (test.example.com) to a domain, today my everysite was redirecting to that site and control panel didnt work,
now i am installing ehcp again and clear everything, but i found maybe i should give access to bvidinli to check it out.
is it possible that i do this if it happen again?

Yes,
I may have a look, if I have time in my daily business.
I will try to help as much as I can..

what you should check in these cases:

  • did you enter/changed some "apache template" wrongly ? if so: login to mysql in console, update domains set apachetemplate='' where domainname='yourdom.com'; insert into operations(op)values('syncdomains'); This should fix it..
  • did you change something in apache default file in /etc/apache2/sites-enabled , or 000-default file. ? restore it
  • may happen if you play with apachetemplate file... you need to restore it and repeat item 1.
  • Really I am not sure. everything stop working. i reinstall everything and this time i will write down everthing changes.

    May I ask, how did you update your ehcp ? which file did you use ?

    For anyone who uses a production server, I suggest:

  • Do NOT update to testing versions, or development versions. As of now (22.2.2010) the latest stable version is 0.29.12 (with some minor bugs) So, sometime, we post some url's to testing versions. do not update to those, if your server is production.
  • In any case, before upgrade, do backup your ehcp files, ehcp db. upgrading should not affect your web files, so, no need to backup them, in general.
  • I had the same problem, the apache configuration, even if i have 50 domains, was rewritten after a reboot with only one domain (dene.com), thing which happend before, this is second time.

    Never added this domain, having to do anything with it.
    It happens after updating EHCP version. EHCP update file apachehcp.conf should be empty, otherwise will happen this thing.

    Thanks,
    Razvan

    you may also start apache temporarily as follows:
    first, open a console and
    tail -f /var/log/apache2/error.log

    keep it and reopen a console,
    empty /var/www/vhosts/ehcp/apachehcp.conf
    > /var/www/vhosts/ehcp/apachehcp.conf
    /etc/init.d/apache2 restart

    That should restart apache. go to ehcp gui, and delete problematic domains or custom https's. otherwise, next time, those problematic domains would cause same problem.

    (You may also apply ehcp debugging for seeing problems: http://ehcp.net/?q=node/771)