Recent Posts

Pages: 1 ... 8 9 [10]
91
Addons / Re: Web Analytics for CWP
« Last post by Starburst on June 02, 2025, 07:16:56 PM »
That is because AlmaLinux is NOT Ubuntu.  ::)

If you look at the packages it installed, you overwrote some key packages, like Apache when you where trying to install Webalizer.

Running a server you need some experience, so you don't follow guides not for your OS.

Your best bet now is to do the 1 time support from CWP, and see if they can restore the server.
If not, hope you made a snapshot (which is always recommended, before making major changes) you can restore to.

Otherwise, you'll be rebuilding the server from scratch.
92
Addons / Re: Web Analytics for CWP
« Last post by DragoCom on June 02, 2025, 07:15:05 PM »
Also I just got an email that says this:

The following list of files have FAILED the md5sum comparison test. This means that the file has been changed in some way. This could be a result of an OS update or application upgrade. If the change is unexpected it should be investigated:

/usr/bin/goaccess: FAILED
/usr/bin/tcamgr: FAILED open or read
/usr/bin/tcamttest: FAILED open or read
/usr/bin/tcatest: FAILED open or read
/usr/bin/tcbmgr: FAILED open or read
/usr/bin/tcbmttest: FAILED open or read
/usr/bin/tcbtest: FAILED open or read
/usr/bin/tcfmgr: FAILED open or read
/usr/bin/tcfmttest: FAILED open or read
/usr/bin/tcftest: FAILED open or read
/usr/bin/tchmgr: FAILED open or read
/usr/bin/tchmttest: FAILED open or read
/usr/bin/tchtest: FAILED open or read
/usr/bin/tctmgr: FAILED open or read
/usr/bin/tctmttest: FAILED open or read
/usr/bin/tcttest: FAILED open or read
/usr/bin/tcucodec: FAILED open or read
/usr/bin/tcumttest: FAILED open or read
/usr/bin/tcutest: FAILED open or read
/bin/goaccess: FAILED
/bin/tcamgr: FAILED open or read
/bin/tcamttest: FAILED open or read
/bin/tcatest: FAILED open or read
/bin/tcbmgr: FAILED open or read
/bin/tcbmttest: FAILED open or read
/bin/tcbtest: FAILED open or read
/bin/tcfmgr: FAILED open or read
/bin/tcfmttest: FAILED open or read
/bin/tcftest: FAILED open or read
/bin/tchmgr: FAILED open or read
/bin/tchmttest: FAILED open or read
/bin/tchtest: FAILED open or read
/bin/tctmgr: FAILED open or read
/bin/tctmttest: FAILED open or read
/bin/tcttest: FAILED open or read
/bin/tcucodec: FAILED open or read
/bin/tcumttest: FAILED open or read
/bin/tcutest: FAILED open or read
93
Addons / Re: Web Analytics for CWP
« Last post by DragoCom on June 02, 2025, 07:14:07 PM »
So I removed (supposedly) webalizer using sudo yum remove webalizer but I still get 502 bad gateway:

[root@viking ~]# sudo yum remove webalizer
Dependencies resolved.
=========================================================================================================================================
 Package                                Architecture               Version                               Repository                 Size
=========================================================================================================================================
Removing:
 webalizer                              x86_64                     2.23_08-15.el8                        @epel                     360 k
Removing unused dependencies:
 GeoIP                                  x86_64                     1.6.12-7.el8                          @epel                     385 k
 GeoIP-GeoLite-data                     noarch                     2018.06-5.el8                         @epel                     1.2 M

Transaction Summary
=========================================================================================================================================
Remove  3 Packages

Freed space: 1.9 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                 1/1
  Erasing          : webalizer-2.23_08-15.el8.x86_64                                                                                 1/3
  Erasing          : GeoIP-1.6.12-7.el8.x86_64                                                                                       2/3
  Running scriptlet: GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         3/3
  Erasing          : GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         3/3
  Running scriptlet: GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         3/3
  Verifying        : GeoIP-1.6.12-7.el8.x86_64                                                                                       1/3
  Verifying        : GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         2/3
  Verifying        : webalizer-2.23_08-15.el8.x86_64                                                                                 3/3

Removed:
  GeoIP-1.6.12-7.el8.x86_64             GeoIP-GeoLite-data-2018.06-5.el8.noarch             webalizer-2.23_08-15.el8.x86_64           

Complete!
[root@viking ~]#
94
Addons / Re: Web Analytics for CWP
« Last post by DragoCom on June 02, 2025, 07:09:32 PM »
Ok just realized that since I did the goaccess update and the webalizer install that went whacky "ALL" my websites are coming uo 502 Bad Gateway, so basically my whole VPS is not showing sites uggggghhhh HELP!!!
95
Addons / Re: Web Analytics for CWP
« Last post by DragoCom on June 02, 2025, 06:55:44 PM »
I upgraded goaccess but I have always liked the way webalizer puts the stats out for you. So I tried installing it using this guide but changed apt-get to yum:

https://www.unixmen.com/install-and-configure-webalizer-on-ubuntu/


Doing so I got this as a result:

Install  7 Packages

Total download size: 2.4 M
Installed size: 6.6 M
Is this ok [y/N]: y
Downloading Packages:
(1/7): httpd-filesystem-2.4.37-65.module_el8.10.0+3966+b9483c84.3.noarch.rpm                             284 kB/s |  44 kB     00:00   
(2/7): almalinux-logos-httpd-84.5-1.el8.noarch.rpm                                                       140 kB/s |  29 kB     00:00   
(3/7): mod_http2-1.15.7-10.module_el8.10.0+3966+b9483c84.3.x86_64.rpm                                    470 kB/s | 155 kB     00:00   
(4/7): httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64.rpm                                        2.7 MB/s | 1.4 MB     00:00   
(5/7): GeoIP-1.6.12-7.el8.x86_64.rpm                                                                     239 kB/s | 124 kB     00:00   
(6/7): GeoIP-GeoLite-data-2018.06-5.el8.noarch.rpm                                                       1.2 MB/s | 552 kB     00:00   
(7/7): webalizer-2.23_08-15.el8.x86_64.rpm                                                               335 kB/s | 148 kB     00:00   
-----------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                    1.1 MB/s | 2.4 MB     00:02     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                 1/1
  Installing       : GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         1/7
  Installing       : GeoIP-1.6.12-7.el8.x86_64                                                                                       2/7
  Running scriptlet: httpd-filesystem-2.4.37-65.module_el8.10.0+3966+b9483c84.3.noarch                                               3/7
  Installing       : httpd-filesystem-2.4.37-65.module_el8.10.0+3966+b9483c84.3.noarch                                               3/7
  Installing       : almalinux-logos-httpd-84.5-1.el8.noarch                                                                         4/7
  Installing       : mod_http2-1.15.7-10.module_el8.10.0+3966+b9483c84.3.x86_64                                                      5/7
  Installing       : httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64                                                          6/7
warning: /etc/logrotate.d/httpd created as /etc/logrotate.d/httpd.rpmnew

  Running scriptlet: httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64                                                          6/7
  Running scriptlet: webalizer-2.23_08-15.el8.x86_64                                                                                 7/7
  Installing       : webalizer-2.23_08-15.el8.x86_64                                                                                 7/7
  Running scriptlet: GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         7/7
  Running scriptlet: httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64                                                          7/7
  Running scriptlet: webalizer-2.23_08-15.el8.x86_64                                                                                 7/7
  Verifying        : almalinux-logos-httpd-84.5-1.el8.noarch                                                                         1/7
  Verifying        : httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64                                                          2/7
  Verifying        : httpd-filesystem-2.4.37-65.module_el8.10.0+3966+b9483c84.3.noarch                                               3/7
  Verifying        : mod_http2-1.15.7-10.module_el8.10.0+3966+b9483c84.3.x86_64                                                      4/7
  Verifying        : GeoIP-1.6.12-7.el8.x86_64                                                                                       5/7
  Verifying        : GeoIP-GeoLite-data-2018.06-5.el8.noarch                                                                         6/7
  Verifying        : webalizer-2.23_08-15.el8.x86_64                                       

Installed:
  GeoIP-1.6.12-7.el8.x86_64                                              GeoIP-GeoLite-data-2018.06-5.el8.noarch                       
  almalinux-logos-httpd-84.5-1.el8.noarch                                httpd-2.4.37-65.module_el8.10.0+3966+b9483c84.3.x86_64         
  httpd-filesystem-2.4.37-65.module_el8.10.0+3966+b9483c84.3.noarch      mod_http2-1.15.7-10.module_el8.10.0+3966+b9483c84.3.x86_64     
  webalizer-2.23_08-15.el8.x86_64                                       

Complete!
[root@viking src]# sudo mv /var/www/webalizer /var/www/html/
mv: cannot stat '/var/www/webalizer': No such file or directory
[root@viking src]# sudo gedit /etc/webalizer/webalizer.conf
sudo: gedit: command not found
[root@viking src]# sudo nano /etc/webalizer/webalizer.conf
[root@viking src]# sudo webalizer
Error: Can't open log file /var/log/httpd/access_log
[root@viking src]#
96
MySQL / upgraded MariaDB, and to 10.11and does not recognize the database....
« Last post by venty on June 02, 2025, 06:18:25 PM »
Hi,

I used the instructions here:

https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/upgrade-mariadb-10-x-to-10-11-with-cwp-on-almalinux-9/

and upgraded MariaDB to 10.11....

Today, I had to create a new database with a user through the user panel. Everything went normally, but when I tried to use the database during WordPress installation, I encountered an error stating that it could not access the database.

I tested it several times, but it didn't work.. Then again, through the user panel, I "changed" the password of the database user (I copied and pasted the same one that I had set when creating the database), and everything worked - the WordPress installation accessed the database???

I haven't made any changes to the server, except that on 25.05 MariaDB was updated to 10.11.13 and I changed the root password.

When checking the status of the MySQL Database Server, I found the following entries:

Jun 02 20:59:19 hosting.mydomain.com mariadbd[1123]: 2025-06-02 20:59:19 682 [Warning] Aborted connection 682 to db: 'postfix' user: 'postfix' host: 'localhost' (Got an error reading communication packets)
Jun 02 21:03:04 hosting.mydomain.com  mariadbd[1123]: 2025-06-02 21:03:04 1234 [Warning] Aborted connection 1234 to db: 'postfix' user: 'postfix' host: 'localhost' (Got an error reading communication packets)
Jun 02 21:04:08 hosting.mydomain.com  mariadbd[1123]: 2025-06-02 21:04:08 1693 [Warning] Access denied for user 'hosmyd_k92test'@'localhost' (using password: YES)

Please help, what should I do?

BR
Venty

97
Installation / Re: AL10 Install Problem
« Last post by Starburst on June 02, 2025, 12:35:50 AM »
TBE -- to be expected. Some more transparency and communication from the devs would be very desirable and would assure other current & future customers. A roadmap, changelogs, a dev blog... anything would be good.

Agreed.
OpenSSL 3.x is already in AL8 & AL9.
Trying to Keep it backwards compatible to an EOL OS (CentOS 7) at this point isn't worth it, and is doing more harm.

And really EL8/AL8 is out of it development phase, and in it's security updates only phase.

There is a reason beta's are released, so programmers have time for updates, and not fall behind the 8.
98
Postfix / Re: Error found - Mail Server Manager
« Last post by overseer on June 01, 2025, 11:45:07 AM »
To further reduce spam, consider this stanza in main.cf:
Code: [Select]
smtpd_sender_restrictions =
        permit_mynetworks,
        permit_sasl_authenticated,
        check_sender_access pcre:/etc/postfix/reject_domains hash:/etc/postfix/sender_access,
        reject_unknown_sender_domain,
        reject_unknown_reverse_client_hostname,
        reject_unknown_client_hostname
99
Postfix / Error found - Mail Server Manager
« Last post by daowen on June 01, 2025, 09:39:15 AM »
Found the following issue when attempting to reduce spam:

rDNS Check (recommended): Drop all emails if no rDNS/PTR

When this option is checked, there should be a positive return running the following command:

Code: [Select]
postconf | grep reject_unknown_client_hostname
We should see this returned:

Code: [Select]
smtpd_client_restrictions = reject_unknown_client_hostname
Upon inspection, after selecting the option and rebuilding the mail server, it failed to change the one line in the main.cf file:

Code: [Select]
smtpd_client_restrictions = reject_unknown_client
Manually edited the file and injected the  "_hostname" to resolve.

100
CentOS 7 Problems / Re: PHPDefender permission denied
« Last post by overseer on June 01, 2025, 12:53:48 AM »
AI bot?
Pages: 1 ... 8 9 [10]