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.
Pages: [1] 2
1
How to / Re: WHMCS+CWP Problem
« on: April 06, 2021, 04:19:57 PM »After waiting so many days for a reply I gave up on waiting. Last night I wake up 1:30, sit down on my notebook and I rewrote the addon almost from zero. Now the addon is working fine with WHMCS 6.3.1. Also tested on WHMCS 7.1.2 and also working fine. I want to make some more improvements and I will share it with you.
Hello thanks for your good job. your module have trouble with new WHmcs. I god this: Allowed IP's not set or you don't have access from IP.
Thanks
2
CentOS 7 Problems / Re: All domains suddenly bring up landing page or 500 error
« on: November 23, 2019, 12:24:57 AM »
Hello I have the same probleme. Can't see the domain. i see the default centos page.
3
Backup / Re: Is there any way to make remote backup to google drive ?
« on: August 15, 2019, 03:34:30 AM »This is based on a script I use for another Control Panel.
What this script does is backup everything in "/backup" folder (admin backups), and upload it to google drive in tar.gz format, this script will run after the CWP admin backup script has ran.
To use; get the gdrive binary for your OS (https://github.com/gdrive-org/gdrive#downloads).
Centos 6/7 64bit:Code: [Select]wget https://drive.google.com/uc?id=1Ej8VgsW5RgK66Btb9p74tSdHMH3p4UNb&export=download
Centos 6 32-bitCode: [Select]wget https://drive.google.com/uc?id=1eo9hMXz0WyuBwRxPM0LrTtQmhTgOLUlg&export=download
Make it executable:Code: [Select]chmod +x gdrive
Move it to /usr/sbinCode: [Select]mv gdrive /usr/sbin/
Setup:Code: [Select]gdrive about
Follow the link and get the verification code by authenticating with the google account for the drive you want access to.
Add the script into /root directory named: GDbackup.sh:Code: [Select]nano /root/GDbackup.sh
Copy and paste the below script into the new file using (CTRL C / CTRL V).
And then save the file:Code: [Select]CTRL + X + Y
Script:Code: [Select]#!/bin/bash
IFS=$'\n'
# Copy the folder you want to store your file in at Google Drive (eg. https://drive.google.com/.../folders/...).
DRIVEFOLDERID=
# Days in which to delete the old backups from google drive (set 0 to disable).
DELETEDAYS=180
echo "#############################################"
echo " ---Google Drive Backup--- "
echo "#############################################"
gdrive about
echo "#############################################"
DATE=$(date '+%d-%m-%Y')
TS=$(date +'%H%M%S')
tar -czvf /tmp/$HOSTNAME.$DATE.$TS.backup.tar.gz -C / backup > /dev/null
BAKFILE=/tmp/$HOSTNAME.$DATE.$TS.backup.tar.gz
if [ -e "$BAKFILE" ] ; then
if [ "$DELETEDAYS" > 0 ]; then
upTime=$(date --date="$DELETEDAYS days ago" '+%Y-%m-%dT%T')
gdrive list -q "name contains 'backup.tar.gz' and name contains '$HOSTNAME' and modifiedTime < '$upTime'" >> drive.txt
filename='drive.txt'
# Read the list file
while read -r line
do
theId=$(cut -c-2 <<< "$line")
#basically skip the first line...
if [ "$theId" != "Id" ]; then
echo "Deleting old backup file: "
gdrive delete $(cut -c-33 <<< "$line")
fi
done < $filename
# Remove temp list file
rm -rf drive.txt
fi
gdrive upload -p "$DRIVEFOLDERID" --delete "$BAKFILE"
# ensures removal of backup file from /tmp
rm -rf "$BAKFILE"
echo "Backup to Google Drive is complete..."
echo "#############################################"
fi
exit 0
Run this command to activate the automated cron job:Code: [Select]echo 'sh /root/GDbackup.sh' >> /etc/cron.daily/cwp
You will see the backup information in the email that CWP sends when the backup cron has ran, you can also run the script manually:Code: [Select]sh /root/GDbackup.sh
and enjoy your free space...! Hope this helps others..
Thanks for this tips.
But I see this not make cron each day. how to see tach cron? Another thing i see the backup don't take the email account. How to add email account in the backup.
Thanks
4
CentOS-WebPanel Bugs / Re: dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 22, 2019, 05:57:25 PM »
Thank you very much
5
CentOS-WebPanel Bugs / Re: dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 22, 2019, 05:56:54 PM »
good it's work now.
6
Installation / Re: Centos 6 or 7, Which one is the best
« on: May 22, 2019, 05:50:37 PM »
The [PHP Switcher] doesn't work. Every times I try to put it to php7 it stuck
7
Installation / Re: Centos 6 or 7, Which one is the best
« on: May 22, 2019, 12:16:46 PM »
but in centos 7 can't install the latest php 7
8
CentOS-WebPanel Bugs / Re: dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 22, 2019, 12:14:44 PM »
the second command give this output:
[root@sv1 ~]# yum -y install dovecot-pigeonhole dovecot-mysql
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirror.cisp.com
* extras: repo1.ash.innoscale.net
* remi-safe: repo1.ash.innoscale.net
* updates: mirrors.mit.edu
Package 1:dovecot-pigeonhole-2.0.9-22.el6.x86_64 already installed and latest version
Package 1:dovecot-mysql-2.0.9-22.el6.x86_64 already installed and latest version
Nothing to do
----------
[root@sv1 ~]# service dovecot restart
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: service(stats): executable is empty
[FAILED]
[root@sv1 ~]#
[root@sv1 ~]# yum -y install dovecot-pigeonhole dovecot-mysql
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirror.cisp.com
* extras: repo1.ash.innoscale.net
* remi-safe: repo1.ash.innoscale.net
* updates: mirrors.mit.edu
Package 1:dovecot-pigeonhole-2.0.9-22.el6.x86_64 already installed and latest version
Package 1:dovecot-mysql-2.0.9-22.el6.x86_64 already installed and latest version
Nothing to do
----------
[root@sv1 ~]# service dovecot restart
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: service(stats): executable is empty
[FAILED]
[root@sv1 ~]#
9
CentOS-WebPanel Bugs / Re: dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 22, 2019, 11:48:56 AM »
it's empty
10
CentOS-WebPanel Bugs / Re: dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 21, 2019, 11:50:21 AM »
Hello,
Thanks for the reply
/etc/dovecot/conf.d/20-managesieve.conf don't exist
/etc/dovecot/conf.d/10-master.conf
#default_process_limit = 100
#default_client_limit = 1000
# Default VSZ (virtual memory size) limit for service processes. This is mainly
# intended to catch and kill processes that leak memory before they eat up
# everything.
#default_vsz_limit = 256M
# Login user is internally used by login processes. This is the most untrusted
# user in Dovecot system. It shouldn't have access to anything at all.
#default_login_user = dovenull
# Internal user is used by unprivileged processes. It should be separate from
# login user, so that login processes can't disturb other processes.
#default_internal_user = dovecot
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
#port = 993
#ssl = yes
}
# Number of connections to handle before starting a new process. Typically
# the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
# is faster. <doc/wiki/LoginProcess.txt>
#service_count = 1
# Number of processes to always keep waiting for more connections.
#process_min_avail = 0
# If you set service_count=0, you probably need to grow this.
#vsz_limit = 64M
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
inet_listener pop3s {
#port = 995
#ssl = yes
}
}
service lmtp {
unix_listener lmtp {
#mode = 0666
}
# Create inet listener only if you can't use the above UNIX socket
#inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
#address =
#port =
#}
}
service imap {
# Most of the memory goes to mmap()ing files. You may need to increase this
# limit if you have huge mailboxes.
#vsz_limit = 256M
# Max. number of IMAP processes (connections)
#process_limit = 1024
}
service pop3 {
# Max. number of POP3 processes (connections)
#process_limit = 1024
}
service auth {
# auth_socket_path points to this userdb socket by default. It's typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its default
# permissions make it readable only by root, but you may need to relax these
# permissions. Users that have access to this socket are able to get a list
# of all usernames and get results of everyone's userdb lookups.
unix_listener auth-userdb {
#mode = 0600
#user =
#group =
}
# Postfix smtp-auth
#unix_listener /var/spool/postfix/private/auth {
# mode = 0666
#}
# Auth process is run as this user.
#user = $default_internal_user
}
service auth-worker {
# Auth worker process is run as root by default, so that it can access
# /etc/shadow. If this isn't necessary, the user should be changed to
# $default_internal_user.
#user = root
}
service dict {
# If dict proxy is used, mail processes should have access to its socket.
# For example: mode=0660, group=vmail and global mail_access_groups=vmail
unix_listener dict {
#mode = 0600
#user =
#group =
}
}
Thanks for the reply
/etc/dovecot/conf.d/20-managesieve.conf don't exist
/etc/dovecot/conf.d/10-master.conf
#default_process_limit = 100
#default_client_limit = 1000
# Default VSZ (virtual memory size) limit for service processes. This is mainly
# intended to catch and kill processes that leak memory before they eat up
# everything.
#default_vsz_limit = 256M
# Login user is internally used by login processes. This is the most untrusted
# user in Dovecot system. It shouldn't have access to anything at all.
#default_login_user = dovenull
# Internal user is used by unprivileged processes. It should be separate from
# login user, so that login processes can't disturb other processes.
#default_internal_user = dovecot
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
#port = 993
#ssl = yes
}
# Number of connections to handle before starting a new process. Typically
# the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
# is faster. <doc/wiki/LoginProcess.txt>
#service_count = 1
# Number of processes to always keep waiting for more connections.
#process_min_avail = 0
# If you set service_count=0, you probably need to grow this.
#vsz_limit = 64M
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
inet_listener pop3s {
#port = 995
#ssl = yes
}
}
service lmtp {
unix_listener lmtp {
#mode = 0666
}
# Create inet listener only if you can't use the above UNIX socket
#inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
#address =
#port =
#}
}
service imap {
# Most of the memory goes to mmap()ing files. You may need to increase this
# limit if you have huge mailboxes.
#vsz_limit = 256M
# Max. number of IMAP processes (connections)
#process_limit = 1024
}
service pop3 {
# Max. number of POP3 processes (connections)
#process_limit = 1024
}
service auth {
# auth_socket_path points to this userdb socket by default. It's typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its default
# permissions make it readable only by root, but you may need to relax these
# permissions. Users that have access to this socket are able to get a list
# of all usernames and get results of everyone's userdb lookups.
unix_listener auth-userdb {
#mode = 0600
#user =
#group =
}
# Postfix smtp-auth
#unix_listener /var/spool/postfix/private/auth {
# mode = 0666
#}
# Auth process is run as this user.
#user = $default_internal_user
}
service auth-worker {
# Auth worker process is run as root by default, so that it can access
# /etc/shadow. If this isn't necessary, the user should be changed to
# $default_internal_user.
#user = root
}
service dict {
# If dict proxy is used, mail processes should have access to its socket.
# For example: mode=0660, group=vmail and global mail_access_groups=vmail
unix_listener dict {
#mode = 0600
#user =
#group =
}
}
11
CentOS-WebPanel Bugs / dovecot can't start: error in unknown setting : managesieve_max_line_length
« on: May 20, 2019, 10:25:28 PM »
Hello,
With two servers i have the same trouble with dovecot>
Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 144: Unknown setting: managesieve_max_line_length
When i remove dovecot and install dovecot it't start for fews minutes if i change hostname or rebuild mailserver the dovecot stop again and can't start.
With two servers i have the same trouble with dovecot>
Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 144: Unknown setting: managesieve_max_line_length
When i remove dovecot and install dovecot it't start for fews minutes if i change hostname or rebuild mailserver the dovecot stop again and can't start.
12
CentOS 6 Problems / Can't see my hostname server in module ssl
« on: August 07, 2018, 03:29:11 PM »
Hello,
After change de hostname. I can't see my svr.domain.com display in list module ssl.
thanks
After change de hostname. I can't see my svr.domain.com display in list module ssl.
thanks
13
Installation / Re: CWP account API error in creation a new account in WHMCS
« on: March 17, 2018, 08:00:31 PM »
Hello,
Thank you for your module its' work. Their are two problemes, when suspend an account the website associate with the website stil alive.
Thanks
Thank you for your module its' work. Their are two problemes, when suspend an account the website associate with the website stil alive.
Thanks
14
SSL / Re: Secure CWP Admin Panel Port 2031
« on: March 12, 2018, 08:19:14 PM »
Hello i got the same probleme with some port.
openssl s_client -connect hostname:2031 -servername hostname
I got notice
openssl s_client -connect hostname:2031 -servername hostname
I got notice
15
SSL / Re: I can't see ssl.conf file in Apache Include Conf
« on: March 12, 2018, 08:04:33 PM »
thanks
Pages: [1] 2