I re-issued the certificate again and everything works just the same with the same problems.
I had downgraded to 2.2.29 and then nothing worked
re-upgraded to 2.2.30 and then used a sysdb.sql backup to restore the ispconfigdb
and now it goes to the apache2-default "it works" page
I am willing to pay for some help...I may lose a big 20,000 USD client if I cant get it up by tomorrow morning.
I couldnt even access the panel after the re-upgrade...changed the vhosts file with the old one and i could access the panel but all the domains still go to the apache2 default it works page
How could this happen just by downgrading!? I'm so stressed out i cant see straight.
All I care about is not losing my clients web data.
Does anybody have a clear tutorial on how to restore an ISPConfig backup?
BTW...I did issue the SSL cert commands before i downgraded and it still gave me the "Error - certificate too long" error with an eight character passphrase btw...
I couldnt access ISPConfig except from the internal network after the upgrade to 2.2.30
now it works when i access it directly through https://www.domain.com:81
when i changed the vhosts file in the /root/ispconfig, or httpd or whatever to an older one
but the websites still dont show....co-domains dont redirect....it's like ispconfig is not even functional.
I backed up ISPConfig sysdb.zip earlier...so i backed that up....I also have an export.csv but not sure if i have to import that or not because i cant find documentation.
I'm in danger of having to sell my office and go out of business if I cannot get ISPConfig restored by tonight!
Please help anybody!
Hell....I backed up the ispconfig master data, the web data, the database data....everything but the log data.....there's gotta be a way to restore it right?
Thanks to all care....I'll get u back....or pay u straight up front