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.
391
Problems on other RedHat linux servers / Re: blah.blan.com ssl almalinux 8.9
« on: March 06, 2024, 08:19:14 PM »
The server can't be mail.blah.com
The server must have a unique sub-hostname from your domain, most just use e.g. srv1.blah.com.
THEN you crate a user account with the hostname mail.blah.com
AND IF the A record is pointing correcting, the SSL certificate that you create will work.
CWP -> CWP Migration is tricky, it needs port 2304 open for TCP_IN & TCP_OUT.
The server must have a unique sub-hostname from your domain, most just use e.g. srv1.blah.com.
THEN you crate a user account with the hostname mail.blah.com
AND IF the A record is pointing correcting, the SSL certificate that you create will work.
CWP -> CWP Migration is tricky, it needs port 2304 open for TCP_IN & TCP_OUT.
392
E-Mail / Re: AutoSSL for webmail and mail only
« on: March 04, 2024, 05:57:48 PM »
When you create the account, you have to set the domain name as e.g. mail.domain.com
Otherwise the SSL will fail because the domain isn't pointing to CWP.
Then just create your MX record and A records to point to CWP at your DNS provider.
To access webmail, you will have to create a redirect (which CWP usually does automatically in Apache), or just use mail.domain.com/webmail.
Otherwise the SSL will fail because the domain isn't pointing to CWP.
Then just create your MX record and A records to point to CWP at your DNS provider.
To access webmail, you will have to create a redirect (which CWP usually does automatically in Apache), or just use mail.domain.com/webmail.
393
Suggestions / Re: Roundcube 1.6
« on: March 02, 2024, 07:21:34 AM »
There are code changes between the PHP versions.
Hopefully the next version will be based on 8.1 or 8.2, but so far it looks like 7.4.
Hopefully the next version will be based on 8.1 or 8.2, but so far it looks like 7.4.
394
CentOS 9 Problems / Re: Any update on a CWP release for CENTOS 9 Delayed Stream?
« on: March 01, 2024, 10:09:00 PM »
RHEL Clone 9 Testing is ongoing.
Problem seems to be libraries are in different locations, and names.
We have semi-successfully upgraded AlmaLinux 8 to AlmaLinux 9.
Everything seems to work, except PHP rebuilding.
Problem seems to be libraries are in different locations, and names.
We have semi-successfully upgraded AlmaLinux 8 to AlmaLinux 9.
Everything seems to work, except PHP rebuilding.
395
Installation / Re: Installation problem when trying to access repo https://espejito.fder.edu.uy
« on: March 01, 2024, 03:14:40 AM »
The link above is to the MariaDB repo mirror config.
For distro, select either RHEL 7 or 8. Depending on what you have installed.
You have to select the version MariaDB you have, or follow the CWP upgrade wiki.
This is basic server administration.
For distro, select either RHEL 7 or 8. Depending on what you have installed.
You have to select the version MariaDB you have, or follow the CWP upgrade wiki.
This is basic server administration.
396
Installation / Re: I have centos 7 want only the server as the only domain...
« on: February 28, 2024, 03:23:37 AM »
iRedMail works on AlmaLinux 8 and 9.
Even works on FreeBSD.
Just uses Postfix & Dovecot like CWP does. Also includes SOGo
What are your server specs?
8 & 9 aren't any more resource hogs than 7 was.
Even works on FreeBSD.
Just uses Postfix & Dovecot like CWP does. Also includes SOGo
What are your server specs?
8 & 9 aren't any more resource hogs than 7 was.
397
Updates / Re: Automatic YUM Updates?
« on: February 27, 2024, 05:06:57 PM »
For some reason that cron wasn't working. :/
Found dnf-automatic, and have that running on 1 server.
Create a KB article for AlmaLinux 8 and CentOS 7.
Found dnf-automatic, and have that running on 1 server.
Create a KB article for AlmaLinux 8 and CentOS 7.
398
Suggestions / Re: Roundcube 1.6
« on: February 27, 2024, 02:48:52 PM »
You can update RoundCube to 1.5.6, which is a LTS version.
https://www.alphagnu.com/topic/33-update-cwp-roundcube-mail-version-156-%E2%80%93-control-web-panel/
CWP can't update to 1.6.x due to PHP 7.3 being required, and CWP uses PHP 7.2 as it's core version.
https://www.alphagnu.com/topic/33-update-cwp-roundcube-mail-version-156-%E2%80%93-control-web-panel/
CWP can't update to 1.6.x due to PHP 7.3 being required, and CWP uses PHP 7.2 as it's core version.
399
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 27, 2024, 02:42:18 PM »Where is this 8 pages installation instruction / upgrade Maria to LTS page.
Can you please provide me its link. I had just followed the installation notes on the landing site. I think that link shall be added there as well.
It's an internal document we created to make it easier to bring servers online, and make sure nothing is missed.
Just started making it this month, and have had 19 updates so far. :/
Something we might put on our public KB soon, if there is interest.
But most sys admins like doing their own configs.
The MariaDB Wiki can be found at: https://wiki.centos-webpanel.com/mariadb-upgrade-to-new-version
But I think you found it already.
Just replace the 10.5 with 10.11.
400
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 27, 2024, 02:37:22 PM »
CWP -> CWP Migration is tricky, you have to have the right port (2304) open thru the firewall on both servers.
And any hardware firewalls, if you have them also.
This is just needed during the transfer, after you are complete, you can close that port.
And any hardware firewalls, if you have them also.
This is just needed during the transfer, after you are complete, you can close that port.
401
Installation / Re: I have centos 7 want only the server as the only domain...
« on: February 26, 2024, 11:25:11 PM »
CentOS 7 is EOL.
So you would want to setup a server using AlmaLinux 8.
CWP has to have a Hostname, which is usually a sub-domain.
So if you TLD is domain.com, make a DNS A record for srv1.domain.com, and then you can create a user account for domain.com
This user account sets up the web, email, DNS etc. as CWP is a complete hosting solution.
If you just want to use email, you can. But the other items will still be there unused, since you wouldn't be pointing any A records to those services.
CWP doesn't use base hostname except for panel access.
So you would want to setup a server using AlmaLinux 8.
CWP has to have a Hostname, which is usually a sub-domain.
So if you TLD is domain.com, make a DNS A record for srv1.domain.com, and then you can create a user account for domain.com
This user account sets up the web, email, DNS etc. as CWP is a complete hosting solution.
If you just want to use email, you can. But the other items will still be there unused, since you wouldn't be pointing any A records to those services.
CWP doesn't use base hostname except for panel access.
402
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 26, 2024, 04:29:12 PM »following installation script, as soon as i runCode: [Select]yum -y update
I got these errors and I lost my interest in this oneCode: [Select]Total 31 MB/s | 542 MB 00:17
AlmaLinux 8 - BaseOS 3.3 MB/s | 3.4 kB 00:00
Importing GPG key 0xC21AD6EA:
Userid : "AlmaLinux <packager@almalinux.org>"
Fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
AlmaLinux 8 - AppStream 3.3 MB/s | 3.4 kB 00:00
Importing GPG key 0xC21AD6EA:
Userid : "AlmaLinux <packager@almalinux.org>"
Fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for kernel-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: kernel-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for kernel-core-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: kernel-core-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for kernel-modules-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: kernel-modules-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for linux-firmware-20230824-120.git0e048b06.el8_9.noarch.rpm is not installed. Failing package is: linux-firmware-20230824-120.git0e048b06.el8_9.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for NetworkManager-1.40.16-13.el8_9.alma.1.x86_64.rpm is not installed. Failing package is: NetworkManager-1:1.40.16-13.el8_9.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for NetworkManager-libnm-1.40.16-13.el8_9.alma.1.x86_64.rpm is not installed. Failing package is: NetworkManager-libnm-1:1.40.16-13.el8_9.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for NetworkManager-team-1.40.16-13.el8_9.alma.1.x86_64.rpm is not installed. Failing package is: NetworkManager-team-1:1.40.16-13.el8_9.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for NetworkManager-tui-1.40.16-13.el8_9.alma.1.x86_64.rpm is not installed. Failing package is: NetworkManager-tui-1:1.40.16-13.el8_9.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for glibc-2.28-236.el8_9.12.x86_64.rpm is not installed. Failing package is: glibc-2.28-236.el8_9.12.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for glibc-common-2.28-236.el8_9.12.x86_64.rpm is not installed. Failing package is: glibc-common-2.28-236.el8_9.12.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for glibc-gconv-extra-2.28-236.el8_9.12.x86_64.rpm is not installed. Failing package is: glibc-gconv-extra-2.28-236.el8_9.12.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for glibc-langpack-en-2.28-236.el8_9.12.x86_64.rpm is not installed. Failing package is: glibc-langpack-en-2.28-236.el8_9.12.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for gnutls-3.6.16-8.el8_9.1.x86_64.rpm is not installed. Failing package is: gnutls-3.6.16-8.el8_9.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for kernel-tools-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: kernel-tools-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for kernel-tools-libs-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: kernel-tools-libs-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libssh-0.9.6-13.el8_9.x86_64.rpm is not installed. Failing package is: libssh-0.9.6-13.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libssh-config-0.9.6-13.el8_9.noarch.rpm is not installed. Failing package is: libssh-config-0.9.6-13.el8_9.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libsss_autofs-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: libsss_autofs-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libsss_certmap-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: libsss_certmap-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libsss_idmap-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: libsss_idmap-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libsss_nss_idmap-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: libsss_nss_idmap-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libsss_sudo-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: libsss_sudo-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for openssh-8.0p1-19.el8_9.2.x86_64.rpm is not installed. Failing package is: openssh-8.0p1-19.el8_9.2.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for openssh-clients-8.0p1-19.el8_9.2.x86_64.rpm is not installed. Failing package is: openssh-clients-8.0p1-19.el8_9.2.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for openssh-server-8.0p1-19.el8_9.2.x86_64.rpm is not installed. Failing package is: openssh-server-8.0p1-19.el8_9.2.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for platform-python-3.6.8-56.el8_9.3.alma.1.x86_64.rpm is not installed. Failing package is: platform-python-3.6.8-56.el8_9.3.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for python3-libs-3.6.8-56.el8_9.3.alma.1.x86_64.rpm is not installed. Failing package is: python3-libs-3.6.8-56.el8_9.3.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for python3-perf-4.18.0-513.18.1.el8_9.x86_64.rpm is not installed. Failing package is: python3-perf-4.18.0-513.18.1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for python3-rpm-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: python3-rpm-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for python3-urllib3-1.24.2-5.el8_9.2.noarch.rpm is not installed. Failing package is: python3-urllib3-1.24.2-5.el8_9.2.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for rpm-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: rpm-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for rpm-build-libs-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: rpm-build-libs-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for rpm-libs-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: rpm-libs-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for rpm-plugin-selinux-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: rpm-plugin-selinux-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for rpm-plugin-systemd-inhibit-4.14.3-28.el8_9.x86_64.rpm is not installed. Failing package is: rpm-plugin-systemd-inhibit-4.14.3-28.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sos-4.6.1-1.el8.alma.1.noarch.rpm is not installed. Failing package is: sos-4.6.1-1.el8.alma.1.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sqlite-libs-3.26.0-19.el8_9.x86_64.rpm is not installed. Failing package is: sqlite-libs-3.26.0-19.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sssd-client-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: sssd-client-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sssd-common-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: sssd-common-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sssd-kcm-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: sssd-kcm-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sssd-nfs-idmap-2.9.1-4.el8_9.5.alma.1.x86_64.rpm is not installed. Failing package is: sssd-nfs-idmap-2.9.1-4.el8_9.5.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for sudo-1.9.5p2-1.el8_9.x86_64.rpm is not installed. Failing package is: sudo-1.9.5p2-1.el8_9.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for tzdata-2024a-1.el8.noarch.rpm is not installed. Failing package is: tzdata-2024a-1.el8.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for cloud-init-23.1.1-11.el8_9.1.alma.1.noarch.rpm is not installed. Failing package is: cloud-init-23.1.1-11.el8_9.1.alma.1.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for libmaxminddb-1.2.0-10.el8_9.1.x86_64.rpm is not installed. Failing package is: libmaxminddb-1.2.0-10.el8_9.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for qemu-guest-agent-6.2.0-40.module_el8.9.0+3714+46544554.2.x86_64.rpm is not installed. Failing package is: qemu-guest-agent-15:6.2.0-40.module_el8.9.0+3714+46544554.2.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for tcpdump-4.9.3-3.el8_9.1.alma.1.x86_64.rpm is not installed. Failing package is: tcpdump-14:4.9.3-3.el8_9.1.alma.1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: GPG check FAILED
I also had tried the Rocky one, there were no errors. but the issue was same with iptables. I couldnt enable them
You have an older AlmaLinux 8 image that doesn't have the updated GPG-KEY.
To fix that error, run
Code: [Select]
rpm --import https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinuxOr follow our instructions after a fresh install.
403
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 26, 2024, 04:25:04 PM »
On a Fresh install of AlmaLinux 8, here are the first step you Need to do:
Run the following:
Set timezime with:
Disable SELinux
Config Hostname & Hosts file
Then proceed to install CWP.
After installing CWP, upgrade MariaDB to latest LTS 10.11 following CWP Tutorial.
Config CSF, and start.
That's a clippet of our 9 page setup list for AlmaLinux 8 & CWP.
Run the following:
Code: [Select]
rpm --import https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux
dnf update ca-certificates
dnf install dnf-plugins-core
dnf config-manager --set-enabled powertools
dnf install elrepo-release epel-release -y
/usr/bin/crb enable
dnf install nano wget ipset ebtables iptables uuid uuid-devel libuuid-devel m4 pcre pcre-devel zlib-devel perl-DBD-MySQL perl-IPC-Cmd perl-Pod-Html libtool s-nail -y
dnf --refresh updateSet timezime with:
Code: [Select]
timedatectl set-timezone (your timezone here)
timedatectl set-local-rtc 0Disable SELinux
Config Hostname & Hosts file
Then proceed to install CWP.
After installing CWP, upgrade MariaDB to latest LTS 10.11 following CWP Tutorial.
Config CSF, and start.
That's a clippet of our 9 page setup list for AlmaLinux 8 & CWP.
404
Other / Re: cwp pro license keeps deactivating
« on: February 26, 2024, 10:48:37 AM »
The problem isn't the license, MariaDB 10.2 isn't supported any longer, and has been removed from the MariaDB mirrors.
You need to update MariaDB to at least 10.6, or the latest LTS of 10.11.
You need to update MariaDB to at least 10.6, or the latest LTS of 10.11.
405
SSL / Re: AutoSSL and Cloudflare
« on: February 26, 2024, 10:45:27 AM »
This is a Cloudflare issue.
But I would log into Cloudflare, look at all the SSL settings for the domain name that is working correctly, and mirror those setting to the 2nd.
More than likely you have Cloudflare handling the SSL somewhere.
But I would log into Cloudflare, look at all the SSL settings for the domain name that is working correctly, and mirror those setting to the 2nd.
More than likely you have Cloudflare handling the SSL somewhere.
