Messages

316

CentOS 8 Problems / Re: User with SSH can't run node commands on shell

« on: September 23, 2024, 08:50:08 PM »

Run:

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)

317

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

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 ?

318

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.

319

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.

320

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:

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 ?

321

Other / Re: Nginx Varnish Apache php-fpm 403 Forbidden

« on: September 20, 2024, 07:46:34 PM »

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


322

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/npmwhere vXX.XX.X is the version of nodejs you want to use (v14.15.3, v16.20.2, etc).

323

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:

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.

324

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.

325

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.

326

Information / Re: Confused about listing domains

« on: September 17, 2024, 08:38:14 PM »

The user level control panel shows the main domain name at Dashboard, see the section "Server Information".

If you want to get the list of the main domain names in terminal (shell) then run the script:

Code: [Select]

/scripts/list_usersor

Code: [Select]

echo "select username,domain from user;" | mysql root_cwpThe commands must be executed as root.

327

CentOS 9 Problems / Re: The mail-SSL doesn't work

« on: September 15, 2024, 10:02:03 PM »

I want to use SSL, with port 587.

1. Port 587: Short answer - STARTTLS. Read this:
https://en.wikipedia.org/wiki/Opportunistic_TLS

2. If you want to initiate SSL/TLS session explicitly then you need to use port 465.

3. If you want to do it over the port 587 then you have to reconfigure the mail server but it won't be the correct way.

CWP configures mail server correctly and provides correct mail settings in the user level control panel (see "Email accounts --> Email accounts")

328

CentOS 9 Problems / Re: The mail-SSL doesn't work

« on: September 15, 2024, 07:21:08 PM »

According to the provided log records there are no errors. The log records say the message from "

Code: [Select]

root@vmi1911643.contaboserver.net" was accepted and delivered to "

Code: [Select]

root@vmi1911643.contaboserver.net".

Your previous screeshot indicates you sends emails from the email address like "

Code: [Select]

noreply@...."

Send one more email using your application/script and then check logs again to be sure you check the correct mail records.

329

CentOS 9 Problems / Re: The mail-SSL doesn't work

« on: September 15, 2024, 06:29:25 PM »

You use port 587 (unsecure SMTP). So you need to disable "SSL" support in your mail application. The mail session will be secured automatically after the command "STARTTLS" (see logs).

In case you want to explicit TLS session. Then you need to use the port 465.

330

CentOS 9 Problems / Re: mod_security not allow to upload files

« on: September 15, 2024, 11:36:41 AM »

Make sure the rule is disabled, make a new attempt to upload the file and then check the error log file of the website:

Code: [Select]

/usr/local/apache/domlogs/domlogs/DOMAIN.COM.error_log
if the new attempt fails.