Recent Posts

1

CentOS-WebPanel GUI / Re: force webpanel:2087 to server hostname

« Last post by overseer on Today at 01:38:31 AM »

I wouldn't run the non-SSL version of the admin port (be it 2030 or 2086). Another unsolicited bit of advice: change to a non-standard port for the SSL admin port instead of 2031 or 2087. Here's a guide to do that:
https://azdigi.com/blog/en/webserver-panel-en/centos-web-panel-en/how-to-change-the-port-on-centos-web-panel-cwp/

As Cyberspace mentioned, if you use Cloudflare, you could use their infrastructure to create access rules to the admin port.

Alternately, you could firewall your connection to limit incoming access with CSF. Do you connect to it via static IP so you could lock it down to allow only a handful of chosen access IPs?

2

CentOS-WebPanel GUI / Re: force webpanel:2087 to server hostname

« Last post by kadybee on May 16, 2025, 11:43:04 PM »

You just can redirect the user to hostname.com if the user accesses the panel over the own domain name. To do this you need to add the rewerite rule into the files located in:
/usr/local/cwpsrv/conf.d/

I've tried all the versions of the rewrite rules to achieve that in there without success.  Will go back to it and try again.  Thanks

3

CentOS-WebPanel GUI / Re: force webpanel:2087 to server hostname

« Last post by kadybee on May 16, 2025, 11:38:01 PM »

Admin panel is 2087; user panel is 2083 (to match cPanel port assignments). Do you mean the admin or user panel?

Yes, the admin panel.
The 'issue' is this:  the server, correctly, responds on that port to any call via IP or virtual host DNS name;
It returns the usual 'not secured' SSL response in browsers;
click through and the header maintains the 'virtualhostname:2087';
They obviously don't have credentials to go further.

I've had enquiries relating around that from organisations who are taking out cyber insurance!  Their insurance companies seemingly scan all ports of their web site address and have come back with seeing 2086 and 2087 not secured on the vhost name and identify that as a threat to the insured's assets! 
We've had to explain realities of IP and DNS a few times now and I would just like to circumvent having to do that.

4

CentOS-WebPanel GUI / Re: force webpanel:2087 to server hostname

« Last post by cyberspace on May 16, 2025, 03:23:27 PM »

If the user's domain name is pointed to the server and there is no service like CouldFlare then there is no way to make the admin/user control panel become accessible via:
https://hostname.com:2087/
only.

You just can redirect the user to hostname.com if the user accesses the panel over the own domain name. To do this you need to add the rewerite rule into the files located in:
/usr/local/cwpsrv/conf.d/

5

CentOS-WebPanel GUI / Re: force webpanel:2087 to server hostname

« Last post by overseer on May 16, 2025, 02:25:10 PM »

Admin panel is 2087; user panel is 2083 (to match cPanel port assignments). Do you mean the admin or user panel?

6

Backup / backup notifications by email

« Last post by mason64 on May 16, 2025, 12:39:58 PM »

Good Day!

I am not sure if there is no feature  yet or if there is a way of doing this but when i create a backup say for 6pm a full backup daily which works great, i have the the option selected for when you finish home work it emails me every user that is backed up. if i have 50 accounts it will email be 50 times. Is there away to have email with a list of users that have been backed up or failed?

to give you an example:



also just for my old brain is this correct

When start and end task = emails me when the backup has started and finished

When Start Task = When the backup starts

When your finish home work = when the backup finishes

only when there are errors = Only if any errors happen.

To Whom i notify:

Account Owner = the email account attached to the user is emailed

To the server administrator = emails server admin that is setup in cwp

Other: State an email address to email

Thanks

7

CentOS-WebPanel GUI / force webpanel:2087 to server hostname

« Last post by kadybee on May 16, 2025, 07:41:32 AM »

I've been attempting to force the user web panel access on port 2087 to redirect or only respond to the server hostname - ie not <virtualhost>:2087

All the standard nginx ssl module redirect/rewrite tricks have failed me.  Has anyone achieved this?


Thanks,
Klaus

8

E-Mail / Re: Spamassassin Error: cannot create user preferences file //.spamassassin/user_pre

« Last post by Netino on May 15, 2025, 11:29:52 PM »

Run these commands:

Code: [Select]

# ls -alF /var/lib/spamassassin

Code: [Select]

# grep spamassassin /etc/postfix/master.cf | grep pipe | sed -r 's/^spamassassin.*pipe user=(\S+).*/\1/'
and post here.

Regards,
Netino

9

E-Mail / Re: Spamassassin Error: cannot create user preferences file //.spamassassin/user_pre

« Last post by setecabanas on May 15, 2025, 06:14:21 PM »

thanks

only 2 user have created this directory
iŽll try to create in all users

10

E-Mail / Re: Spamassassin Error: cannot create user preferences file //.spamassassin/user_pre

« Last post by overseer on May 15, 2025, 05:56:33 PM »

That said, your server will continue to function, but yes -- best to migrate to AlmaLinux 8 and then work toward upgrading to EL9.
Meanwhile, each user on your server should have a SpamAssassin user_prefs directory. Do you see that when you run:

Code: [Select]

ls -l /home/*/.spamassassin/user_prefsPer-user prefs are based on these templates:

Code: [Select]

/usr/share/spamassassin/user_prefs.template
/var/lib/spamassassin/3.004000/updates_spamassassin_org/user_prefs.template