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
CentOS-WebPanel Bugs / Re: BUG on PHP Builder
« on: May 13, 2018, 07:20:26 AM »
I have experienced the same problem as the persons above, and it seems that this is a general bug, as a great many incidents with the exact same description turns up when searching the web...

Therefore it is not a 'one time on one server' incident and therefore needs to be taken care of.

Today I updated PHP to 7.2.5 and the same happened, just like it happened when I updated to 5.6.36 and other PHP versions on CWP servers.

I am sure that the CWP administrators have been logging in to several clients servers since March to see what happens and why, but we are now in May and still it happens on a new installation on 7.2.5 as well as on 5.6.36...

Maybe it would be an idea for the CWP administrators to post an update on the problem and an ETA for a solution?

Information / Re: Changelog....?
« on: January 16, 2018, 06:11:03 AM »
I contacted CWP regarding the changelog and they said that they are, actually, replacing all old modules with new ones and once this has been done, they will post the changelogs.

However, I think its a very bad practice to change the things silently while it does not take more than few minutes to post the changelogs.

Any CWP team or forum management can put light on it?

Thanks for sharing that information.

I do think however that even that information - if correct - should have been shared with the users....

The website changelog and Facebook has not been updated since October 2017 and such rare changelog updates usually only happens to software that are close to being obsolete

We - as CWPPRO users - can see that updates are actually happening as the version numbers are changing, but why not share some light on what is actually happening in the machineroom...?

Remember that users are made of illusive material - if not nurtured and cared for they tend to fade away to other 'flowers'.....

Information / Changelog....?
« on: January 13, 2018, 09:55:22 AM »
It seems like the changelog on Facebook and on has stalled...?

Yes - I know that 'only major changes' are listed, but really...?

Updating the changelog only takes seconds and is a major help to all your users, that somestimes has to guess what can have caused a strange behaviour or similar time consuming things - simply list what changes in the running updates to keep your customers updated on what is going on...

- or read this

Anyhow - the issue persists after 3 months and was introduced after an update by CWP - so why they still havenīt fixed it after 3 months is hard to say.....

Postfix / Re: Let's build New Postfix Email Server
« on: December 30, 2017, 09:09:40 AM »
This issue has been around for several months now for CWP7 users:

Why hasnīt it been fixed permanently?

Try fixing such open bugs sooner - you intoduced the bug almost 3 months ago.......

Postfix / Re: postfix cannot install dkim -unit not found
« on: December 30, 2017, 09:03:03 AM »
As far as I remember, this was a bug introduced after the new version of UI was introduced in November 2017 - then administrators of CWP wrote that there was a patch for the bug, but that they would fix the bug in 'a coming release'

However, no Administrator has updated the Changelog, neither on the CWP site or on Facebook, even though several 'releases' has been implemented since then, so affected users are in a Limbo here...

Igor or other CWP administrator: What is happening with this bug???

SPF / Re: policyd-spf skip_addresses not IP network
« on: November 05, 2017, 09:51:22 AM »
Any ETA for a permanent fix for this issue?

Quite annoying not being able to use SPF/DKIM and implementing a temporary fix that might give trouble ahead, does not seem to be a good choice....

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:


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

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

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 or similar, the cer is alright when checking in the form and port 443 also in the browser it is allright and shows the correct cert.

When checking on 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...?

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.

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

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

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?

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?

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

Pages: [1] 2 3