Comments on Updating ISPConfig 3.1 to ISPConfig 3.2

Is billing update needed before this ?

The Billing module works with 3.2, there are no extra steps for the update needed. If you encounter any issues in Billing module with ISPConfig 3.2, then contact me directly by email or ispconfig.org ticket system.

can we update servers with any older 3.1 version directly to 3.2 or do we need to update through any intervening versions first, ie, eg 3.13 -> 3.2  or 3.1.13 -> 3.1.14 -> 3.1.15 -> 3.1.15.p3

You can update directly to 3.2 from any 3.1 version.

7z was not working on centos 8

After installing  p7zip-plugins   it works.

v3.2 is out! Thank you for your great work!

I updated my test VM just a few hours ago. Now I tried it again on my production VM and got the following error.

PHP Parse error:  syntax error, unexpected '[' in  tmp/update_stable.sh.91aIasfVBa/ispconfig3_install/install/lib/installer_base.lib.php on line 251

Seems there is something wrong now. Did you change something in the last 3 hours or is the problem on my site?

Is the recommended update order for multi-server setups still secondary server first and primary server last?

I'll recommend updating master first now. You can set the master to maintenance mode to avoid that customers change settings until the slave nodes are updated.

Sorry for my comment yesterday. Wrong site for this kind of question and the problem was my fault. Forgot to switch System PHP back to v7.2 because of testing a old v5.3 with phpBrew.

Why are Ubuntu/Debian OS-es recommend over CentOS? What are the major caveats? Is this only because of RAR?

TROUBLE IN UPGRADING TO 3.2

Hi all,

I tried to update from 3.15 to 3.2 but probably I made some errors (I didn't install new package prior to upgrade). Result: after upgrade I can't access ISPConfig panel anymore (500 Internal Server Error).

I tried to revert back to previous ISPConfig version, by restoring the dbispconfig database and all /usr/local/ispconfig files to their previous version, but no luck: still 500 Internal Server Error. I didn't restore /etc files from backup, in order not to make more troubles, since I guess that all /etc files aren't strictly related to the ISPConfig version.

Question: how do I revert back to a functional ISPConfig, even on previous version?

Thank you very much.

Aldo

Under Debian Buster I had "The following formats can not be used because they are not installed on the webserver: 7z " in Backup tab "compression options".

I got rid of it by installing p7zip-full

What about pigz? Shouldn't we install that package too on Debian?

@Aldo: Please use the ISPConfig forum here at howtoforge to get support. A 500 error is caused by a failure in your PHP or apache/nginx setup, so a rollback of the update is probably the wrong solution. Look at the webserver error.log of your system to find out what is causing the issue and solve it. Besides that, a partial rollback without restoring etc can't work, that's why your issue is not solved by the partial restore you made.

@till sorry for posting in the wrong place, I was quite nervous for the things not going well. :-)

Just for information, the problem was solved in the meantime: despite PHP7 was installed, the package php7.0-cgi was missing, so I installed it and the panel came back. Now it appears working without issues.

Thanks a lot and keep up the good work.

Aldo

Hello,

after ugrade on Debian 9 autoresponder does not works. What can I do or how can I track why?

Thank you.

thank you so much.I had 500 errors after update from 3.1 to 3.2 and the comment helped me.

The one who said to install "php7.0-cgi".

Now it work

I had 500 internal error to ISPconfig panel on Debian 9 , installing php7.0-cgi fixed it 

Hello, everyone!First of all i want to say: Thank You Till for your work!

As I saw here, I secured ISPconfig by creating the ISPConfig Server site using its host name.

I didn't use a separate script to renew the certificate, but I checked the "Let's Encrypt SSL" box in ispconfig when I created the site.

Then I followed the steps in the "Using the Same Encrypt SSL Certificates for Other Major Services" section (from same tutorial) to use the same certificate for other services. Then I created the script that monitors the certificate renewal, as it appears in the section "[Creating an automatic renewal script for your ISPConfig Pem file (ispserver.pem)]"

From what I could understand from the steps I followed, I did nothing but use the certificate used for the FQDN site, creating links to them for each service I want SSL-ed and, using the icron service, I run the script "Le4ispc_pem.sh" which backs up and creates the ispserver.pem file and restarts the services to use the new certificate. Am I right?

If so, the question now is: do I need to disable icron or make other changes if I choose yes to the question "Create a new ISPConfig SSL certificate (yes, no)" or does ISPConfig do exactly the same thing as Icron?

Do I have an advantage if I choose yes? Or does ISPConfig do the same thing with my script when is runned by icron?Thank You

Hi,

goaccess package is available for CentOS 7 & 8 through EPEL.

Hi I get this error when trying to update to v3.2: Server's public ip (s) (80.245.233.33) not found in A / AAAA records for server.wolf6a.com: how do I fix this

Regards // Roffe

I am updating from Debian 10 (Nginx, BIND, Dovecot, ISPConfig 3.1

While this is the wrong place to answer (you should use the forums for that!), the problem seems to be that you don't have the reverse DNS set up correctly:

This is the forward DNS, configured correctly:

$ dig server.wolf6a.com

[...]

server.wolf6a.com. 7200 IN A 80.245.233.44

but the reverse DNS is not correct:

$ dig -x 80.245.233.44

[...]

44.233.245.80.in-addr.arpa. 600 IN PTR 44-233.soderhamn.com.

This is something that you cannot 'fix' locally; rather, you'll have to ask your upstream provider to do it on your behalf (I'm assuming you're using Binero or one of their resellers/partners).

The main reason for making sure that both the forward and the reverse DNS match is because, these days, almost no mail server will accept mail coming from a server with badly configured DNS — for the simple reason that that's how a majority of spammers/scammers configure their machines.

If you're not interested in using your own server for sending and receiving email (i.e. you are able to forward it upstream to your provider for delivery, and, conversely, you can use fetchmail to get email stored elsewhere into your local mailboxes), you might get away with a wrongly configured DNS setup. But that's certainly not recommended: a proper DNS configuration is a requirement for anyone wishing to (re)sell web hosting services (and if you aren't doing that, why would you be so interested in using ISPConfig? ????)

Bonjour

Suite à la Maj de isconfig 3.1 à suppérieur

j'ai ce message:

root@ns.........:~# PHP Warning:  Packets out of order. Expected 1 received 0. Packet size=30 in /tmp/update_runner.sh.a4PzS2UHHR/install/lib/mysql.lib.php on line 207

Avez-vous une idée d'ou cela peut venir.

Quand me connecte au serveur à l'interface en 8080 , j'ai une erreur 500

Merci