Error create ssl cyberpanel

Isn't it working now?

with permission 0664 the files are accessible from the outside

OK
And with 644?

Yes, the files are accessible, but when trying to create the ssl it still gives errors

1 Like

Ok now I understand.
If you show:
ls -l /that/file
You can see which users/groups are allowed access.

-rw-rw-r--+ 1 root root 22 oct 4 09:20 testfile

hmm...
Well both are root so:
664 and 6*4 should have done the same thing.
unless one is a user and one is a group...
But, in any case, it really doesn't matter - use the one that works best.

ok, now I am seeing that the web is loading a certificate from another domain ... we have advanced something ... I have a reverse proxy.

Now you remembered that! - LOL

No, now my partner told me , sorry...

1 Like

@ikarus
Slap them silly for me! LOL

my face of hatred I think it has been enough ..., however he is not in charge of I am the person who died of covid and now I have had to take the reins of this ... and I am very lost

1 Like

Sorry for your loss.
I hope to have you up and running very soon.
What is the O/S of the proxy?
What is the ACME client it uses?

I try to be up and running, but it has left a good legacy and it is difficult to follow in its footsteps, but I will try, the operating system that uses the proxy is xampp windows (apache), and then it does the reverse proxy to dos centos 7 with cyberpanel, under windows we use certbot

@ikarus
Are you an admin (root user) on the proxy system?
If so, please show the output of:
sudo apachectl -t -D DUMP_VHOSTS

What do you mean by?:

Isn't certbot installed on the proxy?

I have the administrator account of all the computers, I have used the command in centos and it does not show anything, it gives an error, it shows me this:
sudo apachectl -t -D DUMP_VHOSTS
sudo: apachectl: command not found

Let's see, I'm going to try to explain how the server works, the server consists of 3 servers, a windows with xampp and as the main server which receives all requests, it depends on the web you call, it is requested from one server or another There are 3 servers, 1 windows and 2 centos with cyberpanel, when the request that arrives is from a website that is in a cyberpanel, what it does is reach a request to windows and redirect it through a reverse proxy to the corresponding centos.

certbot I have it installed in windows and without problem, and when the request comes to cyberpanel it can load the web by https but the certificate it takes is the one installed in windows in one of the webs

I'm sorry, but I can't understand what you've said.
Maybe if you have a flow diagram or anything more, I might be able to understand better.

In the meantime...
If the Windows XAMP terminates the inbound TLS/SSL connections, then that is where we need to start.

Ok, let's see if I can explain myself better, I have 3 servers, windows has xampp and receives the requests, then 2 centos with cyberpanel, then I have a website that is djpinchos.cloud (hosted on windows) and with an ssl certificate, then I have another what is labodademismejoresamigos.info (hosted in centos) and what loads the djpinchos.cloud certificate, up to here ok

OK
They use the same IP and take the same path.

But they reach two different web servers...

curl -Iki https://djpinchos.cloud
HTTP/1.1 200 OK
Date: Mon, 04 Oct 2021 14:18:42 GMT
Server: Apache/2.4.39 (Win64) OpenSSL/1.1.1c PHP/7.3.8
X-Powered-By: PHP/7.3.8
Set-Cookie: 2355495cc7e2d641864ecd8448f227b6=rvfloh2j0n8aoovjtes8lj0s6b; path=/; HttpOnly
Expires: Wed, 17 Aug 2005 00:00:00 GMT
Last-Modified: Mon, 04 Oct 2021 14:18:43 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html; charset=utf-8

curl -Iki https://labodademismejoresamigos.info
HTTP/1.1 200 OK
Date: Mon, 04 Oct 2021 14:19:03 GMT
Server: LiteSpeed
content-type: text/html; charset=UTF-8
link: <https://labodademismejoresamigos.info/index.php?rest_route=/>; rel="https://api.w.org/"
vary: Accept-Encoding
x-litespeed-cache: hit

Yes, they use the same public IP and therefore they use the same path, private obviously is not the same, they are on the same network and they are seen without problems, in fact it is accessed without problems from the internet, the only problem is the ssl, is that The webs that are in centos load the ssl of the web that is in windows