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.
1186
E-Mail / Re: No send and Receibe Emails...
« on: March 04, 2023, 07:04:31 AM »
You've rebuilt the mail server? Is DNS set up and tested as working? rDNS in place? MX records? SPF TXT records?
1187
PHP / Re: When PHP 8.2 will be available?
« on: March 04, 2023, 07:01:46 AM »
I guess the better question is, when will CWP run on PHP 8.1 instead of the obsolete, EOL PHP 7.1/7.2?
1188
Information / Re: Cluster CWP (Multi-Server Manager) Availability
« on: March 04, 2023, 06:59:19 AM »
Are there any details of this feature documented anywhere? At this point I've adapted to managing my servers with tab groups in a Chromium-based browser and Royal TSX has one-stop management features that get the job done. Cockpit also promises to roll up multi-server management in one location. So I don't necessarily need it, but you have piqued my curiosity...
1189
Installation / Re: wordpress
« on: March 04, 2023, 06:47:14 AM »
Did you check the access and error logs?
Did you fix permissions on the user account?
Did you fix permissions on the user account?
1190
Information / Re: Change IP Public but at CWP Client list not changing
« on: March 04, 2023, 06:45:54 AM »
In phpMyAdmin, edit the root_cwp database. Edit the user table, ip_address column. I've seen this on VMs that I have moved from one physical IP address to another. I don't know that it's more than a cosmetic issue, as it doesn't seem to affect the vhosts (of course, change those IP references, too):
Code: [Select]
perl -pi -e 's/OLDIPADDRESS/NEWIPADDRESS/g' /usr/local/apache/conf.d/vhosts/*.conf
1191
CentOS-WebPanel GUI / Re: Monthly website statistics not working
« on: March 03, 2023, 06:41:03 AM »
Confirmed; please fix!
1192
Migration from other control panels / Re: cwp-cwp migration Connection not reached The following error occurred
« on: March 03, 2023, 06:30:52 AM »
Duplicate posted in case it helps someone in the future:
For 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 this work. Actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution to the failed connection errors:
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.
For 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 this work. Actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution to the failed connection errors:
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.
1193
Migration from other control panels / Re: cwp-cwp migration Connection not reached The following error occurred
« on: March 03, 2023, 06:25:47 AM »on new server copy Public Key from: # cat /root/.ssh/id_rsa.pubAnd to be clear, this had no bearing on my connection difficulties. I already had my SSH key pair in place and it was in the authorized_keys, so that was not the issue. I too experienced the "Connection not reached - the following error occurred" error message before running down my solution list. (For sure, it was the standing on the head part that solved it...)
and paste Public key to Old server: # nano /root/.ssh/authorized_keys
1194
Information / Re: need help cwp-->cwp
« on: March 03, 2023, 05:26:56 AM »
I am going to duplicate post this solution here, in case it helps someone searching for the answer.
In order to succeed at a 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 this work. Actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution:
Disable the firewall (CSF & LDF) on both origin and receiving 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 sshd, reset the r00t passphrase to strong ones, and re-enable the firewalls.
In order to succeed at a 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 this work. Actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution:
Disable the firewall (CSF & LDF) on both origin and receiving 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 sshd, reset the r00t passphrase to strong ones, and re-enable the firewalls.
1195
Migration from other control panels / Re: cwp-cwp migration Connection not reached The following error occurred
« on: March 03, 2023, 05:16:22 AM »
You have to stand on your head, pat your belly, and rub your feet at the same time in order to make this work. Actually, I just had the opportunity to do a CWP -> CWP migration, so here was my solution:
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, reset the r00t passphrase 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, reset the r00t passphrase to strong ones, and re-enable the firewalls.
1196
Backup / Re: New Backup Error
« on: February 13, 2023, 09:46:17 AM »
Not to be snarky, but the New Backup is labeled as "beta" for a reason... I would expect to encounter some bugs along the way until it is fully shaken out!
1197
E-Mail / Re: SMTP Error 451
« on: February 13, 2023, 09:31:28 AM »
You can set message throughput limits under the Packages > Packages menu item (don't you love the redundancy there?).
It is set under the Hourly Emails setting.
It is set under the Hourly Emails setting.
1198
E-Mail / Re: I can rececive emails, but cannot send any emails
« on: February 13, 2023, 09:27:04 AM »
I can confirm (testing against 3 CWP servers) that an nmap ping probe (example above) will not set off the CSF firewall. You won't block yourself by doing so.
Code: [Select]
localhost$ nmap -P0 yourserver.com
Starting Nmap 7.93 ( https://nmap.org ) at 2023-02-13 02:20 MST
Nmap scan report for yourserver.com (111.111.111.111)
Host is up (0.075s latency).
Not shown: 982 closed tcp ports (conn-refused)
PORT STATE SERVICE
25/tcp filtered smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
135/tcp filtered msrpc
139/tcp filtered netbios-ssn
143/tcp open imap
443/tcp open https
445/tcp filtered microsoft-ds
465/tcp open smtps
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s
2031/tcp open device2
3306/tcp open mysql
8888/tcp open sun-answerbook
1199
Other / Re: How to protect my files against download
« on: February 13, 2023, 09:12:42 AM »
curl and wget can get a lot, and many offline web readers can suck down a whole site and localize the HTML. So not much you can do about it.
1200
Installation / Re: Thunderbird problem
« on: February 13, 2023, 09:10:59 AM »
Funny thing is that I've seen countless T-Bird IMAP bugs over the years. And yet, Postbox (a commercial Thunderbird derivative, still using the T-Bird mail engine) seems to have fixed those IMAP errors! I never encounter any when I use Postbox, and having bought a lifetime license years ago, I get all updates that have been released. It offers a lot more spit-n-polish than the default T-bird experience.
