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.
316
Installation / Re: Install fresh or elevate to Alma 8?
« on: September 26, 2024, 03:09:44 PM »
I recommend to install a fresh server, configure it according to your requirements and then migrate all accounts from the old server to new.
If you upgrade your current server using "elevate" then some software requirements/dependencies could be unmet and it will fail the whole migration process. So if you want to upgrade using elevate then it is better to make backup/snapshot of the production server before upgrade.
If you upgrade your current server using "elevate" then some software requirements/dependencies could be unmet and it will fail the whole migration process. So if you want to upgrade using elevate then it is better to make backup/snapshot of the production server before upgrade.
318
PHP / Re: can't install new php version on PHP-FPM
« on: September 26, 2024, 09:48:14 AM »Do you have any solution for this issue?
It looks like the provided build log is incomplete. There are a lot of errors like "No such file or directory".
If you have similar problem then try to build/update PHP and then provide us with your build log.
319
CentOS 7 Problems / Re: module as crontab user does not work, it keeps loading
« on: September 26, 2024, 09:26:57 AM »
There is some problem associated with access permissions:
Try:
and then check if the problem remains. If it still exists then check logs again.
Code: [Select]
2024/09/25 09:27:17 [error] 28033#0: *12840 FastCGI sent in stderr: "PHP message: PHP Warning: fopen(/home/gente/cron): failed to open stream: Permission denied in /usr/local/cwpsrv/var/services/user_files/modules/crontab/index.php on line 0
Try:
Code: [Select]
chown gente.gente /home/gente/cron
chmod 660 /home/gente/cron
and then check if the problem remains. If it still exists then check logs again.
320
CentOS 7 Problems / Re: module as crontab user does not work, it keeps loading
« on: September 24, 2024, 06:38:48 PM »
Update CWP up to the latest stable version.
If the problem remains then look for errors in the file:
If the problem remains then look for errors in the file:
Code: [Select]
/usr/local/cwpsrv/logs/error_log
321
CentOS 8 Problems / Re: User with SSH can't run node commands on shell
« on: September 23, 2024, 08:50:08 PM »
Run:
in shell as the regular user and then:
If it work then just add:
into ~/.bashrc of the user (if the user uses bash)
Code: [Select]
export PATH=/opt/nvm/versions/node/vXX.XX.XX/bin:$PATH
in shell as the regular user and then:
Code: [Select]
/opt/nvm/versions/node/vXX.XX.XX/bin/npm
If it work then just add:
Code: [Select]
export PATH=/opt/nvm/versions/node/vXX.XX.XX/bin:$PATH
into ~/.bashrc of the user (if the user uses bash)
322
Postfix / Re: connection refused to a domain on another virtual machine
« on: September 23, 2024, 08:13:13 PM »
Check the mail logs to identify where your VM tries to connect to when you send emails from VM1 to VM2. Make sure the MX records of the recipient's domain directs emails to the correct host.
What does happen when you run
on the source mail host ?
What does happen when you run
Code: [Select]
telnet MX.HOST.COM 25
traceroute MX.HOST.COM
(MX.HOST.COM - mx record of the destination mail domain)on the source mail host ?
323
Other / Re: Nginx Varnish Apache php-fpm 403 Forbidden
« on: September 23, 2024, 10:10:10 AM »
All services (nginx, varnish and apache) are installed and running. Therefore you need to dig logs to identify why you get the error 403. I recommend you to do following:
1. Create some test .html file and place it in the document root of the website
2. Create a test script .php and place it in the document root of the website too
3. Try to open the .html file over http://domain.com/test.html
if there is no error then the problem is caused by Varnish or Apache. In other case it means access is blocked by Nginx (check logs to get more info about the problem, review the nginx config file of the virtual host)
Do step 4 if the step 3 was accomplished without the error.
4. Try to open the .php script over http://domain.com/test.php
and check the logs to get more info about the problem. Look for the records associated with your WAN IP and your test script.
1. Create some test .html file and place it in the document root of the website
2. Create a test script .php and place it in the document root of the website too
3. Try to open the .html file over http://domain.com/test.html
if there is no error then the problem is caused by Varnish or Apache. In other case it means access is blocked by Nginx (check logs to get more info about the problem, review the nginx config file of the virtual host)
Do step 4 if the step 3 was accomplished without the error.
4. Try to open the .php script over http://domain.com/test.php
and check the logs to get more info about the problem. Look for the records associated with your WAN IP and your test script.
324
Other / Re: Nginx Varnish Apache php-fpm 403 Forbidden
« on: September 21, 2024, 06:40:39 PM »
The error 403 appears when the webserver can't access the file on the server. It can be caused by access permissions, mod_security, etc. More detailed info about the problem the webserver puts into the error log file by default. If you get nothing then you look inside a wrong log file or something like that.
So I recommend you to make sure the error logging is enabled in Nginx, Varnish and Apache. Double check you look for the error in the correct error log file.
However, it isn't good way to solve any problems in attempt to guess because it takes time and could lead far away from the solution.
So I recommend you to make sure the error logging is enabled in Nginx, Varnish and Apache. Double check you look for the error in the correct error log file.
However, it isn't good way to solve any problems in attempt to guess because it takes time and could lead far away from the solution.
325
Other / Re: Nginx Varnish Apache php-fpm 403 Forbidden
« on: September 21, 2024, 07:15:53 AM »
I couldn't recreate the problem on my Almalinux 8 test box.
What errors do you get in the files:
when you try to access the site with enabled Nginx, Varnish, Apache ?
What errors do you get in the files:
Code: [Select]
/var/log/nginx/error.log
/usr/local/apache/domlogs/DOMAIN.error.log
when you try to access the site with enabled Nginx, Varnish, Apache ?
326
Other / Re: Nginx Varnish Apache php-fpm 403 Forbidden
« on: September 20, 2024, 07:46:34 PM »Quote
i goto SelectWebServer option under WebServer Settings menu and select Nginx & Varnish & Apache.
Why do you install Varnish manually after the webserver selection in CWP ?
I use AlmaLinux 8 and it installs Nginx, Varnish and Apache automatically.
Code: [Select]
# ps auxc | egrep "http|varn|nginx"
root 2768751 0.0 0.0 47424 1044 ? Ss 19:42 0:00 nginx
nobody 2768752 0.0 0.2 68876 5152 ? S 19:42 0:00 nginx
nobody 2768753 0.0 0.2 68568 4780 ? S 19:42 0:00 nginx
varnish 2768762 0.0 0.2 55600 5432 ? SLs 19:42 0:00 varnishd
varnish 2768821 0.0 4.2 280468 88952 ? SLl 19:42 0:00 cache-main
root 2769048 0.0 0.2 94748 5280 ? Ss 19:42 0:00 httpd
nobody 2769051 0.0 0.2 854512 5264 ? Sl 19:42 0:00 httpd
nobody 2769052 0.0 0.2 854512 5264 ? Sl 19:42 0:00 httpd
nobody 2769053 0.0 0.2 854512 5264 ? Sl 19:42 0:00 httpd
327
CentOS 8 Problems / Re: User with SSH can't run node commands on shell
« on: September 20, 2024, 06:55:14 PM »
Try:
Code: [Select]
/opt/nvm/versions/node/vXX.XX.XX/bin/npm
where vXX.XX.X is the version of nodejs you want to use (v14.15.3, v16.20.2, etc).
328
CentOS-WebPanel Bugs / Re: Latest CWP Almalinux 9 sept2024 fresh instal = amavis timeout + mariadb Vmem exc
« on: September 18, 2024, 09:53:48 PM »
OpenDKIM:
If it doesn't start automatically on boot then most likely it isn't configured to start automatically. Run:
and then check if it starts automatically after reboot.
Amavis:
Should be ok:
Just make sure postfix is configured to operate with amavis through 127.0.0.1.
If it doesn't start automatically on boot then most likely it isn't configured to start automatically. Run:
Code: [Select]
systemctl enable opendkim
and then check if it starts automatically after reboot.
Amavis:
Should be ok:
Code: [Select]
$inet_socket_bind = '127.0.0.1'
Just make sure postfix is configured to operate with amavis through 127.0.0.1.
329
Information / Re: Confused about listing domains
« on: September 18, 2024, 08:59:19 PM »
I think CWP was created like alternative to cPanel. You can see it in ports used by panels, features provided by CWP (cPanel to CWP migrations, etc), account structure, log files location, user level panel, etc.
Originally, cPanel divided domains to "main", "addon", "parked", "subdomains" and used different options to manage the domains. So I think CWP just copied the mechanism from cPanel. Now, cPanel tries to simplify the domain management and most likely we will see the changes in the future releases of CWP. Actually I see such changes in actual releases of CWP.
Originally, cPanel divided domains to "main", "addon", "parked", "subdomains" and used different options to manage the domains. So I think CWP just copied the mechanism from cPanel. Now, cPanel tries to simplify the domain management and most likely we will see the changes in the future releases of CWP. Actually I see such changes in actual releases of CWP.
330
Apache / Re: Create extra folder in home directory when creating users
« on: September 18, 2024, 08:26:52 PM »
Use CWP Account Hooks:
https://wiki.centos-webpanel.com/action-hooks
to create folders inside the account.
https://wiki.centos-webpanel.com/action-hooks
to create folders inside the account.