This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
16
Updates / Re: Upgrade php 5.6 to version 5.6.29
« on: January 07, 2017, 06:35:55 AM »
Maybe I wasn't clear enough and misled you. This version is installed as alternative version via the switcher, not as default php version.
17
Updates / Re: Upgrade php 5.6 to version 5.6.29
« on: January 06, 2017, 04:10:15 PM »what cwp version you're using ?
CWP version: 0.9.8.132 with auto updates enabled
18
Updates / Re: Upgrade php 5.6 to version 5.6.29
« on: January 05, 2017, 07:10:31 AM »php versions are regularly updated in cwp
What is regularly because the version in the switcher is 5.6.14 ?
19
Updates / Upgrade php 5.6 to version 5.6.29
« on: January 05, 2017, 06:40:51 AM »
CWP use php 5.6.16 which is more than 1 year old - released on 01 Oct 2015. Update is quite easy. Edit file /usr/local/src/php-5.6.sh like this :
After that install new php version with:
Code: [Select]
#version=5.6.14
version=5.6.29
phpsource="http://de1.php.net/distributions/php-$version.tar.bz2"
#phpsource="http://dl1.centos-webpanel.com/files/php/selector/php-$version.tar.bz2"
I used DE mirror because my server is located in Germany, but feel free to use any other near to you.After that install new php version with:
Code: [Select]
sh /usr/local/src/php-5.6.sh
I highly suggest CWP team to update php version - there is a lot CVE fixes between 5.6.14 and 5.6.29.
20
Scripts / basic php setup
« on: September 03, 2016, 08:42:48 AM »
Because I'm too lazy to edit all my php ini files i wrote basic stupid script to edit them instead of me The script is with hard coded values because I did it for my environment but is pretty simple to make changes for yours.
Any edits/updates are welcome
p.s Please dont comment the values of the ini files, because this is not the purpose of this thread
Code: [Select]
#!/bin/bash
INI_FILES="$(ls /opt/alt/php*/usr/php/php.ini) /usr/local/php/php.ini"
#setup some basic variables
for ini in $INI_FILES
do
#make backup just in case :)
[[ -f $ini ]] || cp $ini $ini.orig
sed -i.bak "/upload_max_filesize/c\upload_max_filesize = 16M" $ini
sed -i "/post_max_size/c\post_max_size = 32M" $ini
sed -i "/memory_limit/c\memory_limit = 256M" $ini
grep -q ^error_log $ini && sed -i "/^error_log/c\error_log = error_log" $ini || echo "error_log = error_log" >> $ini
grep -q ^date.timezone $ini && sed -i "/^date.timezone/c\date.timezone = Europe\/Sofia" $ini || sed -i "/;date.timezone/c\date.timezone = Europe\/Sofia" $ini
grep "upload_max_filesize\|post_max_size\|memory_limit\|error_log" $ini
done
service httpd restart
Any edits/updates are welcome
p.s Please dont comment the values of the ini files, because this is not the purpose of this thread
21
SSL / Re: Only 1 site it works with SSL rest of them redirect
« on: August 03, 2016, 08:27:04 PM »
Also you can check out this thread.
22
Information / Re: Transfering CWP from one server to another
« on: August 02, 2016, 06:31:44 PM »It is possible, I've done it.Can you send me all command which i should execute ?
There were elements that didn't get transferred though. For example I had inkscape installed on the old server, and it didn't install correctly on the new one.
But what you'll want to do is simply two things.
1) rSync from old to new server everything but a couple of directories. You will need /var/vmail/, /home for sure
2) MYSQLDUMP ALL databases, then import them on the new server. (http://stackoverflow.com/questions/9497869/export-and-import-all-mysql-databases-at-one-time)
Administrator here on forums can explain better.
Thanks
Will be a lot easier to do rsync / with exclude /proc /dev /sys.
23
SSL / Re: How to install multiple SSL certificates on shared IP
« on: July 26, 2016, 07:09:58 PM »
To enable SNI you have to do little more works
1. Add to apache config
This setup is tested with 1 certificate from certificate authority and 1 lets encrypt. Both certificates work fine.
Files for ssl vhosts are located (in my case):
1. Add to apache config
Code: [Select]
NameVirtualHost *:443
2. Change every ssl VirtualHost from Code: [Select]
<VirtualHost IP Address:443>
toCode: [Select]
<VirtualHost *:443>
3.Restart apacheThis setup is tested with 1 certificate from certificate authority and 1 lets encrypt. Both certificates work fine.
Files for ssl vhosts are located (in my case):
Code: [Select]
/usr/local/apache/conf.d/vhosts-ssl.conf
/usr/local/apache/conf.d/vhosts-ssl-letsencrypt.conf
24
Addons / Re: open source billing system like WHMCS
« on: July 15, 2016, 04:05:22 AM »
WHMCS is far away from open source
25
How to / Re: Fastest Way of Enabling Mod_PageSpeed
« on: June 10, 2016, 04:24:13 PM »
Download url doesn’t work
26
How to / Re: Process Limit
« on: May 23, 2016, 07:08:43 PM »Hello.
You can change your /etc/security/limits.conf and set "username soft nproc unlimited" or delete line with the username.
If csf is enabled also check PT_USERPROC directive or put username into /etc/csf/csf.pignore
27
How to / Re: Install Apache 2.4.x and suPHP 0.7.2
« on: May 23, 2016, 07:05:55 PM »
Will be better if you put Require all granted into Apache virtual host template and after that rebuild vhosts
28
Apache / Re: Suspicious File Alert mail every night
« on: March 27, 2016, 04:38:39 AM »Can you just add these two lines as is to pignore or does it require a different format?
You should add them to /etc/csf/csf.fignore not ot pignoner file. pigone is for process ignoring respectively fignore for file ignoring rules
29
Apache / Re: Suspicious File Alert mail every night
« on: March 20, 2016, 02:02:07 PM »
Append at the end of /etc/csf/csf.fignore those 2 rows
Code: [Select]
/tmp/apache-build/.*
/tmp/php-build/.*
After that restart lfd and everything will be ok I prefer this approach will be better if is added as CWP CUSTOM rules as as the rows in /etc/csf/csf.pignore
30
Apache / Re: Need HTTP/2 support with Apache
« on: March 20, 2016, 11:51:18 AM »
Actually this is now easy task. First of all you have to upgrade your apache to version 2.4.17 or higher version to be able to run h2 module. This is major problem for old CMS Cpanel have a lot of issues with upgrades from 2.2 to 2.4 A lot easier is to run mod_spdy but it is potential security issue because use old ssl - if I remember correctly 1.0.1h also is not maintained a lot from apache foundation