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.


Messages - muscator

Pages: [1] 2
1
Suggestions / Re: AWstats
« on: June 30, 2017, 06:00:35 AM »
It seems that this topic is not on a steady roadmap yet..?

Whatīs the ETA of implementing a statistics module in CWP?

If you see the statistics on this topic, you will see that in 2 years almost 35,000 has expressed interest in the topic (thatīs how many views it has had) so this is a feature of extremely high interest for the users


2
New Modules / Re: Migrate CWP->CWP
« on: June 17, 2017, 09:16:43 AM »
There is already a module for this but you are giving the last touches, please be patient ...!

 ;D  Ok - nice to hear that something is actually happening - this topic was started 18 months ago and I can se many others requesting this feature....

Have just finished a completely manual migration of cwp6->cwp7 without using rsync or similar and that is not a task I would like to do very often as it is so far from what is the actual idea of using a controlpanel instead of all manual coding and work

The whole idea of a controlpanel is to hide all the time consuming tasks behind easily accessible cp links where tasks are performed with almost no user input  --  all automated

But nice to hear that finally a CWP-CWP migration module is being launched...

Any ETA?  :-\

3
CentOS 7 Problems / phpMyadmin max upload size...
« on: June 14, 2017, 06:58:38 PM »
I have spent a lot of time trying to solve the max size error in phpMyadmin Centos 7 - it says 64Mib and everywhere I search for answers on how to raise the limit it seems that everybody says:

" just raise the limits in php.ini, then restart apache, mysql "

Ok - been there, done that, but to no avail - max size still claims to be 64Mib

I have searched for the limit '64Mib' everywhere but canīt seem to locate it...

Somebody outthere must have met the same problem and solved it and therefore haven an easy-to-do solution for me...?

The server itself is completely new installed Centos7 with newest CWP version, so still has most of its default values...

Help appreciated - thanks :)

4
New Modules / Re: Migrate CWP->CWP
« on: June 14, 2017, 10:23:11 AM »
For some reason nobody from CWP has had any comments to this and it seems as if Pedro that promised to work on a migration module 18 months ago has stopped developing...?

Anybody working on this feature?

CWP developers: Please make this a priority feature - many need it

5
Suggestions / Migration module CWP->CWP
« on: May 18, 2017, 06:46:09 AM »
A much needed module in CWP is a migration module from one CWP installation to another.

After the release of CWP for CentOS 7.x a lot of CentOS 6.x users will need an easy migration in the future and instead of spending a lot of time doing this manually, a migration module that takes care of the entire migration is very high on the wish list... ;)

Hopefully someone will jump right into this project and constuct such a module to make CWP an even stronger optionøø

6
SSL / Re: Missing info.....
« on: May 01, 2017, 06:13:28 AM »
letsencrypt module was buggy so we have updated old ssl manager and there will be much more improvements on that module as we will add new webservers, php handlers and automatic ssl installers for all domains/subdomains on the server.

Letsencrypt module will no longer have any updates but you can use it like you did till now.

Info about bigger updates is on the site and facebook.

Thanks for the information.

Concerning changelog info:

As already mentioned many people do not use Facebook for obvious reasons and that seems to be the only place to search for changelog updates - furthermore there are no exact changelog so if something has happened to an installation during an autoupdate of the cwp version, there is no way to track down what can have caused the error as no exact changelog information is visible anywhere - only 'major' updates are explained and then only on Facebook...

Why not make a section on your customerarea that handles ALL changelogs and where registred clients can log in and see ALL changelogs..?

I am sure that will take some weight off the customersupport with related questions...

Work with us - not against us... ;D


Furthermore - in the features of the new AutoSSL management system:

PLEASE add a feature that easily removes obsolete domains SSL with a click of a button - right now it is annoying to spend a lot of valuable time to do this manually - I asked for it more than a year ago, but so far nothing has happened....?

ALSO - add a feature for autocreation of hostname SSL (not a self-signed version but a proper LetsEncrypt certificate) as many things are handled via the hostname URL and therefore a selfsigned ssl produces warnings each time - not good for obvious reasons...


7
SSL / Missing info.....
« on: April 12, 2017, 08:09:31 AM »
I am confused.... :-\

After  doing the update to the newest cwp version, I see that Letsencrypt manager no longer is to be used and that the AutoSSL is to be used instead...?

Why?

And why is there no info at all about this rather major change?

What is going on?

Not much point in running a PRO version of CWP if I as a PRO user arenīt receiving any info at all about changes, changelog etc.

Not all use Facebook - for obvious reasons - and therefore relying on all changelog updates entirely on facebook is not an option for CWP - why not have a mailinglist or a proper changelog place, at least for PRO users...?

But - the SSL options right now are very confusing as CWP hasnīt released any info at all about the letsencrypt manager not being in use anymore...

Please inform about what is going on! Thanks.  >:(

8
Suggestions / Removal of invalid domainnames in letsencrypt
« on: January 09, 2017, 03:57:44 PM »
It would be very highly appreciated, if eg. ssl enabled domains would be removed from letsencrypt ssl listing whenever a domainname is removed from the 'normal' domainlist via CWP interface or at least that there is a 'button' in letsencrypts interface that makes it possible to remove the non-valid or stale domains from the list to avoid the letsencrypt 'up-to'date' function to keep informing that this or that domain is no longer possible to renew or similar messages..

9
Thanks for the instructrions - after having followed them exactly and after having no errors in output, I checked them on
http://checkgzipcompression.com/ - none of the domains or subdomains have gzip enabled....

Only problem I can see ( and that has got nothing to do with the 'main' domains) is that the rebuild shows that some of the subdomains, although working fine, seems to be missing their IP for some reason)

Well - here is an update:

I ran the rebuild v hosts several times and managed to get all domains gzip enabled.

I discovered however, taht many of my subdomains - although working fine - are NOT in the vhost list....? Any idea why?



What can be wrong?


Ok - hereīs latest update on this:

After paying a support ticket to CWPfolks, they discovered that the missing gzip and other problems was caused by a bug in cwp, and that bug was corrected in cwp 0.9.8.131 - I checked and that solution solved the bug.

BUT - not in the SSL enabled domains (infact that is all of them...;-) - here gzip implementing after the above description does not work, not even when adding the code manually....

Any ideas?


10
MySQL / Re: Extreme mysql load!
« on: December 22, 2016, 02:47:57 PM »
Hi guys,

We're a web-hosting company helping our customer to migrate. This is our first experience with CWP and it seems like it's a great control panel but...   before the migration the customer was complaining mysql load was too high. We installed CWP from scratch with MariaDB 10.1.19 and migrated the website but the load is still there. I mean it's really huge ~700-900%CPU. We tried some mysql tweaks but they don't seem to work. We tried moving as much as possible into RAM and ram usage increased from 0.1%, 0.2% etc to 4-5% (running top command) so caching works but it doesn't seem to affect cpu load - it's still huge! Even when the number of php processes is not so big only ~15-20 server load is ~25-30% and %CPU is ~400! The server is a dual hexa-core Xeon with 64GB ram and more than 30GB are available!

We're at a loss here really close to wiping everything and installing cpanel. Please assist.

I experienced the same when upgrading MySQL to 5.6.35.

It seems that the new MySQL version per default has performance scheme enabled.

Just disable performance scheme in my.cnf by adding the line

performance_schema = 0

Then restart mysql and thats it (unless other things in your environment is influencing the high load)


11
MySQL / Canīt add user to MySQL databases
« on: December 22, 2016, 02:44:32 PM »
Hi,

After upgrading MySQL to vers. 5.6.35 instead of the very old defayl version in cwppro, I am now unable to add database users to new databases

In the cwp interface I use 'create database + user' the output show that both are created, but checking in the list the user is not added.

If then clicking on the 'add new user' next to the new database, it shows the user is added, but when checking in the listing, it shows that the user is not added...

Very strange.

Anybody got an idea of how to solve this?

Running CWPPro 0.9.8.128



12
Actually I finally received a response that pointed me in the right direction, I had tried the solution before but to no avail, but this time I added some other actions and now it finally works - thanks for all responses...

13
Hi, it should be works.
Contact with CWP support http://centos-webpanel.com/support-services

It seems like letīs encrypt do not overrule the standard SSL cert placement for CWP, leaving the old selfsigned cert in working mode and the new hostname cert is not 'seen' by cwp/apache...

It works just fine for all other domains, just not for the hostname cert

Does anybody have a workaround for this problem...?

Apparently CWP autosearches for the ssl provided by the selfsigned function at the 'normal' place for CWP certs and NOT at the 'new' ssl location provided by the letīs encrypt certs, so it is probably a simple workaround - but how...??

Hi Igor,

Unfortunately it doesnīt work - furthermore I have raised a ticket at the address you mention, but nobody has responded yet....?


14
Hi Igor, I have - as you suggested - contacted
CWP support http://centos-webpanel.com/support-services

but so far havenīt heard anything from them....

As mentioned before, Iīm sure there is a simple workaround to the problem, I just havenīt been able to find it yet.....

Any assistance would be appreciated.

15
Hi, it should be works.
Contact with CWP support http://centos-webpanel.com/support-services

It seems like letīs encrypt do not overrule the standard SSL cert placement for CWP, leaving the old selfsigned cert in working mode and the new hostname cert is not 'seen' by cwp/apache...

It works just fine for all other domains, just not for the hostname cert

Does anybody have a workaround for this problem...?

Apparently CWP autosearches for the ssl provided by the selfsigned function at the 'normal' place for CWP certs and NOT at the 'new' ssl location provided by the letīs encrypt certs, so it is probably a simple workaround - but how...??

Pages: [1] 2