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 3
1
SSL / Re: CWP hostname certificate not renewed
« on: September 21, 2017, 08:38:19 AM »
Ok - Igor came with a command I didnīt see anywhere in the FAQ or elsewhere, but it did the trick:

/scripts/restart_cwpsrv

Unfortunately it seems to have started a new problem in the Postfix with clamd looping, but thatīs another issue..

2
CentOS-WebPanel Bugs / Re: clamd is stopped....
« on: September 21, 2017, 08:34:47 AM »
- same here - clamd is hammering away on close to 100%



Ok - found a solution here in the forum -  it solved the problem:

service clamd stop
rm -f /var/run/clamd.amavisd/clamd.sock
service clamd start

3
SSL / Re: CWP hostname certificate not renewed
« on: September 20, 2017, 09:48:30 AM »
Hmnnn - after checking a lot I have not found out, that if I check the AutoSSL cert via eg.sslchecker.com or similar, the cer is alright when checking in the form my.domain.com and port 443 also in the browser it is allright and shows the correct cert.

When checking on my.domain.com:2031 it shows the old expired cert in browser and sslchecker

Yes - I have used service cwpsrv start, several times but to no avail, yes, I have restarted httpd, yes, I have cleared cache in browser, yes, I have tried a completely new browser..

Apparently it is some kind of redirect in CWP that doesnīt work as it should for the hostname, but I canīt seem to find that redirect anywhere....?

Anybody got an idea...?


4
SSL / Re: CWP hostname certificate not renewed
« on: September 13, 2017, 02:30:10 PM »
when changing hostname have you got info that autoSSL was installed ?
In case that autoSSL installed certificate output would give you certificate in your browser, if you don't get any ssl output then it generates self signed certificate.

One more important thing is that you need to rebuild your mail server after changing your hostname.

As mentioned in my description above, the 'change hostname' action produced a valid AutoSSL cert, whereas this cert do not show, instead it shows the expired old autossl cert, whereas the Postfix and Dovecot services now use the new self signed cert instead of the correct and new hostname autossl cert which it did before I renewed it via 'change hostname' option...

As also mentioned - everythong worked 100% correct from startup 3 months ago and until autorenewal failed a few days ago...

In my eyes a clear bug.


5
SSL / Re: CWP hostname certificate not renewed
« on: September 13, 2017, 09:40:13 AM »
try to change hostname and then return it back to old

Regarding auto renewal try to contact cwp development to check it
http://centos-webpanel.com/contact

I can see others that are facing the same problem with autorenewal failing, so it seems to be a bug

6
SSL / Re: CWP hostname certificate not renewed
« on: September 13, 2017, 09:25:57 AM »
Did you have server hostname mentioned in Let's Encrypt Config file /usr/local/cwpsrv/conf/cwpsrv.conf   ???


# months ago this server started with CentOs7 and newest cwp - adding the hostname perfectly created the ssl cert.

A few days ago the SSL certs ran out although they were made via AutoSSL and therefore should autorenew themselves - neither the hostname cert or any of the other certs made at the same time, autorenewed.

I therefore ran autorenew of the non-hostname ssl certs and that worked just fine.

I then went to 'change hostname' kept the old hostname and clicked 'change hostname'

The ssl cert renewed with no problem, but now the hostname cert is still using the old cert and the services Dovecot and Postfix now uses the CWP generated certificate instead of the correct one, that is, the same as the hostname should use

When checking the certs at the ssl cert location, I see that the certs are indeed the new ssl cert and when checking the Dovecot and Postfix ssl settings they are also set to use the new hostname ssl just as they are supposed to do, but they are indeed using the wrong and cwp generated selfsigned cert...

Checking the certs location /etc/pki/... I see that there seems to be a few redirects from dovecot/postfix/ and others eg.:

link server-postfix.crt → /etc/pki/tls/certs/hostname.crt

I donīt remember if they were ther before, but it seems as if these links could make a kind of loop sending the application to look the wrong place for the certs...

I think this is a bug created by CWP when creating the SSL certs, as it seems it creates aīcorrect AutoSSL letsencrypt cert when clicking the 'change hostname' but at the same time creates an autogenerated selfsigned ssl cert and creates links to these selfsigned certs instead of using the correct AutoSSL generated certs...

I have not enough insight to see what will happen if I just delete the links mentioned above, if the system will know to use the correct AutoSSL generated certs when the links are gone...

My thoughts are - if it worked just fine before I ran the renewal, why is there a problem after I ran the renewal?

Anybody outthere know of a solution?

7
SSL / CWP hostname certificate not renewed
« on: September 12, 2017, 08:19:53 AM »
For smoe reason the SSL certs on the server did not autorenew although AutoSSL is used - I therefore manually updated all certs, that worked - I did though assume that renewal was automatic?

BUT - the server hostname cert gives some problems.

It expired and I therefore tried to go to 'change hostname' page and hit the 'change hostname' but kept the name.

The output showed that the cert was renewed, but the browser showed that it doesnīt work.

I restarted httpd, restarted cwp, cleared cache in browser - to no avail - it still shows the old cert...?

What has to be done to make it show correct?


8
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


9
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?  :-\

10
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 :)

11
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

12
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øø

13
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...


14
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.  >:(

15
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..

Pages: [1] 2 3