Messages

16

CentOS-WebPanel Bugs / AutoSSL Does not Install Correct Domain

« on: April 20, 2019, 06:40:34 AM »

Common Name missmatch when using AutoSSL.
It's install as hostname, not a real domain name.

Here's the info from sslshopper.com :
None of the common names in the certificate match the name that was entered (billing.domain.com). You may receive an error when accessing this site in a web browser.

And Common Name missmatch info :
Common name: srv.domain.com
SANs: srv.domain.com

billing.domain.com is my real domain and srv.domain.com is my hostname.
See?  it's a different domain name when I'm using AutoSSL to generate SSL.

~ (note) domain.com for example domain only ~

17

CentOS-WebPanel Bugs / Re: WARNING: User Panel possible issue detected! If you have issues with user panel

« on: April 16, 2019, 08:43:40 AM »

Resolved by disabled CSF

Code: [Select]

csf-x

Then, Enabled CSF

Code: [Select]

csf-e

18

CentOS-WebPanel Bugs / WARNING: User Panel possible issue detected! If you have issues with user panel

« on: April 16, 2019, 05:06:52 AM »

WARNING: User Panel possible issue detected! If you have issues with user panel login, CSF Firewall restart will be needed.

Another bugs 

Still cant login CWP.user after restart CSF firewall.

19

CentOS-WebPanel Bugs / Re: All sorts of weird things happening.

« on: April 15, 2019, 12:07:26 PM »

Try to increase max_allowed_packet and timeout in my.cnf

Add / edit below line in /etc/my.cnf
Or in CWP.adm -> SQL Service -> MySQL Configuration

Code: [Select]

[mysqld]
max_allowed_packet = 500M
interactive_timeout = 300
wait_timeout = 300

Big query packet also need increasing of innodb_buffer_pool_size, you can tune your database mysql with "mysqltuner"

20

CentOS 6 Problems / Re: All CWP panel force to using SSL

« on: April 10, 2019, 03:47:17 AM »

why do you even use HTTP for root login, this is highly insecure and you should use HTTPS over your hostname.

Also, this is http to https redirect so it has no anything with the sessions, it can be related to only that you have multiple windows in the same browser open with the different sessions id.

Just convince us if all must be force to SSL, auto renew SSL for hostname must be run perfectly.
Because there are some cases on my server auto renew SSL does not work even it has been configured and checked "auto renovation" as active.

21

Postfix / Re: Can't connect to smtp (postfix) via SSL from sites on the VPS

« on: April 09, 2019, 06:31:15 PM »

Try to :

1. Generate your hostname to get SSL working

CWP.admin > Servers Setting > Change Hostname

2. Then generate MailServer

CWP.admin > Email > Mail Server Manager

22

CentOS 6 Problems / Re: All CWP panel force to using SSL

« on: April 09, 2019, 06:23:18 PM »

Hi, I have the some problem. Please help. How do disabled force all url to secure port ssl?

You can't disabled or modify anything in CWP. It's useless.
The next any CWP update will erase your all configuration on your server.

So, I suggest you follow all the rules.
Because the only CWP's team has rules to modify your server or CWP config.

23

CentOS-WebPanel Bugs / Re: localhost 2030 http --> 2031 https, but nothing have sertificat!

« on: April 09, 2019, 11:57:04 AM »

It is enough! Every update is even worse. I'm afraid of losing my files in the future.
I'm starting to use CyberPanel with the suggestion of a friend from the forum.
.
do what the hell you want ...

agree with you, every cwp update is coming a fulls of bugs.
I'm always facing this issue on every update "502 Bad Gateway" with error :

Code: [Select]

ERROR: Unable to include /usr/local/cwp/php71/etc/php-fpm.d/users.conf from /usr/local/cwp/php71/etc/php-fpm.conf at line 24
[09-Apr-2019 03:07:05] ERROR: failed to load configuration file '/usr/local/cwp/php71/etc/php-fpm.conf'
[09-Apr-2019 03:07:05] ERROR: FPM initialization failed

I'm tired with this command "sh /scripts/restart_cwpsrv" to fix any issue which CWP team cannot fix it automatically when CWP update coming.

24

CentOS-WebPanel Bugs / Re: localhost 2030 http --> 2031 https, but nothing have sertificat!

« on: April 09, 2019, 08:51:22 AM »

Yes. CWP now force you to use SSL.

You must generate hostname in CWP.admin to get SSL working.
And you can use your hostname for login to cwp, for example :

srv.mydomaim.com:2031

25

CentOS 6 Problems / All CWP panel force to using SSL

« on: April 09, 2019, 04:15:54 AM »

My cwp panel has been down because its redirect to using SSL. All port from 2030 redirect to 2031.

And after login it will automatically logout because "invalid session"

What happen to cwp?

26

CentOS 7 Problems / Re: Default page appears, even though account completely set up

« on: March 19, 2019, 06:18:17 PM »

It may related with your vhost.
you set up IP 192.168.1.10 in ur local machine but in your Virtualhost 192.168.1.20:80

Set the appropriate shared IP in "CWP Settings" -> "Edit Setting".

27

CentOS 6 Problems / Re: Apache http not work, only https

« on: March 19, 2019, 11:31:23 AM »

Check your error_log

Let us know about your error, so we can help you.

28

Apache / Re: Internal Server Error

« on: March 17, 2019, 08:14:33 PM »

Yes, I got the same issue.
All my website are going down because the new CWP6 update.

Options FollowSymLinks and SymLinksIfOwnerMatch are both off, so the RewriteRule directive is also forbidden due to its similar ability to circumvent directory restrictions

Resolved by added in .htaccess with this line :
Options +SymLinksIfOwnerMatch

29

Postfix / Re: PostFix Setup problems...

« on: December 19, 2018, 06:24:55 PM »

You must set your reverse DNS in OVH.

- Go to your OVH Manager
- Change default reverse name "vps584125.vps.ovh.ca" to your domain of webserver hostname,
For example: "mail.domain.com" and set IP "1.2.3.4"

*) Make sure you already set A record for your reverse domain name.
 

30

Installation / Re: New account domain not pointing to /home/USERNAME/public_html

« on: December 15, 2018, 08:12:26 AM »

If your domain already pointing to CWP and modified index.html but still showing CWP banner it can be your vhost issue.
Your domain indicate to run by default page of CWP not in your DocumentRoot.

Try to restarting named and httpd :

Code: [Select]

$ service named restart
$ service httpd restart

Or in your CWP.admin dashboard see "Service Status" panel
- restart "BIND DNS Server"
- restart "Apache Webserver"