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 - aamirrajpoot

Pages: [1]
1
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 27, 2024, 09:32:08 AM »
I have followed what you mentioned here, and also updated the maria db to 10.11. Now firewall is starting fine.

I have started CWP->CWP migration and will test further.

Thank you

2
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 27, 2024, 06:40:14 AM »
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.

3
CentOS 8 Problems / Re: Centos 8 fresh install IP tables issue
« on: February 26, 2024, 03:10:51 PM »
following installation script, as soon as i run

Code: [Select]
yum -y update
I got these errors and I lost my interest in this one

Code: [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

4
CentOS 8 Problems / Centos 8 fresh install IP tables issue
« on: February 26, 2024, 01:07:25 PM »
I'm trying to turn on firewall but that is not working

Code: [Select]
Status: csf and lfd have been disabled, use 'csf -e' to enable
I checked the forms and looks like
Code: [Select]
iptables is not installed in the Fresh Installation. Then I installed iptables

Now, when I enable the firewall CWP stop responding and my sites start giving me 500 error. I did disabled using
Code: [Select]
csf -x which bring back the sites and CWP up.

How can I make this up. I had a server from 5 years back and it is now starting to act so doing a fresh clean install on different machine and migrating the content to new one.

5
PHP / Re: Install ImageMagick or GD ?
« on: May 21, 2021, 01:42:55 PM »
Wow so long, here is how I solved the issue,

Code: [Select]
yum -y install ImageMagick ImageMagick-devel ImageMagick-perl
cd /usr/local/src
rm -Rf imagick-3.4.4
rm -Rf imagick-3.4.4.tgz
wget http://pecl.php.net/get/imagick-3.4.4.tgz
tar zxf imagick-3.4.4.tgz
cd imagick-3.4.4
phpize
ln -s /usr/include/ImageMagick-6 /usr/local/include/ImageMagick

./configure --with-php-config=/opt/alt/php-fpm73/usr/bin/php-config
make clean
make
make install
echo ""
grep "imagick.so" /opt/alt/php-fpm73/usr/php/php.ini || echo "extension=imagick.so" >> /opt/alt/php-fpm73/usr/php/php.ini
php -m|grep imagick && echo "Imagick Installed, please restart apache to load changes !" || echo "Imagick NOT Installed !"

Notes:

1. I have used the latest version
2. In the scripts like `ln -s /usr/local/include/ImageMagick-6 /usr/local/include/ImageMagick` was wrong. I have fixed the paths

I have PHP-FPM Multiple versions installed and installed it to only PHP-FPM73

I hope this solves some users issues

6
CentOS-WebPanel Bugs / All accounts got suspended, Can access root
« on: February 15, 2019, 06:55:18 AM »
I have added couple of user accounts and everything working fine for past couple of months.

It happened that one of my client's domain expired and he moved it to his other server, but they were having issues there and asked me to redirect it back to my server. I had not removed their content so its a matter of changing DNS records only for domain. Which I did and their domain is back.

now I tried to login to their account, and I got message it is suspended,

I have performed following so far

1. Checked if user is suspended in Admin panel or not... it is not
2. Rebuild server configuration by going to CWP Side Bar-> CWP Settings -> Edit Settings -> Rebuild hosts files (checked) and saved
3. grep USERNAME /etc/shadow  and i see USERNAME:$ instead of USERNAME:!! so its correct here as well
4. Rebooted the server, didnt logged in.


Any how, i thought to delete and recreate the account, but before that I tried to login someother users and unfortunately all of my users are giving same error 'Account Suspended' So yeah i have not recreated that account yet, and came here for a solutions.


Thanks

7
CSF Firewall / Chat Application with port 8065 - IP not working
« on: January 02, 2019, 06:24:49 AM »
I have been struggling for couple of days that my chat application works only for 24 hours and then stops working. Then I realized that when I do login on CWP with root, my IP gets added in temporary list and chat app starts working. But users on other locations are still not able to connect.


Running Mattermost ( A clone of slack ) for a small team. It runs on port 8065. I have enabled this port in both TCP/UDP in/out sections.

I want it to accessible permanent from anywhere from any IP. Sometimes we do have to work from home and everyone can not have static IP.

Thank you

8
DNS / Re: Unable to start BIND DNS server
« on: December 26, 2018, 12:01:32 PM »
I am not sure which file to provide now, as bind dns is working at the moment. on the other hand I dont want to mess things up again :D

one thing I remember that when I provided MX record I provided TTL for that as well I think in Cache field. cant remember exactly, but when I added it manually, it didnt have TTL value. Shown above

9
DNS / Re: Unable to start BIND DNS server
« on: December 25, 2018, 07:41:12 PM »
Solved by going to Edit Nameservers IPs in DNS section and hit save button with both options selected.

After that edited the zone file for my domain and manually added

Code: [Select]
@ IN MX 1 ASPMX.L.GOOGLE.COM.
@ IN MX 5 ALT1.ASPMX.L.GOOGLE.COM.
@ IN MX 5 ALT2.ASPMX.L.GOOGLE.COM.
@ IN MX 10 ALT3.ASPMX.L.GOOGLE.COM.
@ IN MX 10 ALT4.ASPMX.L.GOOGLE.COM.

Looks everything is working now

10
DNS / Unable to start BIND DNS server
« on: December 25, 2018, 06:08:39 PM »
I am new to CWP and moved my all sites over. SSL applied and everything was working. for one domain I need to set MX record to google and i went to user account and added the MX record, it gave me error and after that my BIND DNS is not starting. I am getting error

Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.


Here is the log

Code: [Select]
systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2018-12-25 17:41:04 UTC; 16s ago
  Process: 18311 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)

Dec 25 17:41:04 server.aalasolutions.com bash[18311]: zone aalasolutions.com/IN: NS 'ns1.aalasolutions.com' has no address records (A or AAAA)
Dec 25 17:41:04 server.aalasolutions.com bash[18311]: zone aalasolutions.com/IN: NS 'ns2.aalasolutions.com' has no address records (A or AAAA)
Dec 25 17:41:04 server.aalasolutions.com bash[18311]: zone aalasolutions.com/IN: not loaded due to errors.
Dec 25 17:41:04 server.aalasolutions.com bash[18311]: _default/aalasolutions.com/IN: bad zone
Dec 25 17:41:04 server.aalasolutions.com bash[18311]: zone urdulook.info/IN: loaded serial 2018071600
Dec 25 17:41:04 server.aalasolutions.com bash[18311]: zone aala.pk/IN: loaded serial 2018071600
Dec 25 17:41:04 server.aalasolutions.com systemd[1]: named.service: control process exited, code=exited status=1
Dec 25 17:41:04 server.aalasolutions.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Dec 25 17:41:04 server.aalasolutions.com systemd[1]: Unit named.service entered failed state.
Dec 25 17:41:04 server.aalasolutions.com systemd[1]: named.service failed.

I tried to rebuild the DNS zone files from DNS section in Admin panel, no luck so far

11
CentOS-WebPanel Bugs / Re: AutoSSL not adding on www
« on: December 14, 2018, 03:26:12 PM »
You must remove the redirect from http to https before generating the Auto ssl, then you could place it again

Thanks @josemnunez, that was the issue.

For any one coming here or future me.

If wordpress is hosted on HTTPS first and then moved to CWP. need to change `siteurl` and `home` values to be without https in `wp_options` table. This will stop the redirect to https. Then generate the certificate.

It does solve my problem

12
CentOS-WebPanel Bugs / Re: AutoSSL not adding on www
« on: December 14, 2018, 02:32:08 PM »
I could see that SSL is properly installed on your website https://www.sslshopper.com/ssl-checker.html#hostname=pgrepublic.com

Are you using apache or any other webserver?

Try to restart apache to see the affect.

if you check https://www.sslshopper.com/ssl-checker.html#hostname=www.pgrepublic.com you will notice "None of the common names in the certificate match the name that was entered (www.pgrepublic.com). You may receive an error when accessing this site in a web browser."

13
CentOS-WebPanel Bugs / Re: AutoSSL not adding on www
« on: December 14, 2018, 02:20:41 PM »
I recently have transferred my domain to CWP and I am getting error .. NET::ERR_CERT_COMMON_NAME_INVALID

My domain is https://www.pgrepublic.com

If your htaccess redirect to www try to remove www and redirect to https://pgrepublic.com

Or simply add redirect on vhost :

Code: [Select]
<VirtualHost *:80>
ServerName www.example.com
Redirect / https://example.com/ <== add this line below ServerName
</VirtualHost>


I can try that, but this is not the solution to the problem. AutoSSL should generate for both pgrepublic.com and www.pgrepublic.com. Other thing is SEO and bank links which I am afraid of

14
CentOS-WebPanel Bugs / Re: AutoSSL not adding on www
« on: December 14, 2018, 02:16:39 PM »
I could see that SSL is properly installed on your website https://www.sslshopper.com/ssl-checker.html#hostname=pgrepublic.com

Are you using apache or any other webserver?

Try to restart apache to see the affect.

Yes I restarted the apache, even restarted whole server couple of times. No effect

15
CentOS-WebPanel Bugs / AutoSSL not adding on www
« on: December 14, 2018, 10:26:47 AM »
I recently have transferred my domain to CWP and I am getting error .. NET::ERR_CERT_COMMON_NAME_INVALID

My domain is https://www.pgrepublic.com

Pages: [1]