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.
211
Installation / Re: Try Install 8 and 9 all stuck in middlle
« on: July 16, 2024, 02:05:10 PM »
Do you have a screenshot of where it locks up at?
Or is this a local box?
Or is this a local box?
212
Installation / Re: Request for CWP Virtual Machine
« on: July 16, 2024, 02:01:57 PM »
Your best bet is to use Proxmox with AlmaLinux 8, and then do a regular install of CWP.
213
Other / Re: Hide Server IP
« on: July 15, 2024, 10:20:13 PM »
Block those ports (2030, 2031, 2086 & 2087) in CSF.
Just remember to whitelist your IP, so you don't get locked out.
If everything was setup in CWP, you should be able to access domainname.com:2083
2082 CWP User Panel
2083 CWP User panel SSL
Just remember to whitelist your IP, so you don't get locked out.
If everything was setup in CWP, you should be able to access domainname.com:2083
2082 CWP User Panel
2083 CWP User panel SSL
214
CentOS-WebPanel Bugs / Re: Problem in rebooting the server
« on: July 15, 2024, 10:14:08 PM »
I've seen this is the server wasn't a virgin, aka Apache, PHP, etc. where already loaded.
And then CWP gets confused.
Was this on a VPS or Dedicated?
Local or Remote?
Do you have console access?
If so, what does it show on boot?
And then CWP gets confused.
Was this on a VPS or Dedicated?
Local or Remote?
Do you have console access?
If so, what does it show on boot?
215
SSL / Re: Domain works on SSL but not the ports
« on: July 14, 2024, 09:11:42 PM »
That is good news.
Just stay away from the CLI, it's amazing how fast that can corrupt a server sometimes.
Having a test box also helps, that way if it gets messed up, you just wipe it.
Just stay away from the CLI, it's amazing how fast that can corrupt a server sometimes.
Having a test box also helps, that way if it gets messed up, you just wipe it.
216
Other / Re: Hide Server IP
« on: July 14, 2024, 09:08:38 PM »
No, if they lookup your domain name, it will point to Cloudflare, hence it's proxy service IP will show.
But if someone scans the whole IP range, then yes, your server will probably acknowledge.
That is the curse of a Public IP.
You can secure what ports a scan might find open.
But as @overseer mentioned, sound like you might be doing something darkweb'ish not wanting your IP to show at all, which again, is impossible.
But if someone scans the whole IP range, then yes, your server will probably acknowledge.
That is the curse of a Public IP.
You can secure what ports a scan might find open.
But as @overseer mentioned, sound like you might be doing something darkweb'ish not wanting your IP to show at all, which again, is impossible.
217
Information / Re: security updates and 2fa
« on: July 14, 2024, 09:05:39 PM »@starbust I was looking in to that but wanted to stay within the admin cpanel I was absolutely portable not complete completely with CSF have the server behind free version of Cloudflare Holly Osteen 3 to 4 sites in general
huh?
@overseer, I think I need some translation help.
218
CentOS 7 Problems / Re: the "listen ... http2" directive is deprecated
« on: July 14, 2024, 09:02:16 PM »
We only use Apache, but take a look at this about upgrading Nginx.
https://www.alphagnu.com/topic/55-how-to-install-latest-stablemainline-nginx-in-cwp-centos-89-stream-almalinux-89-rockylinux-89/#comment-84
https://www.alphagnu.com/topic/55-how-to-install-latest-stablemainline-nginx-in-cwp-centos-89-stream-almalinux-89-rockylinux-89/#comment-84
219
Information / Re: I paid for Pro and was charged by Stripe. But no answer in the Ticket #438687
« on: July 13, 2024, 09:44:41 PM »
We ALL understand you HATE CWP, and keep advertising on here now for Hestia, we got it...
When I place a support ticket, I get an answer within 12 hours or less.
Yes, we are a Reseller and have out own interfcae for adding licenses, so should of you being a 'NOC Partner'.
They do sometimes fall a little behind in releasing an update that includes the new PHP, but lately they have kept on top of that also.
Hestia runs on Debian or the consumer version ubuntu. And not a RHEL-base OS.
There are thing that OS is better for, and some that it worse.
One is EXIM which lags behind Postfix and even Sendmail.
To bad hestaCP's last release on 2023-11-27 with 1.8.11, Almost 8 months ago.
Last CWP updated was on 2024-07-06 with 0.9.8.1181.
Now which one sounds 'abandoned' 8 months or 7 days?
FYI - Hestia IS based on a past abandoned project Vesta. Which looks like they announced a new redo in September 2024 and are bringing back to life, maybe, we will see in September.
aaPanel works on AlmaLinux 8 and 9. Even Debian. And is free also.
When I place a support ticket, I get an answer within 12 hours or less.
Yes, we are a Reseller and have out own interfcae for adding licenses, so should of you being a 'NOC Partner'.
They do sometimes fall a little behind in releasing an update that includes the new PHP, but lately they have kept on top of that also.
Hestia runs on Debian or the consumer version ubuntu. And not a RHEL-base OS.
There are thing that OS is better for, and some that it worse.
One is EXIM which lags behind Postfix and even Sendmail.
To bad hestaCP's last release on 2023-11-27 with 1.8.11, Almost 8 months ago.
Last CWP updated was on 2024-07-06 with 0.9.8.1181.
Now which one sounds 'abandoned' 8 months or 7 days?
FYI - Hestia IS based on a past abandoned project Vesta. Which looks like they announced a new redo in September 2024 and are bringing back to life, maybe, we will see in September.
aaPanel works on AlmaLinux 8 and 9. Even Debian. And is free also.
220
SSL / Re: Domain works on SSL but not the ports
« on: July 13, 2024, 09:29:40 PM »
Look like your SSL configuration is already corrupted from something.
CWP doesn't always use the default paths, and when you try to start doing stuff via CLI without knowing exactly what, the system can become corrupted.
The path listed in the log is not the default path to SSL certificates.
Only option I could suggest is to redo the server from scratch, and not use CLI, and stick to the GUI.
Support maybe able to login and fix thing, but I am not sure.
CWP doesn't always use the default paths, and when you try to start doing stuff via CLI without knowing exactly what, the system can become corrupted.
The path listed in the log is not the default path to SSL certificates.
Only option I could suggest is to redo the server from scratch, and not use CLI, and stick to the GUI.
Support maybe able to login and fix thing, but I am not sure.
221
SSL / Re: Domain works on SSL but not the ports
« on: July 13, 2024, 04:36:42 AM »
Did you whitelist your IP in csf?
If you didn't, and you removed the admin ports from csf's TCP_IN, then that might be the problem.
CWP doesn't use 8181, 8443, or 9090
dnsvj,com as the certificate for rocks.dnsvj.com installed, at that domain & SSL are working.
The SSL manager doesn't create and install subdomain certificates for a whole different domain and another.
That has to be done manually
I looked at https://www.punjabrocks.com/, and the certificate is valid.
It just is having a problem with whatever is trying run on port 9988.
Best bet is to delete ALL the SSL certificates, USE the SSL Admin Panel to create them one by one for each domain name.
I'm also not sure if the Free Let's Encrypt SSL certificates will cover anything outside the normal ports (e.g. Web, FTP & Email)
Ports 2030, 2031, 2086, 2087, 2082, 2083 Do not respond, which points to a firewall issue.
If you can log into your CLI, run:
Then try to login to the web interface.
If you didn't, and you removed the admin ports from csf's TCP_IN, then that might be the problem.
CWP doesn't use 8181, 8443, or 9090
dnsvj,com as the certificate for rocks.dnsvj.com installed, at that domain & SSL are working.
The SSL manager doesn't create and install subdomain certificates for a whole different domain and another.
That has to be done manually
I looked at https://www.punjabrocks.com/, and the certificate is valid.
It just is having a problem with whatever is trying run on port 9988.
Best bet is to delete ALL the SSL certificates, USE the SSL Admin Panel to create them one by one for each domain name.
I'm also not sure if the Free Let's Encrypt SSL certificates will cover anything outside the normal ports (e.g. Web, FTP & Email)
Ports 2030, 2031, 2086, 2087, 2082, 2083 Do not respond, which points to a firewall issue.
If you can log into your CLI, run:
Code: [Select]
systemctl stop lfd
systemctl stop csfThen try to login to the web interface.
222
Installation / Re: Can't get CWPpro to activate
« on: July 13, 2024, 04:21:34 AM »
The IP needs to match the one at the bottom, next to Server IP:
Right under NS1 & NS2.
If that matches, log out of the web interface, and goto your CLI via SSH and run:
Now log back into the web interface, and it should be on CWPpro.
Right under NS1 & NS2.
If that matches, log out of the web interface, and goto your CLI via SSH and run:
Code: [Select]
sh /scripts/update_cwpNow log back into the web interface, and it should be on CWPpro.
223
Information / Re: security updates and 2fa
« on: July 12, 2024, 11:25:12 PM »
Block all the ports in CSF except the ones you want the public to have access to.
Then place your IP into the whitelist.
You can also use Cloudflare to Proxy incoming web requests.
Then place your IP into the whitelist.
You can also use Cloudflare to Proxy incoming web requests.
224
DNS Manager / Re: Error when saving changes in DNS Zone Editor
« on: July 12, 2024, 11:01:09 PM »
If you look, something is trying to access port 2302 on the localhost IP.
Which is a port DNS or CWP doesn't use, and really neither does anything else.
Are they trying to use CWP as the PRI or SEC DNS?
Which is a port DNS or CWP doesn't use, and really neither does anything else.
Are they trying to use CWP as the PRI or SEC DNS?
225
SSL / Re: Domain works on SSL but not the ports
« on: July 12, 2024, 10:55:41 PM »
What error shows in your SSL logs?
Or a screenshot of the error your are receiving in CWP?
Does the server have a Public IP with ports 80 & 443 open?
Or is it behind a NAT or Proxy?
Try running:
Did you create a hostname SSL certificate via the panel?
Creating SSL certificates via CLI may not work correctly, they should all be created & renewed with the admin panel under:
WebServer Settings -> SSL Certificates.
Or a screenshot of the error your are receiving in CWP?
Does the server have a Public IP with ports 80 & 443 open?
Or is it behind a NAT or Proxy?
Try running:
Code: [Select]
/root/.acme.sh/acme.sh --set-default-chain --preferred-chain "ISRG Root X1"Did you create a hostname SSL certificate via the panel?
Creating SSL certificates via CLI may not work correctly, they should all be created & renewed with the admin panel under:
WebServer Settings -> SSL Certificates.
