CentOS6 Upgrade

THIS ARE UPGRADE INSTRUCTIONS ONLY FOR CWP VERSION 0.9.8.1xx or lower

This is now critical issue as old version 0.9.8.1xx will completely expire soon and some of the important server services like backups and monitoring will stop working!

Procedure
===============
- Make sure that you are running CWP version 0.9.8.15x before proceedMySQL!!!
- Check your mysql version, you need to have mysql version 5.5 or higher (command: mysql --version)
- If your MySQL version is 5.1 or less than 5.5 then you need to upgrade MySQL by using MySQL upgrade script (instructions are bellow)
- Switch your server to Apache only mode in WebServers menu (you need to disable nginx and varnish, instructions are bellow )
- Download and Run CWP upgrade script (instructions are bellow)
- Download and Run Apache Upgrade script (instructions are bellow)

MySQL Upgrade (NOT required if you have MariaDB or MySQL 5.5 or newer)
- Before running any mysql upgrade please make sure you have backups of your databases, if you have cwp backups enabled then you should also have backups, but please check before proceeding.

Code: [Select]

cd /usr/local/src
wget http://dl1.centos-webpanel.com/files/el6/cwpupgrade/mysql.sh
sh mysql.sh
CWP Upgrade script
- Download and Run CWP upgrade script

Code: [Select]

cd /usr/local/src
wget http://dl1.centos-webpanel.com/files/el6/cwpupgrade/cwpsrv.sh
sh cwpsrv.sh
Apache Upgrade script
- Before running apache upgrade script, login into cwp.admin and check that you are running apache only under Apache Settings --> Select WebServers, don't forget to rebuild vhosts also.
- Download and Run Apache upgrade script

Code: [Select]

cd /usr/local/src
wget http://dl1.centos-webpanel.com/files/el6/cwpupgrade/apache.sh
sh apache.sh
If something goes wrong with you apache try also this command

Code: [Select]

yum reinstall cwp-httpd cwp-suphp

RESTORE
If something goes wrong you can restore your apache/cwpsrv with the command

Code: [Select]

cd /usr/local/src
sh cwpsrv.sh restore
sh apache.sh restore
*** Please note that it would be good that you have some system admin at your side before proceeding
If you stuck somewhere you can restore your current version and/or contact our support for assistance.
http://centos-webpanel.com/contact

On CWPpro version: 0.9.8.153 OS6. I hate to assume anything.

Running 10.1.21-MariaDB and can only assume there will be no issue upgrading since not MySQL 5?

So just run the CWP and Apache updates?

Thanks

Hello.

MySQL does NOT require upgrade if it higher 5.1!

CWP update was successfull, but the apache not.
I have this for every domains and subdomains:

Forbidden
You don't have permission to access / on this server.

ps: + a lot "Internal Server Error" errors

Hi,

Let us know what kind error in error.log do you have.
Also let us know what kind configuration did you have (apache+nginx etc, mod_security)?

CWP update was successfull, but the apache not.
I have this for every domains and subdomains:

Forbidden
You don't have permission to access / on this server.

ps: + a lot "Internal Server Error" errors

Hi,

Let us know what kind error in error.log do you have.
Also let us know what kind configuration did you have (apache+nginx etc, mod_security)?

CWP update was successfull, but the apache not.
I have this for every domains and subdomains:

Forbidden
You don't have permission to access / on this server.

ps: + a lot "Internal Server Error" errors

Before Update:
Application Version
    Apache version: Apache/2.2.27
    PHP version: 5.6.27 [PHP Switcher]
    MySQL version: 10.1.21-MariaDB
    FTP version: 1.0.36
System Info
   Distro Name: CentOS release 6.8 (Final)
CWP info
   CWP version: 0.9.8.153
   
After CWP update:   
CWP info
   CWP version: 0.9.8.188
   

Code: [Select]

Installed:
  cwp-httpd.x86_64 0:2.4.25-3                                                                     cwp-suphp.x86_64 0:0.7.2-2

Complete!
Stopping httpd:                                            [FAILED]
Starting httpd: AH00548: NameVirtualHost has no effect and will be removed in the next release /usr/local/apache/conf/sharedip.conf:1
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using s1.sowe.hu. Set the 'ServerName' directive globally to suppress this message
                                                           [  OK  ]
Apache has been upgraded


Code: [Select]

[Wed Mar 15 11:11:34 2017] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Mar 15 11:11:34 2017] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Wed Mar 15 11:11:34 2017] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Wed Mar 15 11:11:35 2017] [warn] Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Wed Mar 15 11:11:35 2017] [notice] Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Wed Mar 15 11:11:35 2017] [notice] caught SIGTERM, shutting down
[Wed Mar 15 11:11:46.001155 2017] [ssl:warn] [pid 6027:tid 140026756859648] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Mar 15 11:11:46.005490 2017] [mpm_event:notice] [pid 6027:tid 140026756859648] AH00489: Apache/2.4.25 (Unix) OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Wed Mar 15 11:11:46.005534 2017] [core:notice] [pid 6027:tid 140026756859648] AH00094: Command line: '/usr/local/apache/bin/httpd'
[Wed Mar 15 11:12:00.681838 2017] [authz_core:error] [pid 6031:tid 140026537047808] [client *.*.*.*:36317] AH01630: client denied by server configuration: /home/-username-/public_html/

edit: "/usr/local/apache/conf.d/vhosts-ssl-letsencrypt.conf" not loaded, httpd not listening on 443

This error

client denied by server configuration: /home/-username-/public_html/

looks like you are using deprecated Allow, Order directives in apache config or .htaccess.
You can try restore Apache and then rebuild via CWP.

This error

client denied by server configuration: /home/-username-/public_html/

looks like you are using deprecated Allow, Order directives in apache config or .htaccess.
You can try restore Apache and then rebuild via CWP.

Current running version:

Code: [Select]

Server version: Apache/2.4.25 (Unix)
Server built:   Mar  1 2017 14:22:27

Loaded Modules:
 core_module (static)
 so_module (static)
 http_module (static)
 mpm_event_module (static)
 authn_file_module (shared)
 authn_core_module (shared)
 authz_host_module (shared)
 authz_groupfile_module (shared)
 authz_user_module (shared)
 authz_core_module (shared)
 access_compat_module (shared)
 auth_basic_module (shared)
 reqtimeout_module (shared)
 ext_filter_module (shared)
 include_module (shared)
 filter_module (shared)
 deflate_module (shared)
 mime_module (shared)
 log_config_module (shared)
 env_module (shared)
 expires_module (shared)
 headers_module (shared)
 unique_id_module (shared)
 setenvif_module (shared)
 version_module (shared)
 proxy_module (shared)
 proxy_connect_module (shared)
 proxy_ftp_module (shared)
 proxy_http_module (shared)
 proxy_fcgi_module (shared)
 proxy_scgi_module (shared)
 proxy_ajp_module (shared)
 proxy_balancer_module (shared)
 slotmem_shm_module (shared)
 ssl_module (shared)
 unixd_module (shared)
 status_module (shared)
 autoindex_module (shared)
 asis_module (shared)
 suexec_module (shared)
 vhost_alias_module (shared)
 negotiation_module (shared)
 dir_module (shared)
 actions_module (shared)
 userdir_module (shared)
 alias_module (shared)
 rewrite_module (shared)
 suphp_module (shared)
This it the latest version as I see.

Now I try a vhost rebuild.

Edit: not working. I removed .htaccess but it didn't help.

still: client denied by server configuration: /home/-user-/public_html/

Apache rebuild started.

This error

client denied by server configuration: /home/-username-/public_html/

looks like you are using deprecated Allow, Order directives in apache config or .htaccess.
You can try restore Apache and then rebuild via CWP.

Current running version:

Code: [Select]

Server version: Apache/2.4.25 (Unix)
Server built:   Mar  1 2017 14:22:27

Loaded Modules:
 core_module (static)
 so_module (static)
 http_module (static)
 mpm_event_module (static)
 authn_file_module (shared)
 authn_core_module (shared)
 authz_host_module (shared)
 authz_groupfile_module (shared)
 authz_user_module (shared)
 authz_core_module (shared)
 access_compat_module (shared)
 auth_basic_module (shared)
 reqtimeout_module (shared)
 ext_filter_module (shared)
 include_module (shared)
 filter_module (shared)
 deflate_module (shared)
 mime_module (shared)
 log_config_module (shared)
 env_module (shared)
 expires_module (shared)
 headers_module (shared)
 unique_id_module (shared)
 setenvif_module (shared)
 version_module (shared)
 proxy_module (shared)
 proxy_connect_module (shared)
 proxy_ftp_module (shared)
 proxy_http_module (shared)
 proxy_fcgi_module (shared)
 proxy_scgi_module (shared)
 proxy_ajp_module (shared)
 proxy_balancer_module (shared)
 slotmem_shm_module (shared)
 ssl_module (shared)
 unixd_module (shared)
 status_module (shared)
 autoindex_module (shared)
 asis_module (shared)
 suexec_module (shared)
 vhost_alias_module (shared)
 negotiation_module (shared)
 dir_module (shared)
 actions_module (shared)
 userdir_module (shared)
 alias_module (shared)
 rewrite_module (shared)
 suphp_module (shared)
This it the latest version as I see.

Now I try a vhost rebuild.

Edit: not working. I removed .htaccess but it didn't help.

still: client denied by server configuration: /home/-user-/public_html/

Apache rebuild started.

u see a new and better speed, cache etc? in ur server? load website?

After an Apacha Rebuild now it's working

Before:
Application Version
    Apache version: Apache/2.2.27
    PHP version: 5.6.27 [PHP Switcher]
    MySQL version: 10.1.21-MariaDB
    FTP version: 1.0.36

After:
Application Version
    Apache version: Apache/2.4.25
    PHP version: 5.6.27 [PHP Switcher]
    MySQL version: 10.1.21-MariaDB
    FTP version: 1.0.36

Now I have to use PHP Swticher to switch to the latest php7?

@robbyq: the CWP Control panel is faster, the web test is in progress

Next problem with webmail:

Code: [Select]

DATABASE ERROR: CONNECTION FAILED!
Unable to connect to the database!
Please contact your server-administrator.

Now I have to use PHP Swticher to switch to the latest php7?

No, it does not requires. You can use if you want.

Code: [Select]

DATABASE ERROR: CONNECTION FAILED!
Unable to connect to the database!
Please contact your server-administrator.

Hmmm, never seen it before after update.
Check if config

Code: [Select]

/usr/local/cwpsrv/var/services/roundcube/config/config.inc.phphas correct rouncube login and password.

Now I have to use PHP Swticher to switch to the latest php7?

No, it does not requires. You can use if you want.

Code: [Select]

DATABASE ERROR: CONNECTION FAILED!
Unable to connect to the database!
Please contact your server-administrator.

Hmmm, never seen it before after update.
Check if config

Code: [Select]

/usr/local/cwpsrv/var/services/roundcube/config/config.inc.phphas correct rouncube login and password.

It's interesting because i have a proxy to forward https://cwp.url to 2030 , so I can use it behind a limited network.
And If I use it with https://cwp.url/roundcube its working. If i use a standard url.url/webmail (like before) I got this error message.
Any idea why?

It's interesting because i have a proxy to forward https://cwp.url to 2030 , so I can use it behind a limited network.
And If I use it with https://cwp.url/roundcube its working. If i use a standard url.url/webmail (like before) I got this error message.
Any idea why?

Try to use http://url.url:2030/webmail

Try to use http://url.url:2030/webmail

It's working. The question is, why now we lost the default url/webmail access, and why this is not communicated out?
Becuase now we using again a non-standart port. So, if the firewall/proxy is blocking every port and only 80/443 available, now the users can't use the webmail.
I will solve this in vhosts i think, but the questions are open

It's working. The question is, why now we lost the default url/webmail access, and why this is not communicated out?
Becuase now we using again a non-standart port. So, if the firewall/proxy is blocking every port and only 80/443 available, now the users can't use the webmail.
I will solve this in vhosts i think, but the questions are open

We'll think about it. But at the time should be used port 2030.
Thanks.