ISPConfig 2.2.11 released

Thanks again ISPconfig team!

I will update my servers later today!

 

Thanks again for your work Till!
updated with no problems.

 

Another flawless upgrade. Thanks!

 

port 81 problems

I just now upgraded from ISPConfig 2.2.10 to ISPConfig 2.2.11. All of my webs and databases I created with ispconfig are working. Nothing is working on port 81 anymore. I tried rebooting. I get Internet Explorer cannot display the webpage.
examples:
https://host.mydomain.com:81/
https://host.mydomain.com:81/phpmydamin/
https://host.mydomain.com:81/phppgadmin/

?

 

Give https://your_server_ip:81 also a try.

 

output

I tried posting my netstat -tap output to the forum but it wont let me. VBulletin says:

The following errors occurred when this message was submitted:
You have included 5 images in your message. You are limited to using 4 images so please go back and correct the problem and then continue again.

Images include use of smilies, the vB code tag and HTML <img> tags. The use of these is all subject to them being enabled by the administrator.

I tried accessing my control panel using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9 and it says

could not establish an encrypted connection because certificate presented by 'edited here' is invalid or corrupted. Error code: -8182

I got this also when I installed ISPConfig 2.2.10 on a fresh install of the perfect setup fedora core 6. I followed these instructions. and then it worked.

[code]openssl genrsa -des3 -passout pass:yourpassword -out /root/ispconfig/httpd/conf/ssl.key/server.key2 1024
openssl req -new -passin pass:yourpassword -passout pass:yourpassword -key /root/ispconfig/httpd/conf/ssl.key/server.key2 -out /root/ispconfig/httpd/conf/ssl.csr/server.csr -days 365
openssl req -x509 -passin pass:yourpassword -passout pass:yourpassword -key /root/ispconfig/httpd/conf/ssl.key/server.key2 -in /root/ispconfig/httpd/conf/ssl.csr/server.csr -out /root/ispconfig/httpd/conf/ssl.crt/server.crt -days 365
openssl rsa -passin pass:yourpassword -in /root/ispconfig/httpd/conf/ssl.key/server.key2 -out /root/ispconfig/httpd/conf/ssl.key/server.key
chmod 400 /root/ispconfig/httpd/conf/ssl.key/server.key[/code]

Now when I upgraded I have followed those same certificate instructions and it works again.

Why does it do this when I first installed ISPConfig and when I just applied the update?

 

./setup and ssl certificates

It seems that the certificates created during the setup of ispconfig wont work but after ispconfig is installed and i manually recreate the certificates they work.

The only difference I saw was when I did them manually it asked for a password which I hit enter when asked. I hope this was right.

 

ssl certificate

I used the exact same information with all 8 certificates. During my initial ispconfig install, it created 2 certificates that were invalid or corrupted. I then manually recreated them using the steps above, and then everything on the secure (https) port 81 became available immediately. I then upgraded to the new ispconfig and then nothing on the https port 81 worked again because of a corrupt or invalid certificate. I then manually recreated these 2 certificates again using the steps above and then everything on my https:81 worked again.

So my question about this is again, Why does it do this when I update or install ISPConfig?

 

Had the same problem with Firefox but here with the problem, that I told FF to accept that self signed certificate with that URL... after the ugprade the certificate itself changed which results in a conflict.
So to get FF working again with the admininterface was to remove the certificate that I FF remembered for the ISPCOnfig Admin Interface...

hth

 

i've got a working 2.2.9
is it ok to use 2.2.11 to update my installation or should i update from 2.2.9 to 2.2.10 and then from 2.2.10 to 2.2.11?

 

same problem with my certi`s in firefox. if i remove the old certis from my firefox, all works fine!!!

the firefox tell me, that i use a new certi for this site with the same "certi-seriennummer" and i shoult renew/buy a new certi

 

clamav problem, folders in /tmp

Hi there,

I just experienced the problem you mentioned in this thread (http://www.howtoforge.com/forums/showthread.php?t=11100&page=2) happening on my live server. For some odd reason there are clamav folders in my /tmp directory.
The actual problem is that they belong to some ISPConfig users whose quota now exceeded. This seemingly made the server unable to save mails for them. At least people writing them mails get back a very unhandy auto-generated postfix error mail.

I just increased their quota but this of course cannot be a long time solution.

To me it looks like the directories contain the virus databases downloaded by freshclam. But how come they still exist?
Does anybody know whether they have a problem with their servers?

By the way: Where are the files like main.ndb, main.db, etc. placed in ISPConfig? I could find them via "find / -name main.db"

Thanks for your help.

Greets,
Alex

 

Hi Till,

the reason why I posted here is that I already HAVE installed 2.2.11!!!

I have to mention again: I don't think this is a ISPConfig Bug because I experience similar problems with clamav/ freshclam on my Strato server with Serveradmin24 after I upgraded to 0.90.1
The only problem is that their support in my opinion sucks!

Greets,
Alex