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.
166
CentOS 7 Problems / Re: Can you help me plzz
« on: May 01, 2019, 10:05:58 PM »
** Important (as your error message itself):
===========================================================================================
**Check your MySQL root password in: /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php and /root/.my.cnf
===========================================================================================
This means the root password in file:
/usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php
and in the file:
/root/.my.cnf
must be exactly the same.
Check that.
Regards,
Netino
===========================================================================================
**Check your MySQL root password in: /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php and /root/.my.cnf
===========================================================================================
This means the root password in file:
/usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php
and in the file:
/root/.my.cnf
must be exactly the same.
Check that.
Regards,
Netino
167
Information / Re: mysqli_error()
« on: May 01, 2019, 10:02:16 PM »
1) You must restart mariadb server with the mariadb unit.
The command is:
(for CentOS7):
or
(for CentOS6):
2) ** Important (as your error message itself):
===========================================================================================
**Check your MySQL root password in: /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php and /root/.my.cnf
===========================================================================================
This means the root password in file:
/usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php
and in the file:
/root/.my.cnf
must be exactly the same.
Regards,
Netino
The command is:
(for CentOS7):
Code: [Select]
# systemctl restart mariadb
or
(for CentOS6):
Code: [Select]
# service mariadb restart
2) ** Important (as your error message itself):
===========================================================================================
**Check your MySQL root password in: /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php and /root/.my.cnf
===========================================================================================
This means the root password in file:
/usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php
and in the file:
/root/.my.cnf
must be exactly the same.
Regards,
Netino
168
CentOS-WebPanel Bugs / Re: CWP API Manager
« on: May 01, 2019, 04:10:37 AM »
Did you already tried this?:
(with separated arguments, and '--data', not '-data')
Regards,
Netino
Code: [Select]
curl -k "https://xxx.xxx.xxx.xxx:2304/v1/account" -X POST --data "key=IEmzLcOF4Hsozt9bTopbrhQ19nPt6ZuM3BA4pjK49nzVf" --data "action=list"
(with separated arguments, and '--data', not '-data')
Regards,
Netino
169
Installation / Re: can't start Webpanel
« on: May 01, 2019, 04:01:08 AM »
Post the result of the following command:
Regards,
Netino
Code: [Select]
# netstat -tupln | grep -P ":2[0-3][0-9]+"
Regards,
Netino
170
Updates / Re: Latest updates have created a huge list of MD5 Checksum errors on CWP
« on: May 01, 2019, 03:35:23 AM »
This means just the files showed are binary different from before.
If you did run "yum update" this is completely normal.
You should be concerned only if you have not changed anything in your server.
But still csf does these updates automatically, alone, and causes such warnings.
But these warnings are completely important to keep your eyes watching your server.
Regards,
Netino
If you did run "yum update" this is completely normal.
You should be concerned only if you have not changed anything in your server.
But still csf does these updates automatically, alone, and causes such warnings.
But these warnings are completely important to keep your eyes watching your server.
Regards,
Netino
171
E-Mail / Re: CWP Email Issue
« on: April 21, 2019, 11:30:40 PM »
So you are having problem with Gmail, not with CWP.
In general, any unknown sender can be classified as spam in Gmail.
Don't forget if your server are new, it doesn't still a reputation in internet, specially in mail blacklists, as a good mail sender.
In general, any unknown sender can be classified as spam in Gmail.
Don't forget if your server are new, it doesn't still a reputation in internet, specially in mail blacklists, as a good mail sender.
172
CentOS 7 Problems / Re: error 403 Forbidden
« on: April 20, 2019, 04:24:33 AM »
Chrome redirect automatically from 'http' to 'https'.
So, your site *must* be responsive too in 'https'.
This is the case..??
So, your site *must* be responsive too in 'https'.
This is the case..??
173
E-Mail / Re: CWP Email Issue
« on: April 19, 2019, 09:48:27 PM »
What tool are you using to filter spam..??
Regards,
Netino
Regards,
Netino
174
CentOS 7 Problems / Re: error 403 Forbidden
« on: April 19, 2019, 08:22:47 PM »
Error 403 is an webserver level error, just make sense to search in webserver logs.
Might be you looking at the wrong logs.
It may be that a wrong configuration can send requests to other areas, thus logging into different file logs.
If in apache virtual hosts are not being logged events, the first bet is to search in main server error log, at '/usr/local/apache/logs/error_log'.
As you are mentioning to use nginx, you must to check if the events are being logged in nginx logs.
You must check where in your configuration, normally in '/etc/nginx/nginx.conf', and the error log in '/var/log/nginx/error.log'.
Might be too your configuration is not logging events in the severity is wish.
Check the directive "error_log" in the configuration file.
Regards,
Netino
Might be you looking at the wrong logs.
It may be that a wrong configuration can send requests to other areas, thus logging into different file logs.
If in apache virtual hosts are not being logged events, the first bet is to search in main server error log, at '/usr/local/apache/logs/error_log'.
As you are mentioning to use nginx, you must to check if the events are being logged in nginx logs.
You must check where in your configuration, normally in '/etc/nginx/nginx.conf', and the error log in '/var/log/nginx/error.log'.
Might be too your configuration is not logging events in the severity is wish.
Check the directive "error_log" in the configuration file.
Regards,
Netino
175
Apache / Re: Could not Restart Apache
« on: April 18, 2019, 04:06:41 AM »
CentOS7 have a different way to logging events, due to using systemd, mainly to start/restart/stop program events.
You must post here the output of the command:
Regards,
Netino
You must post here the output of the command:
Code: [Select]
# systemctl status httpd.service
Regards,
Netino
176
SSL / Re: File that points to CWP SSLCert
« on: April 15, 2019, 12:42:27 AM »
Sorry if I really do not know if I understand your question, but the answer is:
Regards,
Netino
Code: [Select]
/etc/pki/tls/certs/hostname.crt
Regards,
Netino
177
SSL / Re: SSL on webpanel
« on: April 15, 2019, 12:36:25 AM »
Yes, but for the main host you will not need to install from CWP.
Just put in place the files:
In my case these files don't exist, I just create a symbolic link to the real files.
To create the symbolic links:
Just put in place the files:
Code: [Select]
/etc/pki/tls/certs/hostname.bundle
/etc/pki/tls/certs/hostname.crt
/etc/pki/tls/private/hostname.key
In my case these files don't exist, I just create a symbolic link to the real files.
Code: [Select]
/etc/pki/tls/certs/hostname.bundle -> /etc/pki/tls/certs/host1.panel.xwy.bundle
/etc/pki/tls/certs/hostname.crt -> /etc/pki/tls/certs/host1.panel.xwy.cert
/etc/pki/tls/private/hostname.key -> /etc/pki/tls/private/host1.panel.xwy.key
To create the symbolic links:
Code: [Select]
ln -s /etc/pki/tls/certs/host1.panel.xwy.bundle /etc/pki/tls/certs/hostname.bundle
ln -s /etc/pki/tls/certs/host1.panel.xwy.cert /etc/pki/tls/certs/hostname.crt
ln -s /etc/pki/tls/private/host1.panel.xwy.key /etc/pki/tls/private/hostname.key
179
SSL / Re: SSL on webpanel
« on: April 14, 2019, 04:18:58 AM »
AutoSSL is for Letsencrypt certificates.
If you have already a Comodo Certificate, supposedly you must put the (file with the) cert in the "/etc/pki/tls/certs/" and put the key in "/etc/pki/tls/private/", and access CWP -> Webserver Settings -> Tab "Install From Server", and choose the file certificate, and user and the domain, and click in install.
Regards,
Netino
If you have already a Comodo Certificate, supposedly you must put the (file with the) cert in the "/etc/pki/tls/certs/" and put the key in "/etc/pki/tls/private/", and access CWP -> Webserver Settings -> Tab "Install From Server", and choose the file certificate, and user and the domain, and click in install.
Regards,
Netino
180
Apache / Re: HSTS in CWP
« on: April 14, 2019, 04:09:57 AM »
In Apache, add the following parameter in the VHOST site:
or
The max-age parameter sets the browser the validity period in seconds that HTTPS will be forced, in which case it will be 6 months. The "includeSubDomains" parameter indicates that this rule will apply to subdomains.
Regards,
Netino
Code: [Select]
Header add Strict-Transport-Security "max-age=15768000"
or
Code: [Select]
Strict-Transport-Security: max-age=15768000; includeSubDomains
The max-age parameter sets the browser the validity period in seconds that HTTPS will be forced, in which case it will be 6 months. The "includeSubDomains" parameter indicates that this rule will apply to subdomains.
Regards,
Netino
