Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
My web server is (include version): Apache 2.4.38
The operating system my web server runs on is (include version): Deepin 20.2 (based on Debian)
My hosting provider, if applicable, is: ionos.com is my domain provider, if that's what this means
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no, unless pterodactyl counts
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.14.0
In your apache configuration, you need to look at the VirtualHosts defined in your configuration files. Specifically you need to look at which ServerName and (maybe) ServerAlias is/are defined within each VirtualHost along with which SSL certificate and key is defined within that VirtualHost. You're pairing the host (ServerName/ServerAlias) with the certificate and its key. Be aware of the port number associated with each VirtualHost (something like *:443).
You should begin by identifying which configuration files are active with:
sudo apachectl -S
You can use the following to identify which certificates you have available:
sudo certbot certificates
That command will help you match the certificate names to a part of the directory listed next to the SSL certificate and key directives in your apache VirtualHosts. This will let you know what domain names are covered by each named certificate and the path to the appropriate fullchain and privkey files for that certificate.
looks like 8443 isn't served by apache at all, lets see sudo netstat -tulpn | grep 8443 so we can see which process using that port
btw did you turn the server off? I can't connect to your website at all
it looks like it still uses certificate that only name is node1.trixyservers.com,
that The required authorization heads were not present in the request reply is Nodejs itself refuse to talk as we are not authenticated, to not sure what's your problem now
If your app talks to node1.trixyservers.com:8443 then the cert it has on that port looks fine, if your app tries to talk to pterodactyl.trixyservers.com:8443 instead then that probably won't work because the name in the subject of the certificate is wrong. You could just use the cert you already have for pterodactyl.trixyservers.com:443 - the same cert can be used for multiple services.
My best suggestion would be to look at your existing server configuration files to see how you are pointing to the certificate files, then update that.
You will gain a lot by have a proper read through all of your configuration files for your web services, so that you understand it more, especially regarding where your certificates are being kept and how to point configuration to different files.
Relying on tools to set all the values means you don't get the experience/knowledge required to really understand how it all works. We could keep going back and forth here trying to help you configure this but I don't think it's actually helping you.
First step IMHO is for you to actually understand which software is running on your system and which software is providing what exactly. I mean no offence, but I have a feeling you don't fully grasp the workings of your own system, which is pretty much a requirement for us to successfully help you with this specific issue.