Show Posts
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.
46
CentOS Configuration / Re: Quota not working (user and admin panels)
« on: June 25, 2021, 10:24:05 AM »
After recent update on CWP the email account usage are showing out of allowed space for each account, there was issue in CWP and it is a BUG. how these email users can use more than allow space for their email usage ? IF CWP is working fine this will not happen so below person always say there was no issue in CWP from our expreience CWP always have BUGS and it was not resolved or sorted yet.
We are facing same issue see the screenshot.
http://prntscr.com/16puu6e
We are facing same issue see the screenshot.
http://prntscr.com/16puu6e
there is no bug with quota in cwp
47
CSF Firewall / Re: Targeted attack on pop3d, SSH, IMAP, PORTS more than 500 IP are blocking a day
« on: May 17, 2021, 07:21:17 PM »
We asked CWP support they don't have any resolution for this issue. Even they are promoting for paid support.
We can take paid support from them as the CWP UPDATE LOG and all other things are perfect, but even using this
CWP panel for more than two year did seen any profession with CWP. Current situation is very dangerous but looking
for an solution for this hacking attempt but they are not thinking or considering it.
Yesterday I installed and activated KernelCare by cloudlinux.com but it was also not resolving our issue, finally closed
the pop3d port even stopping the Dovecot IMAP/POP3 Server we though this is good so the users will not face any mail issue
but they are not able to use any desktop email client. After that also getting another type of attack log added below
========== LOG ===============
Firewall message :
172.65.32.248 (US/United States/-) blocked with too many connections
Connections Log:
My server IP and the port they are trying
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55368 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55336 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55362 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55330 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55350 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55352 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55334 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55346 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55354 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55370 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55372 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55412 (ESTABLISHED)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55374 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55398 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55358 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55356 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55338 (TIME_WAIT)
We can take paid support from them as the CWP UPDATE LOG and all other things are perfect, but even using this
CWP panel for more than two year did seen any profession with CWP. Current situation is very dangerous but looking
for an solution for this hacking attempt but they are not thinking or considering it.
Yesterday I installed and activated KernelCare by cloudlinux.com but it was also not resolving our issue, finally closed
the pop3d port even stopping the Dovecot IMAP/POP3 Server we though this is good so the users will not face any mail issue
but they are not able to use any desktop email client. After that also getting another type of attack log added below
========== LOG ===============
Firewall message :
172.65.32.248 (US/United States/-) blocked with too many connections
Connections Log:
My server IP and the port they are trying
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55368 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55336 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55362 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55330 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55350 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55352 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55334 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55346 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55354 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55370 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55372 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55412 (ESTABLISHED)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55374 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55398 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55358 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55356 (TIME_WAIT)
tcp: 172.65.32.248:443 -> 173.XXX.XXX.X:55338 (TIME_WAIT)
48
CSF Firewall / Targeted attack on pop3d, SSH, IMAP, PORTS more than 500 IP are blocking a day
« on: May 16, 2021, 12:08:39 PM »
From the past 4-5 days my server was targeted by hacker, with in one to three second difference my LFD is alerting us message like below. In a day we are getting more than 500 pop3 login failed attempt from different IP address and different country.
So we stopped the Dovecot IMAP/POP3 Server service for a day but it will not given any resolution when ever we turn on the service attempt start again.
Any one have any solution to protect the server ?
Log entries:
May 16 17:15:59 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.com>, method=PLAIN, rip=5.95.195.241, lip= ip removed, session=<Y6QyBXHCFcEFX8Px>
May 16 17:15:37 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.in>, method=PLAIN, rip=83.110.207.34, lip=ip removed, session=<4f/kA3HCd+BTbs8i>
May 16 17:15:07 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.com>, method=PLAIN, rip=157.32.0.107, lip=ip removed, session=<JMMXAnHCo9+dIABr>
etc.... see the screen shot for more logs
So we stopped the Dovecot IMAP/POP3 Server service for a day but it will not given any resolution when ever we turn on the service attempt start again.
Any one have any solution to protect the server ?
Log entries:
May 16 17:15:59 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.com>, method=PLAIN, rip=5.95.195.241, lip= ip removed, session=<Y6QyBXHCFcEFX8Px>
May 16 17:15:37 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.in>, method=PLAIN, rip=83.110.207.34, lip=ip removed, session=<4f/kA3HCd+BTbs8i>
May 16 17:15:07 pop3-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<info@hosteddomain.com>, method=PLAIN, rip=157.32.0.107, lip=ip removed, session=<JMMXAnHCo9+dIABr>
etc.... see the screen shot for more logs
49
E-Mail / Re: LOT OF HACKING ATTEMPT LF_SMTPAUTH SASL LOGIN authentication failed
« on: June 15, 2020, 04:33:51 PM »
Any one have any idea to block some country like China, Iran Etc.. iam getting continuous attack now.
50
E-Mail / LOT OF HACKING ATTEMPT LF_SMTPAUTH SASL LOGIN authentication failed
« on: June 10, 2020, 04:15:10 PM »
Dear CWP,
Getting lot of attack from the past month itself, all attempt are from different county some of them are from the same country and we have blocked some country in the CC_DENY (CN,RU,BG,RU,BR,TR,LT,NL,TR,RO,IE,US) But some of our customers from CC_DENY list was not able to access their website. In the past month these attack was very less but in past day in was increased. As it was not possible to block all country's but you may need to tell us or implement an solution to block these type of attack on SMTP. Below i have added some of them with details please go through it and tell us an solution. Also we are not able to find out which user account they where trying to login ?
Latest:
Time: Wed Jun 10 19:28:38 2020 +0530
IP: 193.56.28.176 (GB/United Kingdom/-)
Failures: 3 (smtpauth)
Interval: 3600 seconds
Blocked: Permanent Block [LF_SMTPAUTH]
Log entries:
Jun 10 19:28:10 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 19:28:23 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 19:28:38 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Other
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:50:00 cbwh postfix/smtpd[14837]: warning: unknown[141.98.80.152]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 09:06:22 cbwh postfix/smtpd[17322]: warning: unknown[59.55.36.129]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:29:46 cbwh postfix/smtpd[12248]: warning: unknown[37.49.230.7]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:29:46 cbwh postfix/smtpd[12248]: warning: unknown[37.49.230.7]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 9 18:31:19 cbwh postfix/smtpd[28740]: warning: unknown[5.249.164.2]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 9 13:21:14 cbwh postfix/smtpd[27667]: warning: unknown[103.139.44.210]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Continuous Attack with different IP
Failures: 6 (smtpauth)
Interval: 3600 seconds
Blocked: Permanent Block [LF_SMTPAUTH]
Jun 8 23:07:43 cbwh postfix/smtpd[4946]: warning: unknown[46.38.145.247]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:08:01 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.251]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:06:20 cbwh postfix/smtpd[4946]: warning: unknown[46.38.145.252]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:04:20 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.253]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:04:20 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.253]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:57:40 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.6]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:57:44 cbwh postfix/smtpd[4558]: warning: unknown[46.38.145.249]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:56:48 cbwh postfix/smtpd[4558]: warning: unknown[46.38.145.248]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:51:43 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.4]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:50:24 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.5]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Getting lot of attack from the past month itself, all attempt are from different county some of them are from the same country and we have blocked some country in the CC_DENY (CN,RU,BG,RU,BR,TR,LT,NL,TR,RO,IE,US) But some of our customers from CC_DENY list was not able to access their website. In the past month these attack was very less but in past day in was increased. As it was not possible to block all country's but you may need to tell us or implement an solution to block these type of attack on SMTP. Below i have added some of them with details please go through it and tell us an solution. Also we are not able to find out which user account they where trying to login ?
Latest:
Time: Wed Jun 10 19:28:38 2020 +0530
IP: 193.56.28.176 (GB/United Kingdom/-)
Failures: 3 (smtpauth)
Interval: 3600 seconds
Blocked: Permanent Block [LF_SMTPAUTH]
Log entries:
Jun 10 19:28:10 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 19:28:23 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 19:28:38 cbwh postfix/smtpd[26746]: warning: unknown[193.56.28.176]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Other
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 18:23:02 cbwh postfix/smtpd[21826]: warning: gw70.coldimport.com.pe[209.45.62.70]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:50:00 cbwh postfix/smtpd[14837]: warning: unknown[141.98.80.152]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 09:06:22 cbwh postfix/smtpd[17322]: warning: unknown[59.55.36.129]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:29:46 cbwh postfix/smtpd[12248]: warning: unknown[37.49.230.7]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 10 12:29:46 cbwh postfix/smtpd[12248]: warning: unknown[37.49.230.7]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 9 18:31:19 cbwh postfix/smtpd[28740]: warning: unknown[5.249.164.2]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 9 13:21:14 cbwh postfix/smtpd[27667]: warning: unknown[103.139.44.210]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Continuous Attack with different IP
Failures: 6 (smtpauth)
Interval: 3600 seconds
Blocked: Permanent Block [LF_SMTPAUTH]
Jun 8 23:07:43 cbwh postfix/smtpd[4946]: warning: unknown[46.38.145.247]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:08:01 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.251]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:06:20 cbwh postfix/smtpd[4946]: warning: unknown[46.38.145.252]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:04:20 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.253]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 23:04:20 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.253]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:57:40 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.6]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:57:44 cbwh postfix/smtpd[4558]: warning: unknown[46.38.145.249]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:56:48 cbwh postfix/smtpd[4558]: warning: unknown[46.38.145.248]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:51:43 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.4]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 8 22:50:24 cbwh postfix/smtpd[3963]: warning: unknown[46.38.145.5]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
51
CentOS 7 Problems / Re: CWP found 191 available yum/rpm updates for your server ?
« on: May 05, 2020, 02:39:22 PM »the solution is posted many times in the forum.Code: [Select]rpm -e --nodeps python3-libs python3
Your answer is not relevant for the quest we have asked here, If don't know the answer please don't post.
For the user Who are facing this issue on CentOS 7 please follow below
Source : https://community.centminmod.com/threads/python-conflict-on-update.17144/
Code: [Select]
# remove ius community python34u
yum -y remove python34u python34u-devel python34u-pip python34u-setuptools python34u-tools python34u-libs python34u-tkinter
# remove ius community python36u
yum -y remove python36u python36u-devel python36u-pip python36u-setuptools python36u-tools python36u-libs python36u-tkinter
# install epel python34
yum -y install python34 python34-devel python34-pip python34-setuptools python34-tools python34-libs python34-tkinter
# install epel python36
yum -y install python36 python36-devel python36-pip python36-setuptools python36-tools python36-libs python36-tkinter
# reinstall removed dependencies from above removed ius community packages
yum -y install cmake3 cmake3-data
52
CentOS 7 Problems / CWP found 191 available yum/rpm updates for your server ?
« on: May 04, 2020, 02:46:33 PM »
After the Past four update of CWP PRO this is error Iam getting always why ? once in day or twise in a day Iam able to see New update are available in my CWP PRO but my YUM STOPPED updating the package after I have installed the CWP PRO PANEL update please let me know why this error is there any solution ?
Detailed yum log https://pastebin.com/VM0gr7QM
======== SOME YUM Error ==============
file /usr/lib64/python3.6/distutils/__pycache__/dir_util.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/file_util.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/_exceptions.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/_exceptions.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/expatreader.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/expatreader.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/handler.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/handler.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/saxutils.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/saxutils.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/xmlreader.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/xmlreader.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
Error Summary
-------------
Detailed yum log https://pastebin.com/VM0gr7QM
======== SOME YUM Error ==============
file /usr/lib64/python3.6/distutils/__pycache__/dir_util.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/file_util.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/_exceptions.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/_exceptions.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/expatreader.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/expatreader.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/handler.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/handler.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/saxutils.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/saxutils.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/xmlreader.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/xml/sax/__pycache__/xmlreader.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
Error Summary
-------------
53
Updates / Re: 190 new updates today!!!
« on: May 02, 2020, 02:04:46 PM »
Iam an pro user I also facing same type of issue from last 4 to 5 update installed in my server , today it shows me 191 Updates below is my yum log full yum log use here https://pastebin.com/YSs9z7ZZ please check and help
Code: [Select]
file /usr/lib64/python3.6/distutils/__pycache__/dir_util.cpython-36.pyc from i nstall of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package pyth on36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.opt-1.pyc fr om install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.opt-1.pyc from i nstall of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package pyth on36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/errors.cpython-36.pyc from ins tall of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python 36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/email/__pycache__/errors.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u- libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.opt-1. pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from pa ckage python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/fancy_getopt.cpython-36.pyc fr om install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/file_util.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from packa ge python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/file_util.cpython-36.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package pyt hon36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/filelist.cpython-36.opt-1.pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from packag e python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/filelist.cpython-36.pyc from i nstall of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package pyth on36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/msvc9compiler.cpython-36.opt-1 .pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from p ackage python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/msvc9compiler.cpython-36.pyc f rom install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/msvccompiler.cpython-36.opt-1. pyc from install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from pa ckage python36u-libs-3.6.8-1.el7.ius.x86_64
file /usr/lib64/python3.6/distutils/__pycache__/msvccompiler.cpython-36.pyc fr om install of python3-libs-3.6.8-13.el7.x86_64 conflicts with file from package python36u-libs-3.6.8-1.el7.ius.x86_64
54
Suggestions / Domain parking option when it will be available ?
« on: March 20, 2020, 02:52:34 PM »
Hi,
Still the team is improving the CWP service why you haven't enabled the domain name parking services in the
CWP or CWP PRO ? While creating an Package it was showing the Parked Domains options still it was not enabled
in any new updates. It was too much difficult to provide hosting services to customers, if an customer need to park
a domain name we need to add an extra Addon Domains in that package. So let me know when you will enable
this feature ?
Still the team is improving the CWP service why you haven't enabled the domain name parking services in the
CWP or CWP PRO ? While creating an Package it was showing the Parked Domains options still it was not enabled
in any new updates. It was too much difficult to provide hosting services to customers, if an customer need to park
a domain name we need to add an extra Addon Domains in that package. So let me know when you will enable
this feature ?
55
E-Mail / Re: Drop all emails if no rDNS/PTR and gmail
« on: March 03, 2020, 04:04:47 PM »
Did you find any solution for this iam also facing this issues in some accounts
56
Updates / Re: User Error logs disappeared after recent update
« on: February 24, 2020, 04:42:03 PM »
Hi, can you tell me if it can done from our end, as the CWP TEAM is looking only for get revenue but they for forgot about if there was feature the user will automatically move to paid version (CWP PRO) Because of the feature they are getting. So if you can explain these this can be added by administrator it will be helpful for other who looking for the same answer.
Seriously Devs. It's not that hard if you would be willing to expand basedirCode: [Select]sed -i "s@fastcgi_param PHP_ADMIN_VALUE \"open_basedir =/home@fastcgi_param PHP_ADMIN_VALUE \"open_basedir =/usr/local/apache/domlogs/:/home@g" /root/cwpsrv/conf.d/users/*.confcwpsrv -s reloadCode: [Select]cp -R /usr/local/cwpsrv/var/services/users/cwp_theme/origional /usr/local/cwpsrv/var/services/users/cwp_theme/modified/// PHP Section /usr/local/cwpsrv/var/services/user_files/modules/php_error.phpCode: [Select]<?phpHTML /usr/local/cwpsrv/var/services/users/cwp_theme/modified/mod_php_error.html <<< YOu might want to copy origional to modified so it doesn't go bye bye
if (isset($_GET["loadfile"])) {
if (file_exists("/usr/local/apache/domlogs/{$_GET["loadfile"]}.error.log")) {
echo $content = file_get_contents("/usr/local/apache/domlogs/{$_GET["loadfile"]}.error.log");
} else {
echo "No File Found";
};
exit;
}
// Replace this with built in code to populate domains and subdomains //
//use API to get list of users
$mod["returl"] = $_SERVER['REQUEST_URI'];
$data = array("key" => "(SET YOUR API KEY HERE)","action"=>'list',"user"=>$_SESSION ['username']);
$url = "https://{$_SERVER['SERVER_NAME']}:2304/v1/accountdetail";
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt ($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt ($ch, CURLOPT_POST, 1);
$response = curl_exec($ch);
curl_close($ch);
$response = json_decode($response);
$domains = array();
$mod['select'] = array();
foreach ($response->result->domains as $key) {
$domains[] = trim($key->domain);
}
foreach ($response->result->subdomins as $key) {
$domains[] = trim($key->subdomain .".". $key->domain);
}
foreach ($domains as $domain) {
$mod['select'][] = $domain;
}
if (file_exists("/usr/local/apache/domlogs/{$domains[0]}.error.log")) {
$mod['file'] = file_get_contents("/usr/local/apache/domlogs/{$domains[0]}.error.log");
} else {
$mod['file'] = "No File Found";
};
?>Code: [Select]<div class="row">javascript /usr/local/cwpsrv/var/services/users/cwp_theme/modified/js/modules/php_error.js.twig
<div class="col-lg-12">
<h1>Error Log</h1>
</div>
<div>
/usr/local/apache/domlogs/
<form action="{{mod.returl}}" action="get"><select id="loadfile">
{% for option in mod.select %}
<option>{{ option }}</option>
{% endfor %}
</select><noscript><input type="submit" value="Change"></noscript></form>
<textarea id="logfile" readonly style="width:800px; height:400px">{{mod.file}}</textarea>
</div>
</div>Code: [Select](function($){INI File /usr/local/cwpsrv/var/services/users/cwp_lang/en/php_error.ini
$(document).ready(function() {
$("#loadfile").change(function() {
$.get( "{{mod.returl}}", { loadfile: $("#loadfile").val() },"text" )
.done(function( data ) {
if (data == "") data = "Congratulations! No PHP Errors were logged";
$("#logfile").text(data);
});
});
});
})(jQuery);Code: [Select]SOMETHING="Nobody Really Cares"
Edit file /usr/local/cwpsrv/var/services/users/cwp_theme/modified/menu_left.html
find (~ Line 62)
{% if ("statistics" in rmenu )or(swmenu==1) %}
<li class="search"><a href="?module=statistics">{{langene.GNLABEL51}}</a></li>
{% endif %}
add after
<li class="search"><a href="?module=php_error">PHP Error Log</a></li>
57
Updates / Re: User Error logs disappeared after recent update
« on: February 24, 2020, 04:38:19 PM »
Seriously it was very hard to find when a small error occur while executing an script. In the error log viewer there was was option to check date wise. Currently we are running and in the CWP hosting account it have user, manager and admin directory each folder inside some script have some issues in a day that CRM was using by more than 50 users with different with different privilege. If we check the error log for an single folder issue we can't find it when we give Results lines as 1 or 10 So it was an serious mistake in CWP. If the CWP TEAM can build an Hosting panel like this why this option was possible ?
58
Updates / Re: User Error logs disappeared after recent update
« on: February 04, 2020, 04:37:21 PM »The error logs stay in the /usr/local/apache/domlogs/*.error.log
If it can't be accessible or view able by the hosted user what is the use of it. Before reply think twise.
It was an important thing which each hosted user needed it.
59
Updates / Re: User Error logs disappeared after recent update
« on: February 04, 2020, 04:35:46 PM »yes all access and error logs are in /usr/local/apache/domlogs/ sorted by individual domain name.
If the error logs are not accessible by the user in their control panel what was the use to staying it there ..?
Error logs are very important for users, if they have sort of issues in their script how they can access it if it was
not view able from their control panel ? Did you think each time the server admin or support have time to share
the error logs with them ..?
60
Updates / User Error logs disappeared after recent update
« on: February 03, 2020, 04:35:51 PM »
Dear Developers,
Congratulate for the new login window, Iam an PRO user, after recent update error log option is not showing
any where in the user control panel. So please let me know if it was removed or it will be available when any error
happen in php script which Cpanel follow. So please let me know where is our error log
If any one know how to move this user error logs to their public directory or error occurring folder same like
Cpanel. OR please consider this request to be added in your next update to move the error logs to user direcotry
by this way user usage quota will also effect and if any one is not caring about error log they will start looking to
it if their quota was full because of error log files.
Congratulate for the new login window, Iam an PRO user, after recent update error log option is not showing
any where in the user control panel. So please let me know if it was removed or it will be available when any error
happen in php script which Cpanel follow. So please let me know where is our error log
If any one know how to move this user error logs to their public directory or error occurring folder same like
Cpanel. OR please consider this request to be added in your next update to move the error logs to user direcotry
by this way user usage quota will also effect and if any one is not caring about error log they will start looking to
it if their quota was full because of error log files.
