So, I am using CWP to test how it performs but I ran into several issues that I need help with.
So I installed CentOS 8 on a server and installed CWP using the installation instruction provided in the documents. I changed the webserver to NGINX+Varnish+Apache. I also changed my PHP version to 8.1.15. I created a cwp user added
mydomain.com there. then I created a subdomain in the usercp called it
panel.mydomain.com so that the DNS is setup properly. I also ensured that both the domain and subdomain are pointing to the server by using dnschecker.org
1. Whenever I reboot the server, The hostname changes back to default
2. When I generate an SSL under CWP>Change Hostname. It generates a self-signed certificate. and this is what I see in /var/log/cwp/autossl.log
2023-12-18 08:12:08 panel.mydomain.com Failed http validation for Hostname: panel.mydomain.com
2023-12-18 08:12:08 panel.mydomain.com Self-signed SSL installed for Hostname: panel.mydomain.com
3. from usercp when I try to generate an SSL for mydomain.com from Domain>AutoSSL this is the error I face
DNS of your domain doesn't point to this server or you have htaccess restrictions
How do I solve all these SSL issues? I've looked into the DNS editor and also tested that the domains are pointed to the server using nslookup both from the inside the server as well as other computers. I am truly baffled and out of ideas on what could be causing this.
If you have https only set, Domain validation will fail because of the 403 redirect.
if you mean opened ports. Then I have both 80 and 443 open. I don't see any option for https only however...
I mean if you have apache or nginx set to "force https", the all port 80 requests will be redirected to ssl. This breaks letsencrypt for some reason.
will that be in the vhost configs? Or will it be in any GUI option? I looked through all the config files, nothing is forcing https from what I see. however, the proxy pass location is using the https protocol for reversing port 2083 and 2031
I am using Nginx+Varnish+Apache webserver configuration btw.
if this line is there, it's redirecting.
return 301 https://$server_name$request_uri;
yup none of the conf contains those. I also didn't enable anything related to https forcing. so unless those rediects comes default with cwp confs it's unlikely there.
I can dm you the access to the server to check if you want. i don't mind since this is a demo server.
You can check the log file /root/.acme.sh/acme.sh.log to see what is going on.
sudo tail /root/.acme.sh/acme.sh.log
tail: cannot open '/root/.acme.sh/acme.sh.log' for reading: No such file or directory
is /.well-known/acme-challenge/ and /.well-known/pki-validation present the the panel. vhost file?
yes with a alias of "/usr/local/apache/autossl_tmp/.well-known/acme-challenge"
Please visit https://letsdebug.net/ and post the results
(http://[b]https://ibb.co/Cs6rkHz%5B/b%5D)
server.domain.com is my hostname and I have port 80 open just to confirm.
Without the actual domain name, it's kind of hard to actually help you.
(https://ibb.co/v4tqZqg)
Hostname and IP address so we can do some external checks.
the hostname and ip are already provided in the images above.
Your image isn't appearing. Just type them.
Hostname: server.alpahnode.in
IP: 140.238.243.255
When I do a dns lookup for server.alpahnode.in, alpanode.in i get NXDOMAIN. Did you purchase the domain name?
Corrected your spelling for "alphanode.in" You do not have an A record for panel.alphanode.in, so letsencrypt cannot possibly do a valid lookup to issue it a certificate
Leaf DNS is showing the A record as what you entered.
http://leafdns.com/index.cgi?testid=6A3F09FB
Is this on a NAT?
Since you seem to have everything going to that poor single IP.
http://leafdns.com/index.cgi?testid=EA888DD3
Do you have port 80 & 443 open in your firewall & upstream?
Quote from: rcschaff on December 21, 2023, 03:43:36 AM
Corrected your spelling for "alphanode.in" You do not have an A record for panel.alphanode.in, so letsencrypt cannot possibly do a valid lookup to issue it a certificate
I am using server.alphanode.in as hostname not using panel.alphanode.in
Quote from: Starburst on December 21, 2023, 07:45:49 AM
Leaf DNS is showing the A record as what you entered.
http://leafdns.com/index.cgi?testid=6A3F09FB
Is this on a NAT?
Since you seem to have everything going to that poor single IP.
http://leafdns.com/index.cgi?testid=EA888DD3
Do you have port 80 & 443 open in your firewall & upstream?
I don't think it's going through a NAT since this is a VPS. created it only for testing CWP.
I'm getting an 'DNS_PROBE_FINISHED_NXDOMAIN' now where before when I tried it I got the default CWP page, which was correct when I tried server.alphanode.in.
And alphanode.in and the IP associated to everything is giving 'ERR_CONNECTION_REFUSED'.
As when you enter the server FQDN or IP, you should get the default CWP page, unless you have changed it manually.
If you would like, send me a PM with the login info, and I can login and take a look at what's going on.
I can already see there is no SSL for the hostname.