Messages

1156

E-Mail / Re: Client host rejected: Access denied

« on: April 11, 2023, 02:16:10 AM »

The vanilla main.cf file leaves a lot to be desired -- much tweaking should be done to it for optimal delivery and UCE controls. But maybe too much to get into now for you if you just want to solve your more basic problem.

1157

Nginx / Re: All my site are now showing 502 Bad Gateway nginx/1.20.2

« on: April 11, 2023, 02:13:37 AM »

When compiling new php-fpm versions, you don't automatically get a user.conf file created (and therefore a user.sock file). You should copy over your existing user.conf from the previous PHP version, change the paths therein appropriately for that PHP version, and restart that version of php-fpm. Also, I see you are using php 8.0. Any specific reason you are not using 8.1 instead? If not, I would recommend compiling 8.1 and using that instead of 8.0.

1158

How to / Re: Upgrade PhpMyAdmin

« on: April 09, 2023, 03:02:08 PM »

And you can't login with your mysql root password? It should be the same credentials as are stored here:

Code: [Select]

/root/.my.cnf
/usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php

1159

Information / Re: License

« on: April 09, 2023, 09:05:20 AM »

It will revert back to the regular free version of CWP, which is in large part useless. Just pay the developers their few shekels and you will be (mostly) happy!

1160

How to / Re: Upgrade PhpMyAdmin

« on: April 09, 2023, 09:04:09 AM »

No, that's not true at all. I deployed the latest phpMyAdmin 5.2.1 yesterday on all my servers. Follow Sandeep's directions here, replacing any instance of "4.9.2" with "5.2.1":
https://www.uxlinux.com/how-to-update-phpmyadmin-latest-version-on-cwp-centos-webpanel/

Also, the link to the Blowfish hash generator is no longer working, so Google a different one.

1161

CWP API / Re: CWP API v1/admindomains added domain but domain unable to access

« on: April 08, 2023, 03:21:04 AM »

Are you creating DNS at the same time? Does the domain resolve properly?

1162

Postfix / Re: error on postfix rebuild

« on: April 08, 2023, 02:05:45 AM »

Yes, it's present on CWP CentOS systems:

Code: [Select]

[overseer@srv]$ ls -al /usr/bin/spfquery
-rwxr-xr-x. 1 root root 4598 Nov 10  2020 /usr/bin/spfquery
[overseer@srv]$ du -sh  /usr/bin/spfquery
8.0K /usr/bin/spfquerySo you would have to manually delete it or move it to the side before running the postfix rebuild routine.

1163

CentOS-WebPanel Bugs / Re: User php selector bug

« on: April 07, 2023, 08:16:08 AM »

And you reported the bug to the dev team? Or request support to help you with the issue?

1164

Apache / Re: apache strange behavior

« on: April 07, 2023, 07:59:20 AM »

Yes, it's normal:

Code: [Select]

ifconfig eth0or

Code: [Select]

ifconfig ens33Look for the "inet6" line.
and test via lsof:

Code: [Select]

[root@srv]# lsof -i :443
COMMAND    PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
httpd    15319 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    26197   root    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    26218 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    26219 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    26220 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    26310 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd    80303 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd   107496 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd   112527 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
httpd   128430 nobody    8u  IPv6 5287623      0t0  TCP *:https (LISTEN)
[root@srv]# lsof -i :80
COMMAND    PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
httpd    15319 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    26197   root    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    26218 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    26219 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    26220 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    26310 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd    80303 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd   107496 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd   112527 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
httpd   128430 nobody    4u  IPv6 5287612      0t0  TCP *:http (LISTEN)
If you would like to disable IPv6, add these lines to /etc/sysctl.conf

Code: [Select]

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1and run

Code: [Select]

sysctl -pThen confirm with:

Code: [Select]

ifconfig eth0or

Code: [Select]

ifconfig ens33

1165

MySQL / Re: 413 Request Entity Too Large by phpmyadmin

« on: April 06, 2023, 02:48:09 PM »

I haven't actually encountered this myself, probably because I use the CLI for larger DB loading & backup tasks. But thanks for resurfacing this thread! I'll enact it on my servers for the sake of clients who live & die by phpMyAdmin.

1166

E-Mail / Re: Imap Folders

« on: April 03, 2023, 02:03:52 PM »

Did you confirm that they don't actually exist on the server, or just not subscribed in your IMAP client?
Do you want them to be created for all users on the server, or is this a one-off for one user?

1167

MySQL / Re: MariaDB crashes after DC incident

« on: April 02, 2023, 09:47:51 PM »

This is the default example configuration of /etc/my.cnf provided by MySQL. This config file was generated by MySQL running on CentOS 7. I am running the same CentOS version as you are, but I am running MariaDB 10.6 (long term support release).

Code: [Select]

# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/8.0/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove the leading "# " to disable binary logging
# Binary logging captures changes between backups and is enabled by
# default. It's default setting is log_bin=binlog
# disable_log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
#
# Remove leading # to revert to previous value for default_authentication_plugin,
# this will increase compatibility with older clients. For background, see:
# https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_default_authentication_plugin
# default-authentication-plugin=mysql_native_password

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid


1168

MySQL / Re: MariaDB crashes after DC incident

« on: April 02, 2023, 02:42:06 PM »

Here is a lightly tuned my.cnf for general purpose CMS use (WordPress, Drupal, Joomla)

Code: [Select]

[mysqld]
performance-schema=0
max_connections=100
max_user_connections=75
query_cache_size=32M
skip-external-locking
key_buffer_size=32M
table_open_cache=128
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=16M
tmp_table_size=32M
max_heap_table_size=32M
thread_cache_size=4
open_files_limit=10000
local-infile=0
max_allowed_packet=500M

# InnoDB
innodb_file_per_table=1
innodb_locks_unsafe_for_binlog=1
innodb_fast_shutdown = 1
# Recovery mode options
#innodb_force_recovery = 5
#innodb_purge_threads=0

#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d

1169

MySQL / Re: MySQL - BAD CONFIGURATION DETECTED

« on: April 02, 2023, 02:39:46 PM »

Is that the default Fedora my.cnf?

Did you run mysql_secure_installation?

Here is a sample my.cnf, lightly tuned for WP and other CMS platforms:

Code: [Select]

[mysqld]
performance-schema=0
max_connections=100
max_user_connections=75
query_cache_size=32M
skip-external-locking
key_buffer_size=32M
table_open_cache=128
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=16M
innodb_file_per_table=1
tmp_table_size=32M
max_heap_table_size=32M
thread_cache_size=4
open_files_limit=10000
local-infile=0
max_allowed_packet=500M

# InnoDB
innodb_locks_unsafe_for_binlog=1
innodb_fast_shutdown = 1
# Recovery mode options
#innodb_force_recovery = 5
#innodb_purge_threads=0

#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d

1170

MySQL / Re: MariaDB crashes after DC incident

« on: April 02, 2023, 02:35:08 PM »

You need MariaDB stable in order to use the server -- CWP depends on it, the Postfix mail transport needs it, Roundcube webmail needs it, and WP and other dynamic sites depend on it.

Did the host add or remove something in /etc/my.cnf ?
Did you run mysql_secure_installation ?