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.
436
CentOS-WebPanel Bugs / Re: IP Manager
« on: February 16, 2024, 10:58:49 PM »
IP Manager has been, and still is in beta.
At this point I wish they would just kinda remove it.
I think it use to use ifconfig, which now has been replaced by ip (e.g. ip addr), so I think it's completely broken at this point.
Best way to add IP's in AlmaLinux 8 is using nmtui.
Quick & easy, add, save, reboot, done.
At this point I wish they would just kinda remove it.
I think it use to use ifconfig, which now has been replaced by ip (e.g. ip addr), so I think it's completely broken at this point.
Best way to add IP's in AlmaLinux 8 is using nmtui.
Quick & easy, add, save, reboot, done.
437
E-Mail / Re: Can i find who the h3ll sends the spam?
« on: February 13, 2024, 05:43:46 PM »
You would only be stopping outgoing emails temporarily.
And can process the que after you find the spammer.
Otherwise you will have to sort thru the postfix logs.
You can find the Postfix logs at / var / log / maillog
(Remove the spaces to get into the folder, the forum blocks paths like this from being posted)
And can process the que after you find the spammer.
Otherwise you will have to sort thru the postfix logs.
You can find the Postfix logs at / var / log / maillog
(Remove the spaces to get into the folder, the forum blocks paths like this from being posted)
438
E-Mail / Re: Can i find who the h3ll sends the spam?
« on: February 13, 2024, 05:34:40 PM »
Do this just until you find out who the spammer is.
Under Service Config -> Startup Services, scroll down and find 'postfix.service', to the right click on Disable.
Then from your Dashboard, click on 'Mail Services', the click on 'STOP' next to Postfix Mail Server.
This will stop the SMTP server, and should stop any mail going out.
Under Service Config -> Startup Services, scroll down and find 'postfix.service', to the right click on Disable.
Then from your Dashboard, click on 'Mail Services', the click on 'STOP' next to Postfix Mail Server.
This will stop the SMTP server, and should stop any mail going out.
439
E-Mail / Re: Can i find who the h3ll sends the spam?
« on: February 13, 2024, 05:11:53 PM »
Disable Postfix temporarily, and let the queue build up, and look at what emails are going out, and from who.
440
CentOS 7 Problems / Re: They disabled my cwp even though it was paid
« on: February 13, 2024, 05:10:15 PM »
PM your server IP, I'll add it to our reseller license so we can get your sites back online.
But it sounds you might need to check your firewall first to see if the country or IP is blocked.
But it sounds you might need to check your firewall first to see if the country or IP is blocked.
441
Installation / Re: EOL: CentoS 7 - June 30, 2024, AlmaLinux 8 - 01 May 2024
« on: February 08, 2024, 12:11:35 PM »
CWP isn't supported on AlmaLinux 9, yet.
AlmaLinux 8.x EOL isn't until 2029
per: https://wiki.almalinux.org/FAQ.html
AlmaLinux 9.x isn't far behind at 2032
So you are good setting up a AlmaLinux 8.x server with CWP.
And at this point I'm guessing CWP might leapfrog 9 to the next version, kinda like what ionCube did with PHP 8.0.
Then there is TuxCare, who for a monthly fee will do extended support.
AlmaLinux 8.x EOL isn't until 2029
per: https://wiki.almalinux.org/FAQ.html
AlmaLinux 9.x isn't far behind at 2032
So you are good setting up a AlmaLinux 8.x server with CWP.
And at this point I'm guessing CWP might leapfrog 9 to the next version, kinda like what ionCube did with PHP 8.0.
Then there is TuxCare, who for a monthly fee will do extended support.
442
Updates / Re: 0.9.8.1175 changes?
« on: February 08, 2024, 12:04:46 PM »
Just saw that also.
Must just be bug fixes.
PHP 8.2.15 & 8.3.2 are both missing, and both came out on 2024-01-18
Must just be bug fixes.
PHP 8.2.15 & 8.3.2 are both missing, and both came out on 2024-01-18
443
CentOS-WebPanel GUI / Re: How to (steps) to increase GUI performance?
« on: February 06, 2024, 05:47:18 PM »
It's not recommended to mess with the internal cwpsrv PHP as @overseer mentioned.
If you break it, the whole server will crap out, and you might have to reinstall it from scratch.
Not worth the risk.
If you break it, the whole server will crap out, and you might have to reinstall it from scratch.
Not worth the risk.
444
SSL / Re: Problem with auto SSL
« on: February 06, 2024, 03:35:47 PM »
When I run a SSL check on the hostname: cwp02.ht.inf.br
On 1 test I get:
None of the common names in the certificate match the name that was entered (cwp02.ht.inf.br). You may receive an error when accessing this site in a web browser. Learn more about name mismatch errors.
The certificate comes back to abaelevadores.com.br
So there is clearly a misconfiguration with the hostname, the hostname should be only going to 1 IP address, the base IP.
You have it going to 2 different IP's for some reason. 198.49.71.199 & .200.
That is not the correct way to setup the hostname IP.
The correct way to setup the hostname, would create the subdomain, like you did, point it to 1 IP, which will be your servers base IP.
Create the rDNS at the upstream, and then create the hostname SSL.
Now if you want to do 2 DNS servers, and example would be:
dns1.ht.inf.br 198.49.71.199
dns2.ht.inf.br 198.49.71.200
of course you couldn't create a rDNS for .199, since it's already pointing to the hostname. But that is a minor issue, that really shouldn't affect anything.
From the looks of it, .200 is your base IP, and you have .199 setup as your shared IP.
If that is so, remove the DNS & rDNS entries for cwp02.ht.inf.br that points to .199, and do the certificates over.
You will also have to look at how your host file is setup.
On 1 test I get:
None of the common names in the certificate match the name that was entered (cwp02.ht.inf.br). You may receive an error when accessing this site in a web browser. Learn more about name mismatch errors.
The certificate comes back to abaelevadores.com.br
So there is clearly a misconfiguration with the hostname, the hostname should be only going to 1 IP address, the base IP.
You have it going to 2 different IP's for some reason. 198.49.71.199 & .200.
That is not the correct way to setup the hostname IP.
The correct way to setup the hostname, would create the subdomain, like you did, point it to 1 IP, which will be your servers base IP.
Create the rDNS at the upstream, and then create the hostname SSL.
Now if you want to do 2 DNS servers, and example would be:
dns1.ht.inf.br 198.49.71.199
dns2.ht.inf.br 198.49.71.200
of course you couldn't create a rDNS for .199, since it's already pointing to the hostname. But that is a minor issue, that really shouldn't affect anything.
From the looks of it, .200 is your base IP, and you have .199 setup as your shared IP.
If that is so, remove the DNS & rDNS entries for cwp02.ht.inf.br that points to .199, and do the certificates over.
You will also have to look at how your host file is setup.
445
SSL / Re: Problem with auto SSL
« on: February 06, 2024, 01:21:38 PM »
Go to your providers and get your rDNS for the hostname fixed, then generate that certificate.
This isn't handled by your DNS.
I think that's the root cause of your problems.
What is the hostname?, and I can check that in a little while.
This isn't handled by your DNS.
I think that's the root cause of your problems.
What is the hostname?, and I can check that in a little while.
446
CentOS 7 Problems / Re: Database not showing for users
« on: February 06, 2024, 12:33:59 PM »
Under SQL Services -> MySQL Manager
Does it show the database and the correct associated database users?
If it does, login via the user control panel link next to the user name under User Accounts -> List Accounts
Let me know what you see.
Does it show the database and the correct associated database users?
If it does, login via the user control panel link next to the user name under User Accounts -> List Accounts
Let me know what you see.
447
PHP / Re: Xdebug on php-fpm enabled but not work
« on: February 06, 2024, 12:26:55 PM »
Should be as simple as selecting that option in PHP-FPM, saving the custom config, and then rebuilding.
Can you please advise of the following:
What 'errors' and/or 'messages' are being displayed?
What distro are you using?
Can you please advise of the following:
What 'errors' and/or 'messages' are being displayed?
What distro are you using?
448
SSL / Re: Problem with auto SSL
« on: February 06, 2024, 12:23:29 PM »
Try this:
Under WebServer Settings -> SSL Certificates, remove all the certificates.
(Tests show a valid certificate for domain, but not hostname)
https://www.hardenize.com/report/casaautomacao.com.br/1707220320#www_certs
https://www.sslcerty.com/certificate?h=casaautomacao.com.br%3A443
https://www.geocerts.com/ssl-checker
https://www.ssllabs.com/ssltest/analyze.html?d=casaautomacao.com.br
The hostname/server name should not be your main domain name, but a subdomain like srv1.domain.com (I'll use this as an example below)
Then under the CLI run:
/root/.acme.sh/acme.sh --set-default-chain --preferred-chain "ISRG Root X1"
Then back to the admin interface, under Server Settings -> Change Hostname
It should show (Should show your sub-domainname for server here):
Your Hostname is: srv1.domain.com
rDNS/PTR = srv1.domain.com [SUCCESS]
Click on the Blue Bar if everything is OK, and wait a few seconds.
Then log out, and close that browser window.
Re-login to the admin console at https://srv1.domain.com:2031/login/index.php
You should show the page as being secure.
No go back under WebServer Settings -> SSL Certificates and generate a new Free certificate for the domain, and the test links above should all be green, with no problems showing a certificate mismatch.
Let me know.
Under WebServer Settings -> SSL Certificates, remove all the certificates.
(Tests show a valid certificate for domain, but not hostname)
https://www.hardenize.com/report/casaautomacao.com.br/1707220320#www_certs
https://www.sslcerty.com/certificate?h=casaautomacao.com.br%3A443
https://www.geocerts.com/ssl-checker
https://www.ssllabs.com/ssltest/analyze.html?d=casaautomacao.com.br
The hostname/server name should not be your main domain name, but a subdomain like srv1.domain.com (I'll use this as an example below)
Then under the CLI run:
/root/.acme.sh/acme.sh --set-default-chain --preferred-chain "ISRG Root X1"
Then back to the admin interface, under Server Settings -> Change Hostname
It should show (Should show your sub-domainname for server here):
Your Hostname is: srv1.domain.com
rDNS/PTR = srv1.domain.com [SUCCESS]
Click on the Blue Bar if everything is OK, and wait a few seconds.
Then log out, and close that browser window.
Re-login to the admin console at https://srv1.domain.com:2031/login/index.php
You should show the page as being secure.
No go back under WebServer Settings -> SSL Certificates and generate a new Free certificate for the domain, and the test links above should all be green, with no problems showing a certificate mismatch.
Let me know.
449
SSL / Re: Problem with auto SSL
« on: February 05, 2024, 07:19:02 PM »
Would need the actual domain name to do some remote testing for you.
What you posted doesn't look fully generated from CWP. As there is no directory /usr/local/apache/domain.logs.
/usr/local/apache isn't even used for domains or SSL certificates.
The certificate name also has the wrong extension than what CWP uses.
Is this a public IP VPS/Dedicated server or NAT?
How was this certificate supposedly generated?
What does it show under WebServer Settings -> SSL Certificates under the 'Signed' column?
Maybe do a screenshot of that and post also.
What you posted doesn't look fully generated from CWP. As there is no directory /usr/local/apache/domain.logs.
/usr/local/apache isn't even used for domains or SSL certificates.
The certificate name also has the wrong extension than what CWP uses.
Is this a public IP VPS/Dedicated server or NAT?
How was this certificate supposedly generated?
What does it show under WebServer Settings -> SSL Certificates under the 'Signed' column?
Maybe do a screenshot of that and post also.
450
Information / Re: Roundcube big security issue.
« on: February 05, 2024, 03:41:30 AM »
@Vinayak If you haven't updated your AlmaLinux servers in awhile, you had mentioned 8.8.
You will need to install the new AlmaLinux GPG Keys first: https://almalinux.org/blog/2023-12-20-almalinux-8-key-update/
You will need to install the new AlmaLinux GPG Keys first: https://almalinux.org/blog/2023-12-20-almalinux-8-key-update/
