About a year and a half ago I created a droplet on Hetzner and installed next cloud with let's encrypt with the subdomain https://drive.leojung.cloudns.ph/ then about 6 months ago I formatted my droplet about a week ago I decided to install Nginx Proxy Manager Then I bought a domain with .xyz on hostinger created a A record pointig to my ip and I created a certificate with let's encrypts (My IP is still the same when I first created the droplet) http is working but something is not working hhtps the message I'm getting is this on chrome
This site can’t be reached The webpage at https://myserver.xyz/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SSL_UNRECOGNIZED_NAME_ALERT
on firefox the message is
Secure Connection Failed
An error occurred during a connection to https://myserver.xyz. SSL peer has no certificate for the requested DNS name.
Error code: SSL_ERROR_UNRECOGNIZED_NAME_ALERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
I moved your post to the Help section. You would have been shown a series of questions to answer but we can start without that.
First, is myserver.xyz your actual name? Because you say HTTP requests are working but I cannot connect to that name using HTTP from various locations.
And, you claim to have gotten a cert but I don't see one for that name either.
If that is not your name please don't use other people's domain names in posts. We will need your actual name to help.
HTTP connections to that domain reach an openresty server. I was expecting to see an nginx server.
Are you using openresty? If not, your DNS is probably setup to use some sort of URL Redirect or Domain Forwarding service. That can work for HTTP but not for HTTPS. You need the DNS A record to point to your public IP address for nginx.
I looked at this further and do not think your DNS A record has the wrong IP. It might, but, the domain reaches an NPM system so it would be odd coincidence to be wrong and also point at a different NPM.
That said, this is some sort of SSL/TLS config issue. And, the page returned from HTTP says you need to complete the NPM setup. Even if you have you need to sort this out with NPM support.
I get the same error you describe for HTTPS. But, for HTTP this is a partial response
curl -i http://leoti.xyz
HTTP/1.1 200 OK
Server: openresty
<!DOCTYPE html>
<html lang="en">
<head>
...
<title>Default Site</title>
...
</head>
<body>
<div class="container">
<div class="jumbotron">
<h1>Congratulations!</h1>
<p>You've successfully started the Nginx Proxy Manager.</p>
<p>If you're seeing this site then you're trying to access a host that isn't set up yet.</p>
<p>Log in to the Admin panel to get started.</p>
...
I am not an NPM expert but it looks like you now have to do that.
I see you got a cert (two, actually) so now you just have to configure your system for HTTPS and to use that cert. We focus on helping people get certs. We also often help configure common servers. But, NPM is a configurator that is hard to debug. Their support is the best place to resolve this. I saw other people posting about the same problem on their github.
If you can't resolve it you might want to reconsider using NPM. If you just want to run a webserver you might try running nginx by itself without NPM and containers. In the end you need a system that you can manage and understand.
