Messages

1516

SSL / Re: Lets Encrypt ROOT CA Expired

« on: October 01, 2021, 06:03:43 AM »

Only the DST Root CA X3 certificate expired on 30 September 2021.

The certificates are now using the ISRG Root X1 certificate automatically.
So there is nothing that needs to be done to "fix".

They only talk about older devices which may not get security updates anymore.
If you have your encryptions stings setup correctly this shouldn't be a problem.

1517

Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.

« on: September 30, 2021, 09:21:28 PM »

This might sound like a stupid question, but need to make sure there is a SSL certificate for the server.

The server does have a FQDN pointed to its IP?

Have you run the (Server Settings -> Change Hostname) to get the servers SSL certificate?

1518

Information / Re: CWP Pro paid invoice

« on: September 29, 2021, 06:38:01 PM »

Have you submitted a Billing support ticket?

We use PayPal when paying our invoices without problems.

1519

Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.

« on: September 29, 2021, 06:34:48 PM »

Postfix is your SMTP (Outgoing)
Dovecot is your IMAP/POP3 (Incoming)

Are you having problems with outbound emails (postfix) or incoming emails (dovecot)?

In your email client, temporarily change you incoming email server name to your server FQDN.
That will troubleshoot if your MX has a problem.

1520

Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.

« on: September 27, 2021, 05:29:17 PM »

Sep 25 02:40:54 host1 postfix/master[802591]: terminating on signal 15
Sep 25 02:40:54 host1 postfix[803347]: Postfix is running with backwards-compatible default settings
Sep 25 02:40:54 host1 postfix[803347]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Sep 25 02:40:54 host1 postfix[803347]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
Sep 25 02:40:54 host1 postfix/postfix-script[803402]: warning: not owned by root: /etc/postfix/./mysql-virtual_vacation.cf
Sep 25 02:40:54 host1 postfix/postfix-script[803415]: starting the Postfix mail system
Sep 25 02:40:54 host1 postfix/master[803417]: daemon started -- version 3.4.8, configuration /etc/postfix
Sep 25 02:40:54 host1 postfix/qmgr[803419]: 47E0B65D4B5: from=<billscott92787@gmail.com>, size=3953, nrcpt=1 (queue active)
Sep 25 02:40:54 host1 postfix/lmtp[803422]: 47E0B65D4B5: to=<kelly@familymaidservices.com>, relay=host1.wvwgssolutions.com[private/dovecot-lmtp], delay=2194, delays=2194/0.02/0/0, dsn=4.2.0, status=deferred (host host1.wvwgssolutions.com[private/dovecot-lmtp] said: 451 4.2.0 <kelly@familymaidservices.com> Internal error occurred. Refer to server log for more information. [2021-09-25 02:40:54] (in reply to end of DATA command))
Sep 25 02:41:04 host1 postfix/smtpd[803432]: connect from c-73-135-99-232.hsd1.md.comcast.net[73.135.99.232]
Sep 25 02:41:17 host1 postfix/smtpd[803442]: connect from mail-oo1-f42.google.com[209.85.161.42]
Sep 25 02:41:17 host1 postfix/smtpd[803442]: warning: loading SNI data for mail.familymaidservices.com: ignoring PEM type: CERTIFICATE REQUEST
Sep 25 02:41:17 host1 postfix/smtpd[803442]: Anonymous TLS connection established from mail-oo1-f42.google.com[209.85.161.42] to mail.familymaidservices.com: TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
Sep 25 02:41:17 host1 postfix/smtpd[803442]: NOQUEUE: reject: RCPT from mail-oo1-f42.google.com[209.85.161.42]: 450 4.7.0 <Kelly@familymaidservices.com>: Recipient address rejected: defer_if_permit requested; from=<billscott92787@gmail.com> to=<Kelly@familymaidservices.com> proto=ESMTP helo=<mail-oo1-f42.google.com>
Sep 25 02:41:18 host1 postfix/smtpd[803442]: disconnect from mail-oo1-f42.google.com[209.85.161.42] ehlo=2 starttls=1 mail=1 rcpt=0/1 bdat=0/1 quit=1 commands=5/7



e.com[209.85.210.41] ehlo=2 starttls=1 mail=1 rcpt=1 bdat=1 quit=1 commands=7
Sep 25 00:43:07 host1 postfix/pipe[665998]: 2BBA4FC1B7: to=<kelly@familymaidservices.com>, relay=dovecot, delay=0.09, delays=0.06/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: lda(kelly@familymaidservices.com): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied


I don't know what I'm not doing right or what needs changed to get this working.  A buddy of mine setup CWP, and everything, and email just worked, but mine I've had nothing but issues getting to get it working.    Any tips?  I got this far tailing the log and playing around with settings until I got email to go outbound and not hit spam box.

Something happened in the last update to 0.9.8.1084.

Rebuild your mail server from inside CWP, like @studio4host suggested, and you should be good to go.

1521

Installation / Re: clarification with thunderbird setings

« on: September 24, 2021, 07:28:52 PM »

I don't know.  Google is sending everything to spam on different severs.  I am using tbird client.  When I set up an account I normally use mail.mydomain.com for smtp and imap.  But when I do that, tbird throws an error saying certificates dont match.   When I view the certificate from letsencrypt it says server.mydomain.com and not mail.mydomain.com

Can someone help me stratighten this mess out.?

Now I just tried sending from a different domain and the LE cert says common name is www.mydomain.com

Thanks.

Under your SSL Certificates, make you you have the Mail service added.

Then in your DNS:
Create MX record: mail MX 0 mail.domain.com
Then create an A record for mail 1.2.3.4

SMTP should use StartTLS, while incoming should use SSL/TLS

We currently use Thunderbird 91.1.1

1522

Installation / Re: clarification with thunderbird setings

« on: September 24, 2021, 07:25:11 PM »

I am also getting this error message in tbird when I send mail.

Unable to communicate securely with peer: requested domain name does not match the server’s certificate.

Just got that also after the update today to 0.9.8.1084

Rebuild your Postfix configuration and that should go away.

1523

Updates / Re: Why not implement TLS 1.3 support per default

« on: September 24, 2021, 07:22:49 PM »

Hi, i just received the new Update  CWPpro version: 0.9.8.1081 and was a bit disappointed to see a bunch of new Webserver templates but still no TLS 1.3 implementation per default.

It would be very cool if you could implement TLS 1.3 out of the Box in CWP or is there a Reason why you still doesn't have implemented it yet?


thanks

There is a simple way to enable this, along with HTTP/2.0 & ALPN:

https://www.mysterydata.com/how-to-enable-tls-1-3-in-apache-on-cwp-control-web-panel-centos-7-centos-8-el7-el8/

1524

Updates / Re: 0.9.8.1084 Bug

« on: September 24, 2021, 07:20:12 PM »

Rebuilt the Postfix configuration and all seems to be working again.

1525

Updates / 0.9.8.1084 Bug

« on: September 24, 2021, 07:15:06 PM »

When 0.9.8.1084 auto installed today, there is a bug with sending emails now using the domain name:


Sending of the message failed.
Unable to communicate securely with peer: requested domain name does not match the server's certificate.
The configuration related to [domain name] must be corrected.


Everything was working fine before the update.
SSL certificate is still vaild.

1526

Installation / Re: Issues with connection on CWP servers

« on: September 22, 2021, 09:29:42 PM »

Is this error on a new install or update?

Again, I know CWP has had problems with their repos in the past.
But usually it's after you switch to them for updates.

1527

Installation / Re: Issues with connection on CWP servers

« on: September 22, 2021, 06:24:27 PM »

I'm guessing you are running CentOS Stream using the CWP repos.

The CWP repos have had problems in the past.

If you are using Stream, you can switch back to the stream beta repos, or redo the server.
I would recommend AlmaLinux, since they also are the same company who does CloudLinux.

1528

CentOS-WebPanel Bugs / Re: CPU 100% clamd

« on: September 19, 2021, 09:09:47 AM »

gerasandor method and clamd_fix_100_cpu_usage does not work for me. anyone have another solution?

Run the fix in the /scripts directory, and then log into the admin panel and manually STOP ClamAV & AMaViS.

After CPU goes down to 0%, Start Just ClamAV, wait for it to run a quick scan, it should go back to 0, then Start AMaViS.

You should be good to go.

Had the same problem, and this worked.

1529

Installation / Re: AlmaLinux

« on: September 03, 2021, 02:51:31 PM »

Any way to update from Centos7 to Centos 8 stream?

I know it's still recommended to stay on Centos 7 but i mean for the future one day we will need to update, is this possible or is there anything in progress for getting this done?


A complete reinstall is not a good solution as there are still a lot of things not getting backed up and restored.

Would be cool to have a solution for this scenario, not now but after Centos7 EOL

thanks

As far as I know there is not upgrade from CentOS 7 to CentOS 8 or Stream.

But the built in CWP to CWP Migration tools works great.

1530

Installation / Re: AlmaLinux

« on: September 03, 2021, 02:49:55 PM »

upgrade current centos 8 core to stream :
https://www.mysterydata.com/convert-centos-8-to-centos-8-stream-install-cwp-control-panel-in-centos-8-stream/

Problem is once you upgrade to Stream, you are stuck there with no return possible.

The migrations scripts for AlmaLinux & Rocky Linux only work on CentOS 8.3 or 8.4, NOT Stream.