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.
1
PHP / Re: readline not being installed with the php compilation
« on: Today at 12:09:21 PM »
Try to install libedit, libedit-devel:
and then compile php again.
Code: [Select]
yum install libedit-devel libeditand then compile php again.
2
E-Mail / Re: We Cant verify that this email came from the sender so it might not be safe ...
« on: December 07, 2024, 10:26:42 PM »
Then install some SMTP plugin for Wordpress like "WordPress Mail SMTP" and configure it to send emails using SMTP with authorization.
3
Other / Re: CWP to CWP Website Migration - Unexpected Syncing Behavior
« on: December 06, 2024, 08:42:58 PM »
CWP doesn't have some option to sync user data between the servers automatically. It can be configured manually. Anyway, it is better to contact the guy who moved the data for you and ask if he enabled traffic forwarding or FS synchronization, etc.
4
E-Mail / Re: Box Trapper feature
« on: December 05, 2024, 06:21:07 AM »
Hi,
No, CWP doesn't have the option like "Box Trapper" in cPanel.
Please be aware, if you protect your email addresses by Box Trapper then spammers can collect valid email addresses of the domain. Additionally, your server/vps could be blacklisted if you get numerous spam emails from fake senders.
No, CWP doesn't have the option like "Box Trapper" in cPanel.
Please be aware, if you protect your email addresses by Box Trapper then spammers can collect valid email addresses of the domain. Additionally, your server/vps could be blacklisted if you get numerous spam emails from fake senders.
5
CentOS 8 Problems / Re: New Account Failed
« on: December 04, 2024, 04:31:13 PM »
The error says the home folder of the user you try to create exists (/home/USERNAME). It could happen of you created/removed users manually using useradd/userdel commands or created some folders inside /home/.
Make sure /home/USERNAME doesn't exist.
(USERNAME - username you try to create)
Make sure /home/USERNAME doesn't exist.
(USERNAME - username you try to create)
7
Updates / Re: How to update Imagick?
« on: December 01, 2024, 10:51:24 PM »8
Updates / Re: How to update Imagick?
« on: December 01, 2024, 07:12:25 PM »
Don't you get errors when you run `make` `make install` ?
If no errors then run:
You should get something like:
"No such file or directory"
then make sure all previous steps (see my first post in this thread) are completed without errors.
In other case run:
and check every file listed in output to make sure the path to imagick.so is specified correctly. There is just one record associated with imagick.so.
If no errors then run:
Code: [Select]
ls `php -i| grep "^extension_dir" |awk '{print $5}'`/imagick.so
You should get something like:
Code: [Select]
/usr/local/lib/php/extensions/no-debug-non-zts-xxxxxxxxx/imagick.soif you get:"No such file or directory"
then make sure all previous steps (see my first post in this thread) are completed without errors.
In other case run:
Code: [Select]
php --iniand check every file listed in output to make sure the path to imagick.so is specified correctly. There is just one record associated with imagick.so.
9
Updates / Re: How to update Imagick?
« on: December 01, 2024, 09:49:07 AM »Quote
-bash: cd: too many arguments
it seems you have two or more folders called like "imagick-something". That is why you get the error when run "cd imagick*"
Quote
-bash: cd: /opt/alt/phpXX/usr/bin/phpize: No such file or directory
overseer right. You just need to specify the correct location of php-config. Each php version has own "php-config". So if you want to build imagick for php 5.6 then run:
Code: [Select]
./configure --with-php-config=/opt/alt/php56/usr/bin/php-configfor php 7.1:
Code: [Select]
./configure --with-php-config=/opt/alt/php71/usr/bin/php-configetc, but for main php version:
Code: [Select]
./configure --with-php-config=/usr/local/bin/php-config
10
DNS / Re: name servers taken a while to update
« on: November 30, 2024, 10:06:10 PM »
Hi,
The DNS propagation process is fully automatic and it could take up to 72 hours to be finished.
According to whatsmydns.net your domains use the nameservers:
ns1.clickns.cloud
ns2.clickns.cloud
So it looks good for me.
The DNS propagation process is fully automatic and it could take up to 72 hours to be finished.
According to whatsmydns.net your domains use the nameservers:
ns1.clickns.cloud
ns2.clickns.cloud
So it looks good for me.
11
DNS / Re: named.service failed - NO DNS
« on: November 30, 2024, 01:47:15 PM »
Yes, you are right. The capital "R" supposed to be there. (Updated my previous post to reflect the changes).
Actually, overseer's guess was correct. He recommended to check the access permissions of the folders/files used by named. He made his guess based on the log records demonstrated by you:
The commands provided by me just set the correct access permission on the files and folders to make them available for named service.
I saw a few posts on this forum about wrong access permissions applied on the folder/files used by named and seems the problem appears once one or more accounts are transferred by the migration tool (cwp --> cwp, cpanel --> cwp).
Actually, overseer's guess was correct. He recommended to check the access permissions of the folders/files used by named. He made his guess based on the log records demonstrated by you:
Code: [Select]
Nov 30 08:24:43 svruk01.clickns.cloud named[1986]: could not configure root hints from 'named.ca': permission denied
Nov 30 08:24:43 svruk01.clickns.cloud named[1986]: loading configuration: permission denied
Nov 30 08:24:43 svruk01.clickns.cloud named[1986]: exiting (due to fatal error)
The commands provided by me just set the correct access permission on the files and folders to make them available for named service.
I saw a few posts on this forum about wrong access permissions applied on the folder/files used by named and seems the problem appears once one or more accounts are transferred by the migration tool (cwp --> cwp, cpanel --> cwp).
12
DNS / Re: named.service failed - NO DNS
« on: November 30, 2024, 12:46:14 PM »
Try:
then restart named and check if it works.
Code: [Select]
chmod 770 /var/named
chown root.named /var/named
chown root.named /var/named/named.*
chown -R named.named /var/named/data /var/named/dynamic /var/named/slaves
then restart named and check if it works.
13
DNS / Re: New IP (Rebuild Does Not Update)
« on: November 28, 2024, 09:19:03 AM »
Hi,
Please review this tutorial to learn how to change the IP address of the server properly:
https://forum.centos-webpanel.com/how-to/how-to-change-the-ip-address-of-a-server/
Please review this tutorial to learn how to change the IP address of the server properly:
https://forum.centos-webpanel.com/how-to/how-to-change-the-ip-address-of-a-server/
14
Nginx / Re: Nginx - one site will only go to default Server Test Page
« on: November 27, 2024, 07:51:45 AM »
Open the file:
/etc/nginx/nginx.conf
and make sure it contains the line at the end:
if the line is there then check content of the folder:
/etc/nginx/conf.d/
It should contain the file vhosts.conf. Open the file and check if it contains:
Then check the folder:
/etc/nginx/conf.d/vhosts/
It should contain two files named like domain.com.conf, domain.com.ssl.conf for each domain name.
Also, if you use nginx only, double check there are no some frozen apache/httpd processes.
/etc/nginx/nginx.conf
and make sure it contains the line at the end:
Code: [Select]
include /etc/nginx/conf.d/*.conf;if the line is there then check content of the folder:
/etc/nginx/conf.d/
It should contain the file vhosts.conf. Open the file and check if it contains:
Code: [Select]
include /etc/nginx/conf.d/vhosts/*.conf;Then check the folder:
/etc/nginx/conf.d/vhosts/
It should contain two files named like domain.com.conf, domain.com.ssl.conf for each domain name.
Also, if you use nginx only, double check there are no some frozen apache/httpd processes.
15
I can build it / Re: Apache Status - Accesses
« on: November 25, 2024, 04:24:51 PM »
Put the following content into the file:
/usr/local/apache/conf.d/remoteip.conf
Replace XXX.XXX.XXX.XXX with the main IP address of your server/VPS.
Please note it will show the real IP addresses of the visitors if some site is configured to be proxied via CloudFlare.
/usr/local/apache/conf.d/remoteip.conf
Code: [Select]
RemoteIPHeader X-Forwarded-For
RemoteIPProxiesHeader CF-Connecting-IP
RemoteIPInternalProxy 127.0.0.1 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 XXX.XXX.XXX.XXX
RemoteIPTrustedProxy 173.245.48.0/20
RemoteIPTrustedProxy 103.21.244.0/22
RemoteIPTrustedProxy 103.22.200.0/22
RemoteIPTrustedProxy 103.31.4.0/22
RemoteIPTrustedProxy 141.101.64.0/18
RemoteIPTrustedProxy 108.162.192.0/18
RemoteIPTrustedProxy 190.93.240.0/20
RemoteIPTrustedProxy 188.114.96.0/20
RemoteIPTrustedProxy 197.234.240.0/22
RemoteIPTrustedProxy 198.41.128.0/17
RemoteIPTrustedProxy 162.158.0.0/15
RemoteIPTrustedProxy 104.16.0.0/13
RemoteIPTrustedProxy 104.24.0.0/14
RemoteIPTrustedProxy 172.64.0.0/13
RemoteIPTrustedProxy 131.0.72.0/22
Replace XXX.XXX.XXX.XXX with the main IP address of your server/VPS.
Please note it will show the real IP addresses of the visitors if some site is configured to be proxied via CloudFlare.
