SSL pointing the wrong IP?

[KatuGT]

My domain is:
soñeque.com (IDN)
soñeque.com

I ran this command:
It is not a comandm I am at CloutPanel, trying to add the SSL certificate

It produced this output:
www.soñeque.com: Domain could not be validated, error message: error type: urn:ietf:params:acme:error:unauthorized, error detail: 31.214.178.54: Invalid response from http://www.soñeque.com/.well-known/acme-challenge/qHGHXzk_kUjx1rzieUFOSKuTb_lO6eEvQ8LtFTvti2Y: 404

My web server is (include version):
Ubuntu 22.04

The operating system my web server runs on is (include version):
I don´t know what write here, sorry

My hosting provider, if applicable, is:
Hostinger

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):
CloudPanel

let me show you this

I dont knot from where comes 31.214.178.54, it is not in my records, you cansee it en this image

If I check my domain, I can see there is a similar one but the last number es not the same. The website is now working, but I just can apply the SSL certificate

the Vhost is this:

server {
  listen 80;
  listen [::]:80;
  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  {{ssl_certificate_key}}
  {{ssl_certificate}}
  server_name www.xn--soeque-xwa.com;
  return 301 https://xn--soeque-xwa.com$request_uri;
}

server {
  listen 80;
  listen [::]:80;
  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  {{ssl_certificate_key}}
  {{ssl_certificate}}
  server_name xn--soeque-xwa.com www1.xn--soeque-xwa.com;
  {{root}}

  {{nginx_access_log}}
  {{nginx_error_log}}

  if ($scheme != "https") {
    rewrite ^ https://$host$uri permanent;
  }

  location ~ /.well-known {
    auth_basic off;
    allow all;
  }

  {{settings}}

  index index.html;

  location / {
    proxy_pass http://127.0.0.1:{{app_port}}/;
    proxy_http_version 1.1;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_pass_request_headers on;
    proxy_max_temp_file_size 0;
    proxy_connect_timeout 900;
    proxy_send_timeout 900;
    proxy_read_timeout 900;
    proxy_buffer_size 128k;
    proxy_buffers 4 256k;
    proxy_busy_buffers_size 256k;
    proxy_temp_file_write_size 256k;
  }
}

---

I can see that in www1.xn--soeque-xwa.com tehre is a "1", it wasn´t added from me, I deleted it before but it did nothing.

If it is not a topic related to this communitr please let me now, I will delete the post

[9peppe]

@KatuGT

are these A and AAAA records pointing to the right server?

if so, you can probably remove the ANAME record and retry.

[KatuGT]

yes, they are ok, the website perse is working but not with https, I think that shows that the records are right?

I already deleted the ANAME to try what you say, I don´t now if take some time to update but I will try later to add the SSL certificate

[Osiris]

Note that the www subdomain points to some sort of parking hostname with a CNAME, is that correct?

[KatuGT]

that one?yes, It did have a diferente valor, I just edited it beceause someone else that may help to

[KatuGT]

Good news!! it works Thanks Osiris