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.
961
Installation / Re: mail server only
« on: March 07, 2023, 03:27:58 PM »
From my experience, a valid FQDN and rDNS are the paramount factors for mail delivery, as well as proper SPF records. DKIM is spottily applied out there and not as well understood, so it doesn't tend to be a make-or-break factor for successful delivery. But if your mail server is on a dynamically assigned IP block, you will tend to be blocked by various DNSBL, so hopefully you are looking to do this on a static IP address and can get rDNS assigned by your provider.
962
CentOS 7 Problems / Re: Migration CWP -> CWP doesn't work...
« on: March 07, 2023, 03:24:56 AM »
Sometimes the little things are the ones that get you! Stumped by some niggling detail until you realize what you missed, after staring at it for far too long!
963
Installation / Re: mail server only
« on: March 07, 2023, 03:23:15 AM »
You can, for sure run a mail-only server. Probably the easiest thing would be to only allow the mail ports with CSF -- 25,465,587,110,143,993,995, as well as SSH and CWP ports. Don't allow any other standard ports (FTP, HTTP, HTTPS, etc.). And you could disable other services permanently so nothing auto-starts with the server.
And as you said, configure DNS appropriately and the MX and SPF records and you should be good.
And as you said, configure DNS appropriately and the MX and SPF records and you should be good.
964
Information / Re: CentOS Configuration File Locations (CWP)
« on: March 07, 2023, 03:15:58 AM »
Sorry, but I trust my own methods and intuition for customization over CWP's automated & buggy toolset. Hopefully it will improve with time, but I feel it to be beta quality at its current level.
965
Apache / Re: I am thinking of using mod pagespeed in Apache. Do you think it's a good idea?
« on: March 06, 2023, 07:11:30 AM »
Living up to your name, eh?
966
Apache / Re: Not all sites (Wordpress) are accessible
« on: March 06, 2023, 07:09:47 AM »
CWP tries to be all / do all and fit most use cases. I think if you want max performance for the least effort, Nginx has proven to be the best for me on one heavy server. To ABSOLUTELY milk the most out of a particular server hardware, you would want to add Varnish into the mix (if you have fast storage and/or gobs of RAM). But bang for your buck is definitely in the Nginx side of things.
https://kinsta.com/blog/nginx-vs-apache/
https://kinsta.com/blog/nginx-vs-apache/
967
Information / Re: CentOS Configuration File Locations (CWP)
« on: March 06, 2023, 07:01:20 AM »
That's a pretty vast question... I built my first CWP server and muddled around with the configs for roughly 2 weeks until I got things to a workable, satisfied state. It actually wasn't too bad because my years of cPanel experienced gave me a good reference point. Then I was able to build 2 more CWP servers in a matter of a few hours once that initial learning curve had been done. And then I was able to shuffle some accounts back & forth between them to better load balance and take advantage of more resources on one server.
968
CentOS 8 Problems / Re: How to install docker on cwp?
« on: March 06, 2023, 06:56:29 AM »
Agreed, it's beyond a LAMP/LEMP stack + administration & user control panel -- that is what CWP is, so best to look elsewhere for a Docker platform.
969
CentOS 8 Problems / Re: the cwp dosnt recive emails
« on: March 06, 2023, 06:55:00 AM »
Check your server's reputation with a multi-RBL checking service:
https://multirbl.valli.org
https://multirbl.valli.org
970
CentOS 8 Problems / Re: nginx won't start after server reboot
« on: March 06, 2023, 06:52:11 AM »
But did you fix this problem:
Running CentOS 8 Stream with latest CWP Control Panel software.
971
Information / Re: Cluster CWP (Multi-Server Manager) Availability
« on: March 06, 2023, 06:50:04 AM »
Sing it with me now:
99 bugs in the code...
You take one down, patch it up...
108 bugs in the code...
99 bugs in the code...
You take one down, patch it up...
108 bugs in the code...
972
Installation / Re: AlmaLinux
« on: March 06, 2023, 06:48:16 AM »@overseer nagging doesn't always work.I meant to nag a customer that won't upgrade their site. I do have some sway there, as I could force the issue, offer to help them upgrade, or threaten to drop them if they don't get onto this decade...
But yeah, not sure that nagging is going to get the CWP gears to move any faster or differently than they are...
974
Migration from other control panels / Re: BUG migration from CPanel
« on: March 06, 2023, 06:43:33 AM »
That script was done during the COVID quarantine lockdown in 2020. I took the opportunity to migrate all my cPanel servers to CWP 
I reported the bugs I encountered and submitted the script to the dev team, so hopefully they applied some of that to the migration script.
Yes, the vps1.domain.com was an old hostname from cPanel. Funny, I had stepped from regular hosting, to VPS, to advanced dedicated, then stepped down to dedicated, then down to a high end VPS at the end of my cPanel time. So I had about 5 mixed hostnames in the cur directories, so I wanted to normalize them on the new server under CWP. So I only showed one example in the posted script. In reality I had 5 hostnames to contend with!
I reported the bugs I encountered and submitted the script to the dev team, so hopefully they applied some of that to the migration script.
Yes, the vps1.domain.com was an old hostname from cPanel. Funny, I had stepped from regular hosting, to VPS, to advanced dedicated, then stepped down to dedicated, then down to a high end VPS at the end of my cPanel time. So I had about 5 mixed hostnames in the cur directories, so I wanted to normalize them on the new server under CWP. So I only showed one example in the posted script. In reality I had 5 hostnames to contend with!
975
CentOS 7 Problems / Re: Migration CWP -> CWP doesn't work...
« on: March 06, 2023, 06:38:46 AM »
For a successful CWP -> CWP Migration, you have to stand on your head, pat your belly, and rub your feet at the same time in order to make it work. But actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution to the various unhelpful errors (such as for API TOKEN):
Disable the firewall (CSF & LDF) on both servers.
On both servers, reset the r00t password to be 8 characters or fewer.
In
On the receiving server, use the interface in User Accounts > CWP->CWP Migration.
After successfully migrating the accounts, revert all changes to your SSH configuration, restart the ssh daemon, reset the r00t passphrases to strong ones, and re-enable the firewalls.
Disable the firewall (CSF & LDF) on both servers.
On both servers, reset the r00t password to be 8 characters or fewer.
In
Code: [Select]
/etc/ssh/sshd_config set: Code: [Select]
PermitRootLogin yes
StrictModes noRestart sshd:Code: [Select]
service sshd restartOn the source server, set up the API key (CWP Settings > API Manager) for CWP Migration using the default CWP template.On the receiving server, use the interface in User Accounts > CWP->CWP Migration.
After successfully migrating the accounts, revert all changes to your SSH configuration, restart the ssh daemon, reset the r00t passphrases to strong ones, and re-enable the firewalls.
